Prepare additional nodes

+

Search Tips   |   Advanced Search

Adding an additional node to your topology is a required step when configuring horizontal clustering.

This section applies only to clustering with horizontal cluster members.

As part of the cluster that runs the WebSphere Commerce application, install WAS, and your database client on each machine that will be part of the cluster containing the horizontal cluster members.

To prepare a new node as a horizontal cluster member:

  1. AIX|Linux|Solaris|(DB2) Install your database client software on the machine 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 as outlined in the WebSphere Commerce Installation Guide.

  3. (DB2) Ensure that you can access the WebSphere Commerce database from the new WebSphere Commerce node.You must catalog the remote WebSphere Commerce database node and the remote WebSphere Commerce database. For instructions, refer to the DB2 Universal Database for iSeries documentation. For help in ensuring access to the remote WebSphere Commerce database, refer to your Oracle Database documentation. For more information about accessing a remote database refer to 'Instance creation requirements using a remote database' section of the WebSphere Commerce Installation Guide.

  4. AIX|Linux|Solaris|Create the WAS non-root user and group if they do not already exist on the new node. Follow the instructions in the WebSphere Commerce Installation Guide.

  5. AIX|Linux|Solaris|Ensure that the WebSphere Commerce non-root user has the permission to access your the 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
    
    
    

  6. Install the WAS on the machine that is hosting the horizontal cluster member.

  7. Ensure you have the correct WAS level, and fixes installed, on the machine that is hosting the horizontal cluster member. Refer to Recommended fixes for WebSphere Commerce.

  8. Create a WAS profile.

  9. AIX|Linux|Solaris|Update the ownership and permissions of the WAS profile.

  10. Federating additional WebSphere Commerce nodes.



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

 

Related Concepts


WAS ND clustering mechanism
WebSphere Commerce federation

 

Related tasks


Cluster with vertical cluster members
Cluster with horizontal cluster members
Create the WebSphere Commerce cluster
Define the JDBC driver path
Add additional cluster members
Start or stopping a WebSphere Commerce cluster
Remove a cluster member