Migrating a WebSphere Commerce clustered environment to V7, Part 1: Migrating V5.6.1 to V7.0

The WebSphere® Commerce V7 cluster migration methodology has been changed compared to the WebSphere Commerce V6 cluster migration. The cluster migration process will vary because of different WebSphere Application Server versions and different migration paths. WebSphere Commerce V7 supports migration from V5.6.1 and V6.0. Part 1 of this 2-part tutorial series introduces the migration process for WebSphere Commerce V5.6.1 with WebSphere Application Server V5.1 and for WebSphere Commerce V6.0 with WebSphere Application Server V6.0.

Chuan Jie Zheng (zhengcj@cn.ibm.com), Software Engineer, IBM

Photo of Chuan Jie ZhengChuan Jie Zheng is a Software Engineer with the e-commerce development team at the IBM China Lab. He has worked on WebSphere Commerce for over 5 years. He specializes in distributed configuration, deployment, and migration of WebSphere Commerce.



Qiang Li (qiangli@cn.ibm.com), Software Engineer, IBM

Photo of Qiang LiQiang Li is a Software Engineer in the WebSphere Commerce installation and migration team at the IBM China Lab. He has more than 3 years of experience in WebSphere Commerce installation and migration testing. His areas of interest include deploying WebSphere Commerce product into customer sites and product documentation.



02 June 2010

Also available in

Before you start

This tutorial takes you through step-by-step instructions on migrating a WebSphere Commerce V5.6.1 cluster to a WebSphere Commerce V7.0 cluster. You will learn about remotely migrating WebSphere Application Server Network Deployment Manager from V5.1 to V7.0, remotely migrating WebSphere Application Server federated nodes from V5.1 to V7.0, the migration process for the Websphere Commerce database and application, and how to configure the migrated WebSphere Commerce system.

Objectives

  • Migrate Websphere Application Server Deployment Manager V5.1 to V7.0.
  • Back up and restore the WebSphere Commerce V5.6.1 configuration.
  • Migrate additional federated nodes from V5.1 to V7.
  • Install WebSphere Commerce V7.0.
  • Migrate WebSphere Commerce database using the WebSphere Commerce Migration Wizard.
  • Migrate WebSphere Commerce main node to V7.0 using the WebSphere Commerce Migration wizard.
  • Configure the Web server.

Prerequisites

You need to be familiar with:

  • WebSphere Application Server installation and migration
  • WebSphere Commerce installation and migration
  • Database backup and restore
  • Web server configuration

System requirements

To follow the examples in this tutorial, you need a WebSphere Commerce V5.6.1 clustered environment.

Duration

Approximately 14.5 hours:

  • 0.5 hour: Backing up the WebSphere Commerce V6 configuration
  • 0.5 hour: Installing WebSphere Application Server V7 Network Deployment Manager
  • 2 hours: Migrating WebSphere Application Server Deployment Manager from V5.1 to V7
  • 2 hours: Migrating the WebSphere Application Server federated node from V5.1 to V7
  • 4 hours: Installing WebSphere Commerce V7
  • 4 hours: Migrating the database and application
  • 1 hour: Configuring the Web server
  • 0.5 hour: Restoring the WebSphere Commerce V5.6.1 configuration

Preparation for migration

To keep the old environment running during migration, make sure WebSphere Application Server V5.1 Deployment Manager and all federated node agents for WebSphere Commerce V5.6.1 are stopped.

  • Command for the V5.1 Deployment Manager:
    bash-2.05# cd /usr/WebSphere/DeploymentManager/bin
    bash-2.05# ./stopManager.sh
  • Command for the V5.1 node agent (use the WC-non-root user to do the operation):
    bash-2.05$ cd /usr/WebSphere/AppServer/bin/
    bash-2.05$ ./stopNode.sh

