Federating more WebSphere Commerce nodes

Federating more nodes is necessary to be able to create the cluster.An extra WebSphere Commerce node is a WebSphere Application Server node that you prepared according to the steps in Preparing more nodes.

Procedure

  1. On the WebSphere Application Server Network Deployment machine, start the deployment manager profile.
  2. Optional: LinuxAIX Create the WebSphere Application Server non-root user and group if they do not exist on the WebSphere Commerce node.
  3. Before you federate the WebSphere Commerce application server node into the deployment manager cell, set the SOAP connection timeout to 0. To adjust the SOAP timeout value, complete the following steps on the WebSphere Commerce node:
    1. Open the following file in a text editor: 
      WC_profiledir/properties/soap.client.props
    2. Search for the com.ibm.SOAP.requestTimeout entry. Record the existing value, and change the value to 0.
      For example, com.ibm.SOAP.requestTimeout=0.

      For more information, see WebSphere Application Server Best Practices

    3. Save the file, and exit.
  4. Ensure that the system clock on your WebSphere Commerce node and your WebSphere Application Server Network Deployment node are synchronized within 5 minutes of each other and are set to the same time zone. If the time zones are not set, federation fails.
  5. If you are federating a non-WebSphere Commerce profile into the deployment manager cell, then complete the following steps.
    1. LinuxAIX Log on as the non-root user.
    2. Federate the application server into the deployment manager cell by issuing the following command:
      • LinuxAIXWC_profiledir/bin/addNode.sh deployment_manager_host_name SOAP_port
      • WindowsWC_profiledir/bin/addNode.bat deployment_manager_host_name SOAP_port

      The variables and parameters in the command are defined as follows:

      deployment_manager_host_name
      The fully qualified host name of the deployment manager node.
      SOAP_port
      The SOAP port on which the deployment manager listens. This port number is defined when you create the deployment manager profile. The default deployment manager port is 8879.
  6. You must reset the SOAP connection timeout to the original value. To adjust the SOAP timeout value, complete the following steps on the WebSphere Commerce node:
    1. Open the following file in a text editor: 
      
WC_profiledir/properties/soap.client.props
    2. Search for the com.ibm.SOAP.requestTimeout entry. Reset the entry to the original value. For more information, see WebSphere Application Server Best Practices.
    3. Save the file, and exit.
  7. If you enabled security before you federated your WebSphere Commerce application, you must enable security again.