Migrating the application using the WCIM migration script

Review this information while using the Migration wizard to migrate your WebSphere Application tier. Follow the information if you want to migrate your application tier using the WCIM script.

Before you begin

  • Ensure you have completed the database migration successfully.
  • Application tier migration using mapped or networked drives is not supported.
  • If WebSphere Application Server Global Security is enabled, disable it before you migrate your application.
  • For IBM i OS operating systemIf you are performing a remote application migration, the following steps must be completed before starting the application migration script:
    1. Install WebSphere Application Server version 7 on the WebSphere Commerce Version 5.6.1 or 6.0 machine.
    2. Copy WC_installdir/bin/backupAppWAS400.sh on the WebSphere Commerce Version 7 machine to a temporary directory tempDir on the WebSphere Commerce Version 5.6.1 or 6.0 machine.
    3. Run tempDir/backupAppWAS400.sh on the WebSphere Commerce Version 5.6.1 or 6.0 machine. For more information, run backupAppWAS400.sh directly to see its usage details.
    4. Copy prod.jar, user.jar, and backupforpostupgrade.jar from /tmp on the WebSphere Commerce Version 5.6.1 or 6.0 machine to a temporary directory tempDir70 on the WebSphere Commerce Version 7 machine.
    5. Run WC_installdir/bin/restoreAppWAS400.sh on the WebSphere Commerce Version 7 machine to restore the backup files. For more information, run restoreAppWAS400.sh directly to see its usage details.
    6. Ensure your WebSphere Application Deployment Manager and all federated node agents for WebSphere Commerce version 5.6.1 or 6.0 are stopped.

About this task

The following functions are performed by the WCIM utility:

  • Backing up of the existing application tier that is being migrated
  • Migration of the existing application tier to the WebSphere Commerce Version 7.0 level
Note: If you are using multiple instances on your previous installation of WebSphere Commerce, you must back up and migrate each instance separately.

