InfoCenter Home >
3: Migration overview >
3.2: Migrating from previous product versions >
3.2.1: Migrating from Version 2.0x >
3.2.1.1: Migration from Version 2.0x to Version 3.0

3.2.1.1: Migration from Version 2.0x to Version 3.0

This article is for Version 2.0x users who have chosen to migrate to Version 3.5 or later by way of Version 3.0. After you have upgraded your Version 2.0x installation to Version 3.0 as specified in these instructions, install PTF 2 from the product Web site. At that point, you can use automated migration support to upgrade the product to Version 3.5 or later.

For complete Version 3.0x installation and configuration information, consult the product Web site Library page cited in the Related information.

Preparation before installing Version 3.0x

Before uninstalling any previous version of the product, be sure the files that you want to migrate will be saved. The graphical user interface displayed when you install Version 3.0x backs up the files in the following directories:

  1. classes
  2. realms
  3. servlets
  4. properties, including the files--
    • servlet.properties
    • admin_port.properties
    • rules.properties
    • jvm.properties
    • aliases.properties
    • conmgr.properties
    • userprofile.properties

If you have files that reside outside of those four directories (for example, if you created your own directory in the product installation), back up the files in a location outside of the current installation before installing Version 3.0x.

Before uninstalling Version 2.0x, back up files and directories so that you can perform the following procedure after installing Version 3.0x:

  1. Copy the Version 2.0x servlets directory to the Version 3.0x directory ...\WebSphere\AppServer\hosts\default_host\default_app\servlets.
  2. Copy all files in the Version 2.0x \classes directory to the Version 3.0x \classes directory.
  3. Copy all files in the Version 2.0x \web\classes directory to the Version 3.0x \web\classes directory.

Additional work after installing Version 3.0x

Before uninstalling Version 2.0x, you backed up some files in preparation for the previous steps. Finish those steps now.

Migrating administrative data

To assist you in moving administrative data from Version 2.0x to Version 3.0x, you can use a migration tool developed to move the data.

To start the data migration tool, use the following command:

java com.ibm.ejs.sm.ejscp.scripts.Migrate -file properties_file
-node node_name
-jarFile DB2_driver_jarfile
[-trace]

properties_file is the name of the configuration file. node_name is the name of the node. DB2_driver_jarfile is the name of the jar/zip file containing the JDBC provider. -trace enables tracing.

Running the tool gives you an ejscp script as the output. The output file name is Upgradenode_name.tcl. To complete the migration, run the script using ejscp with the following command:

java tcl.lang.Script Upgradenode_name.tcl
Go to previous article: Migration from Version 2.0x Go to next article: Migrating from Version 3.x

 

 
Go to previous article: Migration from Version 2.0x Go to next article: Migrating from Version 3.x