Migrating WebSphere Commerce in a clustered environment

Complete the following steps to migrate your WebSphere Commerce clustered environment. Many of the steps are links to the WebSphere Application Server Network Deployment Version 7.0.0.3, or higher version 7.0 fix pack Information Center, with detailed recommended settings relevant to WebSphere Commerce.

Before you begin

Ensure your WebSphere Application Deployment Manager and all federated node agents for WebSphere Commerce version 5.6.1 or 6.0 are stopped.
If WebSphere Application Server Global Security is enabled, disable it before you migrate your application.
Review the following white papers for information about typical cluster migration scenarios:
- Migrating a WebSphere Commerce clustered environment to V7, Part 1: Migrating V5.6.1 to V7.0
- Migrating a WebSphere Commerce clustered environment to V7, Part 2: Migrating V6.0 to V7.0

Procedure

Before you migrate a WebSphere Application Server Version 5.1, Version 6, or Version 6.1 deployment manager, use the backupConfig command or your own preferred backup utility to back up your existing configuration so that you can restore it to its previous state after migration. Ensure that you back up your EAR files and configuration files on all of your nodes:
1. Back up the configuration by running the backupConfig command that is provided by WebSphere Application Server.
  - backupConfig command
  Important: Before you migrate a WebSphere Application Server Version 5.1, Version 6, or Version 6.1 node, use the backupConfig command or your own preferred backup utility to back up your existing configuration if you want to be able to restore it to its previous state after migration.
2. Back up the following EAR file manually:
  - WAS_installdir/profiles/profile_name/installedApps/node_name/WC_demo.ear
3. Back up the following file all servers on your old nodes:
  - WAS_installdir/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name/server.xml
Install WebSphere Application Server Network Deployment Version 7.0.0.3, or higher version 7.0 fix pack in the deployment manager machine and migrate your old deployment manager, following the WebSphere Application Server Network Deployment Version 7.0.0.3, or higher version 7.0 fix pack migration guide.
Note: It is recommended that you use the same user type (root user or non-root user) to run WebSphere Application Server. If you change the user type to run WebSphere Application Server Network Deployment Version 7.0.0.3, or higher version 7.0 fix pack, complete one of the following tasks before migration:
- Migrating root configurations to non-root
- Migrating non-root configurations to root
1. If your new and old versions of WebSphere Application Server are installed on the same machine, migrate your deployment manager using the Migration wizard.
  Important: The following settings are recommended when you migrate your profile:
  - When you are creating a profile, the cell name must match the cell name from your Version 5.1, Version 6, or Version 6.1 configuration.
  - Select Migrate and install the applications in application migration settings.
  - Select Install the applications in the default directory of the target version for Directory to install the applications.
  - Check Do not disable the deployment manager of the previous version in the Deployment manager options.
  - Check Migrate to support script compatibility.
2. If your new and old versions of WebSphere Application Server are on remote machines, migrate your deployment managers using migration tools.
  Important: The following settings are mandatory when you migrate your profile:
  - As the WebSphere Commerce non-root user, increase the file handle limit with the following command:
    ulimit -n 8192 for the WASPostUpgrade command
  - When you are creating a profile, the cell name must match the cell name from your Version 5.1, Version 6, or Version 6.1 configuration.
  - You must specify the parameter machineChange=true for the WASPreUpgrade command.
  - It is recommended that you specify the parameters replacePorts=true and keepDmgrEnabled=true for the WASPostUpgrade command.
Sync all of your old nodes with the migrated deployment manager:
1. Make sure that the migrated deployment manager is started.
2. Open a command line on each old node and change to the following directory:
  - WebSphere Application Server Version 5.1: WAS_installdir\bin
  - WebSphere Application Server Version 6:WAS_installdir\profiles\profile_name\bin
