InfoCenter Home > 3.2.2.2.2: Saving the current configuration manuallyThis process uses a Version 3.x XMLConfig tool to export the current configuration. Before exporting an Advanced Edition configuration to a file, be sure that the administrative server is running. See XMLConfig documentation for further details on the following parameters:
Export from Version 3.x by using the standard XMLConfig interfaceA sample export command for Version 3.x follows: XMLConfig -export j:/websphere/backup/websphere_3x_backup.xml -adminNodeName cally This export technique works with the following limitations:
Export using the migration version of XMLConfigImportant: This procdure does not work for Version 3.x installations on Linux or Solaris. Use the previous procedure (standard Version 3.x XMLConfig). A sample export command for versions 3.02.x through 3.5.1 follows. For versions 3.5.2 and later, use the XMLConfig35.jar file instead of XMLConfig302.jar. This sample reflects a Windows NT installation. You may have to update many of the values used in this sample to reflect your configuration requirements or when using a different operating system. The server.root variable points to the currently installed Version 3.02x directory. j:\jdk1.1.8.orig\bin\java -Dserver.root=j:\websphere\appserver302 -Dcom.ibm.CORBAConfigURL=file:/j:/WebSphere/AppServer302/properties/sas.client.props -classpath j:\WebSphere\AppServer40\bin\XMLConfig302.jar; j:\websphere\appserver302\lib\ibmwebas.jar; j:\websphere\appserver302\lib\servlet.jar; j:\websphere\appserver302\lib\xml4j.jar;j:\websphere\appserver302\lib\ujc.jar; j:\websphere\appserver302\lib\ejs.jar;j:\websphere\appserver302\lib\console.jar; j:\websphere\appserver302\lib\admin.jar;j:\websphere\appserver302\lib\repository.jar; j:\websphere\appserver302\lib\sslight.jar;j:\websphere\appserver302\lib\tasks.jar; j:\jdk1.1.8.orig\lib\classes.zip; j:\websphere\appserver302\propertiescom.ibm.websphere.xmlconfig.XMLConfig -adminNodeName cally -nameServiceHost cally -nameServicePort 900 -export j:\websphere\backup\websphere_3x_backup.xml Backing up configuration filesFirst, make copies of key directories. Remember that you must update many of the names shown in the following samples to reflect your configuration requirements: j:\websphere\appserver\hosts > j:\websphere\backup\websphere_3x_backup.userFiles\hosts j:\websphere\appserver\servlets > j:\websphere\backup\websphere_3x_backup.userFiles\servlets j:\websphere\appserver\classes > j:\websphere\backup\websphere_3x_backup.userFiles\classes j:\websphere\appserver\deployableEJBs > j:\websphere\backup\websphere_3x_backup.userFiles\deployableEJBs j:\websphere\appserver\deployedEJBs > j:\websphere\backup\websphere_3x_backup.userFiles\deployedEJBs j:\websphere\appserver\properties > j:\websphere\backup\websphere_3x_backup.programFiles\properties Next, back up the following file: j:\websphere\appserver\bin\admin.config > j:\websphere\backup\websphere_3x_backup.programFiles\bin |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|