Procedure

  • Choose one of the following options to migrate your application tier:
  • WebSphere Commerce Version 7.0 and previous version are on different machines
    1. Insert the WebSphere Commerce Version 7.0 media into the drive on the machine where the previous version of WebSphere Commerce is installed.
      Note: You might also be prompted to insert a WebSphere Application Server supplemental DVD.
    2. AIXIf you run the installation on AIX version 5.3, you may get an error forcing you to cancel the installation, with a message similar to the following example:
      AIX 53 Maintenance Level 06-01 was detected.  AIX 53 Maintenance level 07-01 is required.
      Upgrading your operating system will prevent this message. If you do not want to upgrade your old WebSphere Commerce server operating system, an alternate migration path has been provided. Perform the following steps:
      1. On your WebSphere Commerce 7.0 system, make a copy of WC_installdir\bin\backupAppWAS60.sh to a temporary directory, tempdir, on the remote (old) machine.
      2. Run the following command as the root user on your old WebSphere Commerce server:
        tempDir/backupAppWAS.sh -oldWASDir WAS_installdir -oldWCSDir WCS_installdir [oldProfileName]
      3. The script creates two folders in tempDir. Copy tempDir to your WebSphere Commerce version 7 server.
      4. Run the following command on the WebSphere Commerce version 7 server: 
        chown -R wasuser:wasgroup tempDir
      Attention: After running this command, skip to the back up your version 7 application tier step.
    3. If you are not running AIX 5.3, and are not forced to cancel the installation, select Custom installation and choose to install only the Remote WebSphere Commerce Management Utilities component.
    4. SolarisLinuxAIXIf you are migrating from WebSphere Application Server Version 6.1, you need to change some file permissions before running the wcimRemoteBackup script:
      1. Log in as root.
      2. Open a command line session and change to the WAS_installdir\properties directory.
      3. Run the following command:
        chmod o+r NIFRegistry.properties profileRegistry.xml WSCustomConstants.properties
        Remember: Change the file permission back for security reasons after completing the application migration.
    5. On the machine where you just installed the remote WebSphere Commerce Management Utilities, navigate to the WC_installdir/bin directory and run the following command:
      • WindowswcimRemoteBackup.bat -tier app -from version -action backup -instanceName instance_name
      • SolarisLinuxAIXRun the following command as the non-root user:
        wcimRemoteBackup.sh -tier app -from version -action backup -instanceName instance_name
      where:
      version
      The original WebSphere Commerce version. Enter 561 or 60.
      This script creates a folder, WC_installdir/temp/zip, containing two files:
      • backupwas.zip
      • backupwc_version_instance_name.zip.
    6. Copy the resulting folders to the WebSphere Commerce Version 7.0 target system. Ensure the files are put in WC_installdir/temp/zip and ensure that the WebSphere Commerce non-root user is the owner of WC_installdir/temp/zip and the files. The Migration wizard displays the directories where the files must be placed.
    7. If you used backupAppWAS.sh or backupAppWAS400.sh to backup previous WebSphere Commerce application in step 2, then on your WebSphere Commerce version 7 machine, back up your version 7 WebSphere Commerce application tier and the application tier related assets using WCIM. For example:
      • Windowswcim_ant.bat -tier app -from previous_version -action backup -instanceName instance_name
      • For IBM i OS operating systemSolarisLinuxAIXRun the following command from using the non-root user: 
        ./wcim_ant.sh -tier app -from previous_version -action backup -instanceName instance_name
      where:
      previous_version
      Is the version of WebSphere Commerce you are migrating from for example, 561 or 60.
      When prompted, ensure that you:
      • Specify the tempDir/WAS as the previous WebSphere Application Server directory.
      • Specify tempDir/Commerce as the previous WebSphere Commerce directory.
    8. Migrate your application using the WCIM utility:
      1. SolarisLinuxAIXRun WCIM as the non-root user, for example, wasuser.
      2. Run the WCIM script (with any optional flags that you might require for your application tier) from the following directory:
        • For IBM i OS operating systemSolarisLinuxAIXWC_installdir/bin
        • WindowsWC_installdir\bin
      3. Type the following WCIM command to migrate the current WebSphere Commerce version application tier with minimal options (this is normally sufficient for most migrations):
        • For IBM i OS operating systemSolarisLinuxAIX./wcim_ant.sh -tier app -from previous_version -action migrate -instanceName instance_name
        • Windowswcim_ant.bat -tier app -from previous_version -action migrate -instanceName instance_name
        where:
        previous_version
        Is the version of WebSphere Commerce you are migrating from for example, 561 or 60.
        action
        Is either backup, migrate, or config. Enter migrate for application tier migration.

        Running the command migrates your application tier to the WebSphere Commerce Version 7.0 level.

      4. Provide responses to the following prompts:
        1. WCIM ensures that you choose an instance name from your previous version of WebSphere Commerce. You cannot change the name of the instance from your previous version of WebSphere Commerce.
        2. A new Web server host name. If you install the Web server locally on the WebSphere Commerce Version 7.0 machine, you can accept the default host name or type a new host name as applicable. If you use the same remote Web server as your previous WebSphere Commerce version, you need to type a new Web server host name that is different from that your previous WebSphere Commerce version. Otherwise, there will be a port conflict between your new instance and old instance. In test runs, you cannot reuse the same Web server host name as the production site is still running.
        3. The new profile name for WebSphere Commerce Version 7.0 can be different from the old profile name for WebSphere Commerce previous version except on iSeries Platform.
        4. For IBM i OS operating systemThe new profile name for WebSphere Commerce Version 7.0 must be the same as the old profile name for WebSphere Commerce previous version.
    9. Verify that WCIM ran successfully.
    10. Perform post migration steps.
    11. Configuring the application server and web server tiers from the command line.
  • WebSphere Commerce Version 7.0 and previous version are on the same machine
    1. On your source machine, back up your current WebSphere Commerce application tier and the application tier related assets using WCIM. For example:
      • Windowswcim_ant.bat -tier app -from previous_version -action backup -instanceName instance_name
      • For IBM i OS operating systemSolarisLinuxAIXRun the following command from using the non-root user: 
        ./wcim_ant.sh -tier app -from previous_version -action backup -instanceName instance_name
      where:
      previous_version
      Is the version of WebSphere Commerce you are migrating from for example, 561 or 60.
      For example:
      
