Migrating the WebSphere Commerce application using the Migration wizard

Before the application tier is migrated, a backup is needed. If the previous and new versions of WebSphere Commerce are installed on the same system, the Migration wizard automatically backs up the application for you. If the previous and new versions of WebSphere Commerce are installed on different systems, manual steps are required.

Before you begin

If WebSphere Application Server Global Security is enabled, disable it before you migrate your application.
If 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 your WebSphere Commerce Version 5.6.1 or 6.0 machine.
2. Copy WC_installdir/bin/backupAppWAS400.sh from 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 display 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.

About this task

If you are migrating multiple instances, you must complete the Migration wizard for each instance you want to migrate.

Procedure

Launch the Migration wizard.
Back up the WebSphere Commerce Version 5.6.1 or 6.0 application. The Migration wizard asks if the previous and new versions of WebSphere Commerce are installed on the same system.
- The WebSphere Commerce versions are installed on the same system. Continue with step 3
- The WebSphere Commerce versions are installed on different systems. Continue with step 3
- The WebSphere Commerce versions are installed on different systems. A backup is required. Continue with the following steps:
1. If you have not already done so, install the Remote WebSphere Commerce Management Utilities on the machine where WebSphere Commerce Version 5.6.1 or 6.0 is installed.
  Note: If 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:
  
  On your WebSphere Commerce 7.0 system, make a copy of WC_installdir\bin\backupAppWAS.sh to a temporary directory, tempDir, on the remote machine you are migrating from.
  
  Log into your old WebSphere Commerce server as the root user.
  
  Run the following command:
  tempDir/backupAppWAS.sh -oldWASDir WAS_installdir -oldWCSDir WCS_installdir [oldProfileName]
  If you use backupAppWAS.sh to back up the WebSphere Commerce Version 5.6.1 or 6.0 application, you must select Yes for WebSphere Commerce versions installed on the same machine in the Migration wizard.
  
  The script creates two folders in tempDir. Copy the tempDir folder to your WebSphere Commerce version 7 server.
  
  Run the following command on the WebSphere Commerce version 7 server:
  chown -R wasuser:wasgroup tempDir
  
  Continue with step 3 and when prompted, ensure that you:
  
  Specify tempDir/WAS as the previous WebSphere Application Server directory.
  
  Specify tempDir/Commerce as the previous WebSphere Commerce directory.
2. If 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.
3. 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:
  - wcimRemoteBackup.bat -tier app -from version -action backup -instanceName instance_name
  - Run 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.
4. 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.
Respond to prompts of the Migration wizard to migrate the application tier.
After the application migration completes, the Migration wizard displays a message box. Review the information and ensure that the WebSphere Application Server administrative console port number is recorded.
Optional: If you disabled WebSphere Application Server Global Security before you migrated the application, you can re-enable it.

What to do next

Configure the WebSphere Commerce application and the Web server using the Migration Wizard.