3. Run the syncNode command:
```
syncNode.bat deployment_manager_host deployment_manager_Soap_port
```
```
syncNode.sh deployment_manager_host deployment_manager_Soap_port
```
Ensure that the EAR files on your nodes are still in the following location:
- WAS_installdir/profiles/profile_name/installedApps/node_name/WC_demo.ear
If the files are no longer there, you must manually restore the files.
Migrate nodes from the old version of WebSphere Application Server to version 7 using the WebSphere Application Server migration utility.
Note: Migrate only the additional nodes. Do not migrate the primary node, which is migrated by WebSphere Commerce.
- The primary node is the node where the WebSphere Commerce product is installed.
- An extra node is any node that does not have the WebSphere Commerce product that is installed on it, but does have WebSphere Application Server installed.
1. startManager command
2. If your new and old versions of WebSphere Application Server are installed on the same machine, migrate your node using migration tools.
  Important: The following settings are recommended when you migrate your profile:
  - When you are creating a profile, the node name must match the node name from your Version 5.1, Version 6, or Version 6.1 configuration.
  - Select Migrate and install the applications in application migration settings.
  - Select Install the applications in the default directory of the target version for Directory to install the applications.
  - Check Migrate to support script compatibility.
  - To create a WebSphere Application Server Version 7.0 profile on the Version 7.0 machine, select Custom Profile. You can use either the Profile Management Tool or the manageprofiles command
3. If your new and old versions of WebSphere Application Server are on remote machines, migrate your node to a version 7 federated s using migration tools
  Important: The following settings are mandatory when you migrate your profile:
  - As the WebSphere Commerce non-root user, increase the file handle limit with the following command:
    ulimit -n 8192 for the WASPostUpgrade command
  - When you are creating a profile, the node name must match the node name from your Version 5.1, Version 6, or Version 6.1 configuration.
  - You must specify the parameter machineChange=true for the WASPreUpgrade command.
Sync all of your migrated nodes with the migrated deployment manager.
Note: Make sure you completed all the backup activities from step 1. The following steps modify your configuration and are not reversible.
1. Make sure that the migrated deployment manager is started.
2. Open a command line on the migrated extra nodes and change to the following directory:
  - WebSphere Application Server Version 7: WAS_installdir\profiles\profile_name\bin
3. Run the syncNode command:
```
syncNode.bat deployment_manager_host deployment_manager_Soap_port
```
```
syncNode.sh deployment_manager_host deployment_manager_Soap_port
```
Install WebSphere Commerce using a custom installation.
Install WebSphere Commerce using a custom installation.
Install WebSphere Commerce using a custom installation.
Install WebSphere Commerce using a custom installation.
Install WebSphere Commerce using a custom installation.
startManager command
Migrate your WebSphere Commerce database and application using the Migration wizard on the WebSphere Commerce node.
Start all Version 7 node agents.
Redefine the JDBC driver path.
Regenerate the web server plug-in for your web server.
1. Log on the WebSphere Application Server Network Deployment Administration Console server.
2. Expand Servers > Server Types > Web servers.
3. Select webserver1 and click Generate Plug-in to generate the plugin-cfg.xml file for the web server.
Copy the updated plugin-cfg.xml file to your web server:
- Communicating with web servers
- Communicating with web servers
Update the path to the plugin-cfg.xml file in the web server configuration file on the web server.
Restart your web server.
Copy the following file from a WebSphere Commerce node to your web server directory:
- WAS_installdir/profiles/profile_name/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.
If you must restore the WebSphere Application Server cluster assets that you backed up in step 1, complete the following steps:
1. Restore the following file into your WebSphere Application Server version 5.1 installation:
  - WAS_installdir/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name/server.xml
2. Restore your node configuration on every old node
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:
```
syncNode.bat deployment_manager_host deployment_manager_Soap_port
```
```
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/profiles/profile_name/installedApps/node_name/WC_instance_name.ear/Stores.war
  If this file is not present, you must manually restore your published store assets.
Attention: After you migrate your clustered environment, you might see exceptions that begin with the following lines in your SystemOut.log file:
```
[8/5/09 0:03:53:993 CST] 0000000a DeployedAppli W WSVR0215W: Starting application, ManagementEJB, failed. The application is not installed.
[8/5/09 0:03:53:995 CST] 0000000a ApplicationMg W WSVR0100W: An error occurred initializing, ManagementEJB
com.ibm.ws.exception.ConfigurationWarning: No cluster target found for application, ManagementEJB
at com.ibm.ws.runtime.component.DeployedApplicationImpl.initialize(DeployedApplicationImpl.java:506)
```
This exception can safely be ignored. It is a known WebSphere Application Server issue and has no impact on WebSphere Commerce functionality.
Optional: If you disabled WebSphere Application Server Global Security before you migrated the application, you can re-enable it.