./wcim_ant.sh -tier app -from 60 -action backup -instanceName mig60inst3
Are the two WebSphere Commerce products installed on the same machine? [ Yes ] (Yes,No,)
Yes
Previous WebSphere Commerce installation directory?
/QIBM/Proddata/CommerceServer60
Previous WebSphere Application Server installation directory?
/QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/<instance_name>
Previous WebSphere Application Server profile name?
<instance_name>
    2. Migrate your application using the WCIM utility:
      Note: Run WCIM as the non-root user
      1. Run the WCIM script (with any optional flags that you might require for your application tier) from the following directory:
        • For IBM i OS operating systemSolarisLinuxAIXWC_installdir/bin
        • WindowsWC_installdir\bin
      2. Type the following WCIM command to migrate the current WebSphere Commerce version application tier with minimal options (this is normally sufficient for most migrations):
        • For IBM i OS operating systemSolarisLinuxAIX./wcim_ant.sh -tier app -from previous_version -action migrate -instanceName instance_name
        • Windowswcim_ant.bat -tier app -from previous_version -action migrate -instanceName instance_name
        where:
        previous_version
        Is the version of WebSphere Commerce you are migrating from for example, 561 or 60.
        action
        Is either backup, migrate, or config. Enter migrate for application tier migration.
        Running the command migrates your application tier to the WebSphere Commerce Version 7.0 level.
      3. Provide responses to the following prompts:
        1. WCIM ensures that you choose an instance name from your previous version of WebSphere Commerce. You cannot change the name of the instance from your previous version of WebSphere Commerce.
        2. A new Web server host name. If you install the Web server locally on the WebSphere Commerce, Version 7.0 machine, you can accept the default host name or type a new host name as applicable. If you use the same remote Web server as your previous WebSphere Commerce version, you need to type a new Web server host name. Otherwise, there will be a port conflict between your new instance and old instance. In test runs, you cannot reuse the same Web server host name because the production site is still running.
        3. For IBM i OS operating systemThe WebSphere Application Server user directory is the same as the previous WebSphere Application Server installation directory. An example of this type of directory is /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/profile_name. Where profile_name is the name of the user profile.
        4. The new profile name for WebSphere Commerce Version 7.0 can be different from the old profile name for WebSphere Commerce previous version except on iSeries Platform.
        5. For IBM i OS operating systemThe new profile name for WebSphere Commerce Version 7.0 must be the same as the old profile name for WebSphere Commerce previous version.
      For example:
      
./wcim_ant.sh -tier app -from 60 -action migrate -instanceName <instance_name>
Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
os400
Remote database? [ false ] (true,false,)
false
Database name?
<database_name>
Database user?
<instance_name>
Database user password?
<db password>
Database server port?
50000
Web server type? [ HTTP ] (HTTP,IIS,NES,)
HTTP
Remote Web server? [ false ] (true,false,)
false
Are the two WebSphere Commerce products installed on the same machine? [ Yes ] (Yes,No,)
Yes
Is the WebSphere Application Server Global Security enabled? [ No ] (Yes,No,)
No
Is it a cluster member? [ No ] (Yes,No,)
No
    3. Verify that WCIM ran successfully.
    4. For IBM i OS operating systemSolarisLinuxAIXIf you disabled WebSphere Application Server Global Security before you migrated the application, you can re-enable it.
    5. Configuring the application server and web server tiers from the command line.