Back up the old clustered environment before migration

  1. On the federated nodes and Deployment Manager, back up the configuration by running the backupConfig command provided by WebSphere Application Server:

    On the federated nodes:

    bash-2.05# cd /usr/WebSphere/AppServer/bin/
    bash-2.05# ./backupConfig.sh

    On the Network Deployment Manager node:

    bash-2.05# cd /usr/WebSphere/DeploymentManager/bin
    bash-2.05# ./backupConfig.sh

    The command will generate a backup file named WebSphereConfig_yyyy-mm-dd.zip.

  2. On the federated nodes, back up the following EAR file manually or use the command EARExpander.sh to backup the EAR file: WAS_installdir/installedApps/node_name/WC_demo.ear.
  3. On the federated nodes, back up the following file on your federated nodes, it will be used when you restore the old environment:
    WAS_installdir/config/cells/cell_name/nodes/node_name/servers/server_name/server.xml

Install WebSphere Application Server Network Deployment V7.0 on a remote Deployment Manager machine

  1. Run the command install from the <WAS7.0_package>/WAS directory to launch the IBM WebSphere Application Server 7.0 Network Deployment Installer with a WC-non-root user.
  2. Click Next on the WebSphere Application Server Network Deployment installation wizard Welcome page, as shown in Figure 1
    Figure 1. WebSphere Application Server Network Deployment installation wizard Welcome page
    WebSphere Application Server ND installation wizard Welcome page
  3. Select I accept both the IBM and non-IBM terms, click Next on the Agreement page, as shown in Figure 2.
    Figure 2. Software License Agreement page
    Software License Agreement page
  4. Click Next on the System Prerequisite Check page, as shown in Figure 3.
    Figure 3. System Prerequisite Check page
    System Prerequisite Check page
  5. Do not select any option. Click Next on the Optional Features installation page, as shown in Figure 4.
    Figure 4. Optional Features installation
    Optional Features installation
    Specify the production installation directory, for example, /usr/IBM/WebSphere/AppServer. Click Next on the Installation directory page, as shown in Figure 5.
    Figure 5. Installation directory
    Installation directory
  6. Select None. There will be no profiles created after the WebSphere Application Server installation. Click Next on the WebSphere Application Server Environments page, as shown in Figure 6.
    Figure 6. WebSphere Application Server Environments page
    WebSphere Application Server Environments page
  7. Uncheck Enable administrative security. Click Next on the Enable Administrative Security panel, as shown in Figure 7.
    Figure 7. Enable Administrative Security panel
    Enable Administrative Security panel
  8. Do not select Create a repository for Centralized Installation Managers. Click Next on the Repository for Centralized Installation Mangers page, as show in Figure 8.
    Figure 8. Repository for Centralized Installation Managers
    Repository for Centralized Installation Managers
  9. Click Next on the Installation Summary page, as shown in Figure 9.
    Figure 9. Installation Summary page
    Installation Summary page
  10. Click Next on the Installation Summary confirm page, as shown in Figure 10.
    Figure 10. Installation Summary confirm
    Installation Summary confirm
  11. After the installation completes, it will display successful results, as shown in Figure 11. Click Finish to complete the Application Server installation.
    Figure 11. Installation results
    Installation results

Create the WebSphere Application Server V7 Deployment Manager profile using the Profile Management tool

  1. Launch the Profile Managerment tool:
    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/firststeps
    bash-2.05$ ./firststeps.sh
  2. Click the Profile management tool on the “First steps” panel to launch the tool, as shown in Figure 12.
    Figure 12. First steps panel
    First steps panel
  3. Click Create on the Profile Management tool, as shown in Figure 13.
    Figure 13. Profile Management tool
    Profile Management tool
  4. Select Management to create the Deployment Management profile. Click Next, as shown in Figure 14.
    Figure 14. Environment selection
    Environment selection
  5. Select Deployment manager and click Next, as shown in Figure 15.
    Figure 15. Server Type selection
    Server Type selection
  6. Select Advance profile creation and click Next, as shown in Figure 16.
    Figure 16. Profile Creation options
    Profile Creation options
  7. Check Deploy the administrative console and click Next, as shown in Figure 17.
    Figure 17. Optional Application Deployment
    Optional Application Deployment
  8. Specify the profile name, for example Dmgr01, and specify the profile Directory, for example, /IBM/WebSphere/AppServer/profiles/Dmgr01. Click Next as shown in Figure 18.
    Figure 18. Profile name and location
    Profile name and location
  9. Specify the Node name, for example wci92Cellmanager01. Note: For the cell name, the V7.0 Deployment Manager profile must have the same cell name as V5.1 that is being migrated. Otherwise, the Deployment Manager profile migration will fail. Input the host name and click Next, as shown in Figure 19.
    Figure 19. Node, Host, and Cell names panel
    Node, Host, and Cell names panel
  10. Uncheck Enable administrative security and click Next, as shown in Figure 20.
    Figure 20. Administrative Security
    Administrative Security
  11. Check Create a new default person certificate and click Next, as shown in Figure 21.
    Figure 21. Security Certificate, Part 1
    Security Certificate, Part 1
  12. Accept the default value and click Next, as shown in Figure 22.
    Figure 22. Security Certificate, Part 2
    Security Certificate, Part 2
  13. Accept the default values, or you can specify the port values. If you want to keep the old port values, you can update the port values using the old ones. Click Next, as shown in Figure 23.
    Figure 23. Port Values assignment
    Port Values assignmentNote: Record the important port numbers below, as you will use them later:
    • Administrative console port
    • SOAP connector port
  14. Double check the Profile creation information. If there are no errors, click Create, as shown in Figure 24.
    Figure 24. Profile Creation summary
    Profile Creation summary
  15. After the profile is created successfully, it will display a confirmation message. Click Finish to exit the Profile Creation wizard, as shown in Figure 25.
    Figure 25. Profile Creation Complete page
    Profile Creation Complete page

