A fix is available
APAR status
Closed as documentation error.
Error description
This documentation regarding the import/export of a server confi guration archive (CAR) treats WAS 6.0 and WAS 6.1 as interchange able. It is not explicitly stated, but the message from the cust omer's point of view is that exporting a WAS 6.0 .car into a WAS 6.1 profile should work: http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/index.js p?topic=/com.ibm.ws.ast.st.v6.ui.doc/topics/timportscv6.html http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/topic/co m.ibm.ws.ast.st.v6.ui.doc/topics/texportscv6.html However, this isn't true. A WAS 6.0 .car can only be exported to a WAS 6.0 server and similarly, a WAS 6.1 .car can only be expo rted to WAS 6.1 (in particular, not to WAS 6.0.x). If users want to migrate a WAS 6.0 profile to a WAS 6.1 profile, they should instead use the migration wizard provided by WAS 6.1, as documen ted in: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com. ibm.websphere.base.doc/info/aes/ae/tmig_wizto61sas.html
Local fix
Problem summary
In regards to the following topic: http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/inde x.jsp?topic=/com.ibm.ws.ast.st.v6.ui.doc/topics/timportscv6. html http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/topi c/com.ibm.ws.ast.st.v6.ui.doc/topics/texportscv6.html Does not explicitly state that exporting a WebSphere Application Server v6.0 .car file cannot be imported into a WebSphere Application Server v6.1 profile. In addition, the import and exporting the server configuration tools cannot be used to migrating an existing WebSphere Application Server V6.0.x profile into a V6.1.x profile.
Problem conclusion
In the below topic changed the restriction section: http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/topi c/com.ibm.ws.ast.st.v6.ui.doc/topics/timportscv6.html Restriction -The Import server configuration from server option is supported for the WebSphere Application Server v6.1.x and v6.0.x.1 However, importing and exporting of the server configuration must be at the same version-level of the server. For example, if you import a server configuration from WebSphere Application Server V6.0.x, you must export the server configuration into a WebSphere Application Server V6.0.x. The server is going to fail to start if you attempt to export the server configuration into a WebSphere Application Server V6.1.x. -The Import server configuration from server and Export server configuration to server options are not the correct way to migrate an existing WebSphere Application Server V6.0.x profile into a V6.1.x profile. Instead, the Migration wizard from the WebSphere Application Server V6.1.x should be used. For details, see Migrating server configuration files from WebSphere Application Server V6.0.x to V6.1.x topic. In addition added a new topic, Migrating server configuration files from WebSphere Application Server V6.0.x to V6.1.x.
Temporary fix
Comments
APAR Information
APAR number
PK44792
Reported component name
APP DEV V6 WIN
Reported component ID
5724J1901
Reported release
700
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-05-08
Closed date
2007-09-27
Last modified date
2007-09-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 September 2007