Preparing more nodes

Adding an extra node to your topology is a necessary step if you want to configure horizontal clustering.

About this task

The following information applies to clustering with horizontal cluster members only.

As part of the cluster that runs the WebSphere Commerce application, you must install WebSphere Application Server, and your database client on each machine that will be part of the cluster that contains the horizontal cluster members.

To prepare a new node as a horizontal cluster member:

Procedure

  1. LinuxAIXDB2 Install your database client software on the machine that is hosting the horizontal cluster member. The installation wizard can install the DB2 Administration Client on the machine.
  2. Oracle Install the Oracle components for an Oracle client machine. Ensure that you can access the WebSphere Commerce database from the new WebSphere Commerce node. For help in ensuring access to the remote WebSphere Commerce database, refer to your Oracle database documentation.
  3. LinuxAIX Create the WebSphere Application Server non-root user and group if they do not exist on the new node.
  4. LinuxAIX Ensure that the WebSphere Commerce non-root user has the permission to access your WebSphere Commerce database by adding the following to the WebSphere Commerce non-root user's profile: 
    if [ -f "/home/db2_user/sqllib/db2profile" ]; then 
. /home/db2_user/sqllib/db2profile
fi
  5. Install the WebSphere Application Server on the machine that is hosting the horizontal cluster member.
  6. Ensure that you have the correct WebSphere Application Server level, and fixes installed, on the machine that is hosting the horizontal cluster member.
  7. Verify the default WebSphere Application Server SDK level.
    1. Go to the WAS_installdir/bin folder.
    2. Run the following command.
      • LinuxAIX./managesdk.sh -getNewProfileDefault
      • Windowsmanagesdk.bat -getNewProfileDefault
      • For IBM i OS operating system
        1. managesdk -getNewProfileDefault
        2. managesdk -getCommandDefault
    3. If the default WebSphere Application Server SDK level is not 1.7, then run the following command to set to version 1.7.
      • LinuxAIX./managesdk.sh -setNewProfileDefault -sdkName 1.7_64
      • Windowsmanagesdk.bat -setNewProfileDefault -sdkName 1.7_64
      • For IBM i OS operating system
        1. managesdk -setNewProfileDefault -sdkname 1.7_64
        2. managesdk -setCommandDefault -sdkname 1.7_64
  8. Create a WebSphere custom profile.

Results

Important:

Do not create a WebSphere Commerce instance on the new WebSphere Commerce node.