Migrate the WebSphere Application Server Network Deployment Manager from V5.1 to V7.0

  1. Save the current configuration by running the WASPreUpgrade script from the migration/bin directory of the WebSphere Application Server V7.0 utilities disk, which you must mount on the V5.6.1 machine as follows:
    WASPreUpgrade.sh backupDirectory currentWebSphereDirectory -machineChange true

    For example:

    bash-2.05# cd /software/WAS/disk1/migration/bin
    bash-2.05# ./WASPreUpgrade.sh /software/backup/WAS_backup /usr/WebSphere/
     DeploymentManagerV51 -machineChange true

    Note: You must specify –machineChange as true when you run the WASPreUpgrade command for the remote migration. The WASPreUpgrade command provides status to the screen and to the log files in the migration_specific_backup directory (for example, /software/backup/WAS_backup). After the command completes, the configuration backup file will be saved in the backup directory.

  2. Zip the backup directory, transfer the file to the Deployment Manager V7 machine, and extract it to the backup directory. Make sure the WC-non-root user can access the backup directory.
  3. On Deployment Manager V7, run the WASpostupgrade command to restore the old Deployment Manager configuration to the V7 profile with the WC-non-root user.
    WASPostUpgrade.sh backupDirectory -replacePorts true -keepDmgrEnabled true

    For example:

    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    bash-2.05$ ./WASPostUpgrade.sh /software/backup/WAS_backup 
    -replacePorts true -keepDmgrEnabled true

    Note: If you want to keep the old profile port values, specify the replacePorts as true and specify –keepDmgrEnabled as true when you run the WASPostUpgrade command in a remote Deployment Manager migration.

  4. Start the V7 migrated Deployment Manager with the WC-non-root user:
    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    bash-2.05$ ./startManager.sh
  5. Manually synchronize all the old federated nodes with the migrated Deployment Manager using the WC-non-root user. For example, run the sync command from <WAS>/bin on each WebSphere Application Server V5.1 node:
    SyncNode.sh deployment_manager_host deployment_manager_Soap_port

    For example:

    bash-2.05$ cd /usr/WebSphere/AppServer/bin
    bash-2.05$ ./syncNode.sh wci92.cn.ibm.com 8879

    Note: If you fail to do so, the nodes will not be able to communicate with the Deployment Manager and the migration will not be able to upgrade to the federated nodes.

  6. After synchronization, ensure that the EAR files on your WebSphere Application Server V5.1 nodes are still in the following location, WAS_installdir/installedApps/node_name/WC_demo.ear. If the files are no longer there, you need to manually restore the file backup in Step 2 in Backup the old clustered environment before migration.

Install WebSphere Application Server V7 on a remote node

For detailed steps, refer to Install WebSphere Application Server Network Deployment V7.0 on a remote Deployment Manager machine.

