InfoCenter Home >
3: Migration overview >
3.2: Migrating from previous product versions >
3.2.2: Migrating from Version 3.x >
3.2.2.2: Migrating configurations manually >
3.2.2.2.1: Saving the current configuration by using migration tools

3.2.2.2.1: Saving the current configuration by using migration tools

A set of migration tools is provided with the product to help migrate system configurations for installations at Version 3.x and later. The product installation program calls these tools as part of automated migration support. You can call them yourself from the command line.

The tool that saves the system configuration is called WASPreUpgrade. This tool saves all files from the following directories in the existing Version 3.x configuration to a specified backup directory:

  • hosts
  • servlets
  • classes
  • deployableEJBs
  • deployedEJBs
  • properties

WASPreUpgrade also saves selected files from the Version 3.x bin directory. Later, the backup directory can be used with the WASPostUpgrade tool to restore the previously saved environment into a Version 4.0 installation.

WASPreUpgrade also exports the existing application server configuration from the repository. If you are migrating from an Advanced Edition installation, this step requires that the administration server of the existing environment be running. This command is not typically run from the command line unless both Version 3.x and Version 4.0 are installed on the same machine at the same time.

WASPreUpgrade parameters

com.ibm.websphere.migration.preupgrade.WASPreUpgrade
backupDirectoryName
currentWebSphereDirectory
administrationNodeName
[-nameServiceHost host_name [-nameServicePort port_number]]
[-traceString trace_spec [-traceFile file_name]]

The first three parameters are required and positional. The others are optional. A summary follows:

  • backupDirectoryName - The name of the directory in which to store the saved configuration and files. The directory is created if it does not already exist. This is a required parameter.
  • currentWebSphereDirectory - The name of the installation root directory for the current Version 3.x installation. This can be either a Standard or Advanced Edition installation. This is a required parameter.
  • administrationNodeName - The name of the administration node for the currently installed product. XMLConfig is called using this parameter. This is a required parameter.
  • [-nameServiceHost host_name [-nameServicePort port_number]] - If specified, these optional parameters are passed to the XMLConfig tool. They can be used to override the default host name and port number used by XMLConfig.
  • [-traceString trace_spec [-traceFile file_name]] - These optional parameters are used to gather trace information for use by IBM service personnel. The value of the traceString parameter is "*=all=enabled" and must be specified with quotation marks to be processed correctly.

Logging

The WASPreUpgrade tool displays status to the screen while it is running. It also saves a more extensive set of logging information in the backup directory. This file, WASPreUpgrade.log, can be viewed with a text editor.

Special instructions for Linux and Solaris installations

When migrating from Version 3.0x on Linux and Solaris installations, mapping problems will occur in the security settings. The resulting configuration contains substitution variables such as $server_password$ and $server_root$. These values must be modified to their correct values after migration has been completed. It is also advisable to migrate these installations with Security disabled.

Restoring the previous Version 3.x configuration

With one minor modification, you can use the websphere_3x_backup.xml file (found in the backup directory) with a Version 3.x XMLConfig tool to restore the previous configuration. The version of XMLConfig used by WASPreUpgrade encrypts passwords during export. Before you import the configuration back into the Version 3.x installation, these passwords must be reset to their correct, unencrypted values.

Important: This file cannot be used directly in the Version 4.0 environment, because the XMLConfig tool is available only in Version 4.0 Advanced Edition. In addition, the DTDs for the two versions of XML configuration are not compatible; the XML data files exported by the Version 3.x XMLConfig tool cannot be processed by the Version 4.0 tool.

Go to previous article: Migrating configurations manually Go to next article: Saving the current configuration manually

 

 
Go to previous article: Migrating configurations manually Go to next article: Saving the current configuration manually