InfoCenter Home > 3.4.2: Migrating configurations manuallyManual migration might be necessary if either your current installation or your Version 4.0 installation requirements vary too much from assumptions made by the product installation program. This article outlines the first and last steps of the overall product migration process, as follows:
Exporting the current administrative configurationBefore exporting the configuration to a file, be sure an administrative server is running. A sample export command for Version 3.0x follows. You may have to update many of the values used in this sample to reflect your configuration requirements. j:\jdk1.1.8.orig\bin\java Dserver.root=j:\websphere\appserver302 Dcom.ibm.CORBA .ConfigURL=file:/j:/WebSphere/AppServer302/properties/sas.client.props classpath 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_302_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\appserver302\hosts > j:\websphere\backup\userFiles\hosts
j:\websphere\appserver302\servlets > j:\websphere\backup\userFiles\servlets j:\websphere\appserver302\classes > j:\websphere\backup\userFiles\classes j:\websphere\appserver302\deployableEJBs > j:\websphere\backup\userFiles\deployableEJBs j:\websphere\appserver302\deployedEJBs > j:\websphere\backup\userFiles\deployedEJBs j:\websphere\appserver302\properties > j:\websphere\backup\programFiles\properties Also copy one of the following, depending on your operating system:
Restoring the configuration in the new installationFirst, copy the backed-up configuration files into the new installation directory. Be sure to update any names shown in the following samples to reflect your configuration requirements.
j:\websphere\backup\userFiles\hosts > j:\websphere\appserver35\hosts
j:\websphere\backup\userFiles\servlets > j:\websphere\appserver35\servlets j:\websphere\backup\userFiles\classes > j:\websphere\appserver35\classes j:\websphere\backup\userFiles\deployableEJBs > j:\websphere\appserver35\deployableEJBs Restore the following file:
j:\websphere\backup\bin\admin.config > j:\websphere\appserver35\bin\admin.config
In addition, restore one of the following files, depending on your operating system:
Next, import the configuration. A sample import command for Windows NT/2000 follows. Remember that you must update many of the values to reflect your configuration requirements. j:\websphere\appserver35\jdk\jre\bin\Java Dserver.root=j:\websphere\appserver35 Dcom.ibm.CORBA.ConfigURL=file:/j:\websphere\appserver35/properties/sas.client.props classpath j:\websphere\appserver35\lib\ibmwebas.jar; j:\websphere\appserver35\lib\servlet.jar; j:\websphere\appserver35\lib\xml4j.jar;j:\websphere\appserver35\lib\ujc.jar; j:\websphere\appserver35\lib\ejs.jar;j:\websphere\appserver35\lib\console.jar; j:\websphere\appserver35\lib\admin.jar;j:\websphere\appserver35\lib\repository.jar; j:\websphere\appserver35\lib\sslight.jar;j:\websphere\appserver35\lib\tasks.jar; j:\websphere\appserver35\properties com.ibm.websphere.xmlconfig.XMLConfig -adminNodeName cally -nameServiceHost cally -nameServicePort 900 import j:\websphere\backup\websphere_302_backup.xml |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|