Create a WebSphere Application Server V7 profile on the remote node

  1. On the V7 node, repeat Step 1 to Step 3 in Create the WebSphere Application Server V7 Deployment Manager profile using the Profile Management tool to launch the Profile Management tool.
  2. Select Application server to create one application server profile and click Next, as shown in Figure 26.
    Figure 26. Environment selection
    Environment selection
  3. Select Advanced profile creation on the Profile Creation Options panel and click Next, as shown in Figure 27.
    Figure 27. Profile Creation options
    Profile Creation options
  4. Accept the default values on the optional application Deployment panel and click Next, as shown in Figure 28.
    Figure 28. Optional Application Deployment panel
    Optional Application Deployment panel
  5. On the Profile Name and Location panel, specify the profile name, for example, wcs99. Specify the profile directory, for example, /usr/IBM/WebSphere/AppServer/profiles/wcs99. Click Next as shown in Figure 29.
    Figure 29. Profile name and location
    Profile name and location
  6. On the Node and Host Names panel, input the node name. Note: The profile must have the same node name as V5.1 that is being migrated. Otherwise, the node migration will fail. Specify the server name and make sure the host name is correct. Click Next as shown in Figure 30.
    Figure 30. Node and Host Names panel
    Node and Host Names panel
  7. Repeat Step 10 to Step 15 in Create the WebSphere Application Server V7 Deployment Manager profile using the Profile Management tool to complete the profile creation.

Migrate WebSphere Application Server federated nodes from V5.1 to V7

  1. On the WebSphere Application Server V5.1 federated node, save the current configuration by running the WASPreUpgrade script from the migration/bin directory of the WebSphere Application Server V7.0 utilities disk, which you must mount on the Version 5.1 machine:
    WASPreUpgrade.sh backupDirectory currentWebSphereDirectory -machineChange true

    For example:

    bash-2.05$ cd /software/WAS/disk1/migration/bin
    bash-2.05$ ./WASPreUpgrade.sh /software/backup/WAS_backup/
    usr/WebSphere/AppServer -machineChange true

    Note: You must specify -machineChange as true when you run the WASPreUpgrade command for the remote migration. The WASPreUpgrade command provides status to the screen and to the log files in the migration_specific_backup directory (for example, /software/backup/WAS_backup).

  2. Zip the backup directory, transfer the zipped file to the remote V7 Application Server machine, and extract it to backup directory. Make sure the WC-non-root user can access the backup directory.
  3. On the Application Server V7 machine, run WASpostupgrade from the profiles/bin command to restore the old configuration to the V7 profile with the WC-non-root user:
    WASPostUpgrade.sh backupDirectory -replacePorts true

    For example:

    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/wcs99/bin
    bash-2.05$ ./WASPostUpgrade.sh /software/backup/WAS_backup 
    -replacePorts true

    If you want to keep the old profile port values, specify replacePorts as true.

  4. Make sure the WebSphere Application Server V7 Deployment Manager is started. If it is not, start the WebSphere Application Server V7 migrated Deployment Manager on the WebSphere Application Server V7 Deployment Manager machine:
    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    bash-2.05$ ./startManager.sh
  5. On the WebSphere Application Server V7 migrated node, manually synchronize all the migrated nodes with the migrated Deployment Manager. Run the sync command with the WC-non-root user from <WAS7>/profiles/bin:
    SyncNode.sh deployment_manager_host deployment_manager_Soap_port

    For example:

    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/wcs99/bin
    bash-2.05$ ./syncNode.sh wci92.cn.ibm.com 8879

Install WebSphere Commerce V7 on the WebSphere Commerce node

Before the WebSphere Commerce migration, you need to install all the software supported by WebSphere Commerce V7. For detailed steps, refer to Completing a custom installation using the WebSphere Commerce Installation Wizard in the WebSphere Commerce Information Center.

WebSphere Commerce migration on WebSphere Commerce node

To minimize the downtime for a WebSphere Application Server clustered environment, keep the previous WebSphere Commerce application running during the WebSphere Commerce migration. You need to:

  • Stop the WebSphere Application Server Deployment Manager V5.1 and all node agents for the old clustered environment.
  • Make sure the migrated WebSphere Application Server Deployment Manager is started and all the migrated node agents are stopped.

