Migrate the application using the WCIM utility

Refer to this information while using the migration wizard to migrate your WebSphere Application tier.

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 6.0 level

If the application tier of the previous version of WebSphere Commerce (source) is on a different machine from your (target) WebSphere Commerce Version 6.0, complete the following steps. These steps will create a backup of your previous WebSphere Commerce application.

1. Insert the WebSphere Commerce v6 CD:

   • AIX|Linux|Solaris|Windows:

     Into the CD-ROM drive on the machine where the previous version of WebSphere Commerce is installed.

   • I5/OS|On a Windows system. Choose to install on the i5/OS machine where the previous version of WebSphere Commerce is installed. Enter the system name, user profile and password for this i5/OS machine.

2. Select Custom installation and choose to install only the Remote WebSphere Commerce Management Utilities component.

3. After installation completes, run the wcimRemoteBackup script on the previous version WebSphere Commerce machine.

   1. Complete the following steps:

      • I5/OS|Open a Qshell window by running the STRQSH command.

      • Navigate to the WC_installdir/bin directory.

   2. Run one of the following commands:

      • AIX|I5/OS|Linux|Solaris|./wcimRemoteBackup.sh -component app -from previous_version -action backup -instanceName instance

      • Windows: wcimRemoteBackup.bat -component app -from previous_version -action backup -instanceName instance

      • Where:

        previous_version

        Is the version of WebSphere Commerce you are migrating from for example, 55, 56, or 561.

        instance

        Is the name of the previous version WebSphere Commerce instance.

        This command will create an EAR file and zip file of the previous WebSphere Commerce instance.

   3. Copy the EAR and zip files to the WebSphere Commerce, v6 machine. The files must be copied to the same directories where the files were created on the previous WebSphere Commerce machine, for example:

      • AIX|Linux|Solaris|WC_installdir/temp or WC_installdir/temp/zip

      • I5/OS|WC60_userdir/tmp or WC60_userdir/zip

      • Windows: WC_installdir\temp or WC_installdir\temp\zip

4. Migrate the application using the WCIM utility:

   1. AIX|Linux|Solaris|Run WCIM as the same user you use to start your WebSphere Commerce application server. IBM recommends that you use a non-root user, for example, wasuser to do so. Following is an example of switching to the wasuser: su - wasuser.

   2. I5/OS|All WCIM commands must be run from within the i5/OS QShell. Open a Qshell window by running the STRQSH command. The user running WCIM must have *SECOFR authority.

   3. Run the WCIM script (with any optional flags that you might require for the application tier) from the following directory:

      • AIX|I5/OS|Linux|Solaris|WC_installdir/bin

      • Windows: WC_installdir\bin

   4. Type the following WCIM command to migrate the current WebSphere Commerce version application tier with minimal options (this is normally sufficient for most migrations):

      • AIX|I5/OS|Linux|Solaris|./wcim.sh -component component -from previous_version -action action -instanceName instance

      • Windows: wcim.bat -component component -from previous_version -action action -instanceName instance

      Where:

      previous_version

      Is the version of WebSphere Commerce you are migrating from for example, 55,56, or 561.

      component

      Is either app, ws, or wpm, meaning application, Web server, and Payments respectively.

      action

      Is either backup, migrate, or config.

      Run the command migrates the application tier to the WebSphere Commerce v6 level.

   5. Provide responses to the following prompts:

      1. AIX|Linux|Solaris|Windows:

         WCIM checks whether the WebSphere Commerce instance name is already used, and prompts you to enter a new WebSphere Commerce v6 instance name. The length of the WebSphere Commerce instance name you enter cannot be greater than 12 characters long and cannot include any of the following characters: / \ " | < > ? * : &.

      2. I5/OS|WCIM checks whether the WebSphere Commerce instance name is already used, and prompts you to enter a new WebSphere Commerce, Version 6.0 instance name. The length of the WebSphere Commerce instance name you enter cannot be greater than 10 characters and cannot include any of the following characters: / \ " | < > ? * : &.

      3. A new Web server host name. If you install the Web server locally on the WebSphere Commerce v6 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, 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 can not reuse the same Web server host name as the production site is still running.

   6. I5/OS|Provide a response to the prompt for the WAS V6 instance name that the migrated WebSphere Commerce instance will use.

   7. Verify that WCIM ran successfully. See the WebSphere Commerce Migration Guide.

   8. Perform post migration steps. See the WebSphere Commerce Migration Guide.

If your earlier version of WebSphere Commerce application tier is on the same machine as your WebSphere Commerce v6 machine, then follow these basic steps for application tier migration using the WCIM:

1. On your source machine, back up your current WebSphere Commerce application tier and the application tier related assets using WCIM for example:

   • AIX|I5/OS|Linux|Solaris|./wcim.sh -component app -from previous_version -action backup -instanceName instance

   • Windows: wcim.bat -component app -from previous_version -action backup -instanceName instance

   Where:

   previous_version

   Is the version of WebSphere Commerce you are migrating from for example, 55, 56, or 561.

   instance

   Is the name of the previous version WebSphere Commerce instance.

2. Migrate the application using the WCIM utility:

   1. AIX|Linux|Solaris: Run WCIM as the same user you use to start your WebSphere Commerce application server. IBM recommends that you use a non-root user, for example, wasuser to do so. Following is an example of switching to the wasuser: su - wasuser.

   2. I5/OS:

      All WCIM commands must be run from within the iSeries QShell. Open a Qshell window by running the STRQSH command. The user running WCIM must have *SECOFR authority.

   3. Run the WCIM script (with any optional flags that you might require for the application tier) from the following directory:

      • AIX|I5/OS|Linux|Solaris|WC_installdir/bin

      • Windows: WC_installdir\bin

   4. Type the following WCIM command to migrate the current WebSphere Commerce version application tier with minimal options (this is normally sufficient for most migrations):

      ./wcim.sh -component component -from previous_version -action action -instanceName instance

      • Windows: wcim.bat -component component -from previous_version -action action -instanceName instance

      Where:

      previous_version

      Is the version of WebSphere Commerce you are migrating from for example, 55, 56, or 561.

      component

      Is either app, ws, or wpm, meaning application, Web server, and Payments respectively.

      action

      Is either backup, migrate, or config.

      Run the command migrates the application tier to the WebSphere Commerce v6 level.

   5. Provide responses to the following prompts:

      1. AIX|Linux|Solaris|Windows:

         WCIM checks whether the WebSphere Commerce instance name is already used, and prompts you to enter a new WebSphere Commerce, v6 instance name. The length of the WebSphere Commerce instance name you enter cannot be greater than 12 characters long and cannot include any of the following characters: / \ " | < > ? * : &.

      2. I5/OS|WCIM checks whether the WebSphere Commerce instance name is already used, and prompts you to enter a new WebSphere Commerce, Version 6.0 instance name. The length of the WebSphere Commerce instance name you enter cannot be greater than 10 characters and cannot include any of the following characters: / \ " | < > ? * : &.

      3. A new Web server host name. If you install the Web server locally on the WebSphere Commerce, v6 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, 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 can not reuse the same Web server host name as the production site is still running.

   6. I5/OS|Provide a response to the prompt for the WebSphere Application Server 6 instance name that the migrated WebSphere Commerce instance will use.

   7. Verify that WCIM ran successfully. See the WebSphere Commerce Migration Guide.

   8. Perform post migration steps. See the WebSphere Commerce Migration Guide.

AIX|Linux|Solaris|Windows:

Application tier migration using mapped or networked drives is not supported.

 

Related Concepts

Migrate from a previous version of WebSphere Commerce

 

Related Reference

WCIM utility