Launch the WebSphere Commerce Instance Migrator wizard

  1. Run the wcimServer command with the WC-non-root user from <WC7>/bin.
  2. Run wcimClient with the WC-non-root user from <WC7>/bin.
  3. Input the username and password. The default username is wcimadmin and the default password is wcimibm. Click OK to launch the WebSphere Commerce Instance Migrator wizard.
  4. Select WebSphere Commerce and click Launch to launch the WebSphere Commerce Instance Migrator (WCIM) wizard, as shown in Figure 31.
    Figure 31. WCIM wizard
    WCIM wizard

Database migration

  1. On the WCIM server panel, select Yes for “Is this a test run”, specify 561 for the previous version, and specify the xml instance file to be migrated, for example, /software/backup/instance/demo.xml. Click Next, as shown in Figure 32.
    Figure 32. WCIM server panel
    WCIM server panel

    If the previous version of WebSphere Commerce and the new version of WebSphere Commerce are not in the same machine, you need to manually copy the <instance.xml> from the old WebShpere Commerce V5.6.1 machine to the WebSphere Commerce V7 machine.

  2. On the WCIM database panel, specify the database type, for example, DB2. Click Next as shown in Figure 33.
    Figure 33. WCIM database panel
    WCIM database panel
  3. Manually back up the database and then check Yes for “Is the database backup completed” on the database backup panel. Click Next as shown in Figure 34.
    Figure 34. Database backup panel
    Database backup panel
  4. Manually restore the database since this is a test run. You need to run the database migration on the restored database. Check Yes for “Is the database restore completed” on the database restore panel. Click Next as shown in Figure 35.
    Figure 35. Database restore panel
    Database restore panel
  5. On the database Pre-check panel, specify if the database is remote or local. Specify the database name, database user, database password, database server hostname and server port, schema owner, and custom tablespace. Click Run as shown in Figure 36.
    Figure 36. Database pre-check panel
    Database pre-check panel
  6. When the database pre-check succeeds, click OK on the confirmation dialog box and to display the WebSphere Commerce migration panel. Click Run to run the WebSphere Commerce database migration, as shown in Figure 37.
    Figure 37. Database Migration panel
    Database Migration panel
  7. When the database migration succeeds, clickOK on the confirmation dialog box to display the WebSphere Commerce application migration panel.

Install the remote utility on the previous WebSphere Commerce V5.6.1 machine

Since WebSphere Commerce V7 and V5.6.1 are on different machines, you need to install the WebSphere Commerce remote utility on the V5.6.1 machine and back up the assets of the previous version with it for migration use:

  1. Launch the WebSphere Commerce installer from <WC7>/setup.sh to launch the panel, as shown in Figure 38.
    Figure 38. WebSphere Commerce installer launch panel
    WebSphere Commerce installer launch panel
  2. Click Next on the Installer Welcome panel, as shown in Figure 39.
    Figure 39. Installer Welcome panel
    Installer Welcome panel
  3. On the IBM License Acceptance panel, accept the license, and click Next, as shown in Figure 40.
    Figure 40. IBM License Acceptance panel
    IBM License Acceptance panel
  4. Specify the home directory of the non-root user. Click Next as shown in Figure 41.
    Figure 41. Home directory of non-root user
    Home directory of non-root user
  5. On the setup type panel, select Custom Installation and click Next, as shown in Figure 42.
    Figure 42. Setup type panel
    Setup type panel
  6. Since a previous version of WebSphere Commerce is installed, a warning message box indicates that a previous version of WebSphere Commerce has been detected. Click Yes to proceed with the installation. Click Next as shown in Figure 43.
    Figure 43. Warning message box
    Warning message box
  7. On the Components list panel, select Remote Websphere Commerce Management Utilities and click Next, as shown in Figure 44.
    Figure 44. Components list
    Components list
  8. On the WebSphere Commerce destination path panel, specify the WebSphere Commerce Server directory, for example, /opt/IBM/WebSphere/CommerceServer70. Click Next as shown in Figure 45.
    Figure 45. WebSphere Commerce destination path panel
    WebSphere Commerce destination path panel
  9. Specify the non-root user ID and group, for example, wasuser and wasgroup. Click Next as shown in Figure 46.
    Figure 46. Non-root user ID information
    Non-root user ID information
  10. If you want to generate a response file, check Create a response file. Click Next as shown in Figure 47.
    Figure 47. Create a response file
    Create a response file
  11. On the Installation summary panel, click Next, as shown in Figure 48.
    Figure 48. Installation summary information
    Installation summary information
  12. When the installation completes, click Finish to complete the remote utility installation on the previous version machine.

Backup application for migration on a previous version machine

  1. On the previous version machine, run the Backup command from <WC7>/bin with the WC-non-root user. For example:
    bash-2.05$ cd /usr/WebSphere/CommerceServer70/bin/
    bash-2.05$ ./wcimRemoteBackup.sh -tier app -action backup 
    -instancename demo -from 561
  2. Specify the previous WebSphere Commerce information:
    • For the previous WebSphere Commerce installation directory: /usr/WebSphere/CommerceServer561.
    • For the previous WebSphere Application Server installation directory, /usr/WebSphere/AppServer.
    • For the previous WebSphere Application Server version, for example: 5.1.
  3. The command will create a folder, WC_installdir/temp/zip, containing two files: backupwas.zip and backupwc_version_instance_name.zip.
  4. Copy the resulting folders to the WebSphere Commerce V7.0 target machine. 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.

Migrate the WebSphere Commerce application

  1. Return to the WebSphere Commerce application migration panel on the WebSphere Commerce V7.0 environment. Specify the WebSphere Commerce instance information on the WCIM Application panel:
    1. Select No for “Are the Websphere Commerce versions installed on the same machine”.
    2. Specify the previous WebSphere Application Server version, 5.1.
    3. Select No for “Is WebSphere Application server Global security is enabled” because you do not enable WebSphere Application Server Global security in this scenario.
    4. Since it is a clustered environment, select Yes for “Is it a cluster member”.
    5. Specify IBM HTTP Server for the Web server.
    6. Select Yes for the remote Web server.

    After all the information has been specified, then click Next as shown in Figure 49.

    Figure 49. WebSphere Commerce Instance Migrator migrate panel
    WebSphere Commerce Instance Migrator migrate panel
  2. On the Backup panel, specify Yes for “Application backup completed”, as shown in Figure 50.
    Figure 50. Application backup panel
    Application backup panel
  3. When the backup is completed, click OK to display the Application Migrate panel:
    1. Enter the remote Web server plugin installation directory, for example, /opt/IBM/HTTPserver/Plugins.
    2. Enter the WebSphere Application Server profile name, for example, demo.
    3. Enter the New Deployment manager hostname, for example, wci92.cn.ibm.com.
    4. Enter the soap port of the new Deployment Manager, for example, 8879.
    5. Make sure the database information is correct, such as if the database is remote or local, the database name, the database user, the database password, the database server hostname, and the server port.
    6. Click Run to run the WebSphere Commerce application migration, as shown in Figure 51.
    Figure 51. Application Migrate panel
    Application Migrate panel
  4. When the migration is completed, click OK to display the Application Configure panel:
    1. Specify the WebsServer host name, for example: pleander.cn.ibm.com.
    2. Specify the Web server installation directory, for example: /opt/IBM/HTTPServer.
    3. Specify the remote configuration path, for example: /opt/IBM/HTTPServer/imt60.
    4. Specify the FTP server hostname, for example: pleander.cn.ibm.com.
    5. Specify the FTP server port, user ID, and password. Note: Ensure that the ftp server is running. You can logon with the user and password you used above.
    6. Make sure the database information is correct.
    7. Click Run to configure the WebSphere Commerce application, as shown in Figure 52.
      Figure 52. Application Migration panel
      Application Migration panel
  5. When the application configuration completes, click OK on the confirmation dialog box.

Synchronize all the federated nodes to sync the migrated application among all nodes

  1. Ensure the migrated Deployment Manager is started. If not, start it by running the command startManager under <WAS7>/<DMGRprofile>/bin/:
    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    bash-2.05$ ./startManager.sh
  2. On all the migrated additional nodes, run the sync command from <WAS7>/<profileName>/bin, syncNode.sh deployment_manager_host deployment_manager_Soap_port.

    For example:

    bash-2.05$ cd /usr/IBM/WebSphere/AppServer/profiles/wcs99/bin
    bash-2.05$ ./syncNode.sh wci92.cn.ibm.com 8879
  3. Start the node agent on the migrated additional nodes.

Configure the Web server

  1. Regenerate the Web server plug-in for your Web server:
    1. Log on to the WebSphere Application Server Network Deployment Administration Console server, for example, http://hostname:9090/admin.
    2. Expand Servers > WebServers.
    3. Select webserver1 and click Generate Plug-in to generate the plugin-cfg.xml file for the Web server.
    4. Copy the updated plugin-cfg.xml file to your Web server machine and update the path to the plugin-cfg.xml file in the Web server configuration file on the Web Server node.
    5. Restart your Web server.
  2. If you are using a remote webserver, copy the following file from a WebSphere Commerce node to your Web server directory: WC_profiledir/installedApps/cell_name/WC_instance_name.ear.

The destination path on your Web server should be the same as the source. If the directories do not exist, create them.

Define the JDBC driver path for all federated nodes

  1. If they are not started, start the node agent on each system managed by WebSphere Application Server Network Deployment.
  2. If it is not started, start the Deployment Manager.
  3. Open the WebSphere Application Server Deployment Manager Administrative Console. For example, http://hostname:9090/admin.
  4. In the Navigation area, expand Environment and select WebSphere Variables.
  5. Select Browse Nodes and choose the node that you want to configure. You must configure all nodes that run WebSphere Commerce. Click OK.
  6. Click the link for the variable that represents your database type. The defaults are listed below:
    DB2_JDBC_DRIVER_PATH 
    ORACLE_JDBC_DRIVER_PATH
  7. In the Value field, enter the path to the appropriate JDBC provider. Do not enter the name of the .jar file in this field. This value requires the directory path only. For example:
    DB2_installdir/java 
    Oracle_installdir/jdbc/lib
  8. Click OK.
  9. Click Review to save your changes.
  10. Select Synchronize changes with Nodes to ensure that the Deployment Manager profile immediately synchronizes the configuration changes with the other nodes.
  11. Click Save.
  12. Click OK.
  13. Log out of the WebSphere Application Server Deployment Manager Administrative Console.

Start the migrated cluster

  1. Log on to the WebSphere Application Server Network Deployment Administration Console server.
  2. Expand Servers > Clusters.
  3. Check the cluster name, for example, WC_cluster and click Start.
  4. After the cluster migration is completed, you can access following URLs to make sure the WebSphere Commerce cluster has migrated successfully:
    https://hostname:8000/accelerator
    https://hostname:8002/adminconsole
    https://hostname:8004/orgadminconsole

Restore the previous clustered environment

If you need to restore the WebSphere Application Server cluster assets you backed up in Step 1 in Back up the old clustered environment before migration:

  1. Restore the following file into your WebSphere Application Server V5.1 installation:
    WAS_installdir/config/cells/cell_name/nodes/node_name/servers/instance_name/
     server.xml
  2. Restore your node configuration on every old node by running the restoreConfig command from WAS_installdir/bin.
  3. Sync the old nodes with the old Deployment Manager:
    1. Open a command line on your old installation and change to the WAS_installdir\bin directory.
    2. Run the syncNode command with the WC-non-root user:
      ./syncNode.sh deployment_manager_host deployment_manager_Soap_port
  4. Ensure that your store assets are still in the old WebSphere Commerce node, in the following location:
    WAS_installdir/installedApps/node_name/WC_instance_name.ear/Store.war

If this file is not present, you need to manually restore your published store assets from the backup files.


Conclusion

Part 1 demonstrated how to install WebSphere Application Server, remotely migrate WebSphere Application Server Deployment Manager from V5.1 to V7.0, remotely migrate federated nodes from V5.1 to V7.0, migrate the WebSphere Commerce database from V5.6.1 to V7.0, and migrate a WebSphere Commerce instance from V5.6.1 to V7.0 in a clustered environment.

Part 2 will introduce how to migrate WebSphere Application Deployment Manager from V6.0 to V7.0 locally, locally migrate federated nodes from V6.0 to V7.0, migrate the WebSphere Commerce database from V6.0 to V7.0, and migrate a WebSphere Commerce instance from V6.0 to V7.0 in a clustered environment.

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=492767
ArticleTitle=Migrating a WebSphere Commerce clustered environment to V7, Part 1: Migrating V5.6.1 to V7.0
publish-date=06022010