Federating additional WebSphere Commerce nodes

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

Before you begin

Ensure the following tasks are completed before completing the steps in this section:

Procedure

On the WebSphere Application Server Network Deployment machine, start the deployment manager profile.
- Start the Deployment Manager
Optional: Create the WebSphere Application Server non-root user and group if they do not already exist on the WebSphere Commerce node.
Before federating the WebSphere Commerce application server node into the deployment manager cell, set the SOAP connection timeout to 0. To adjust the SOAP timeout setting 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.
  - WebSphere Application Server Best Practices
3. Save the file, and exit.
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 they are not, federation will fail.
If you are federating a non-WebSphere Commerce profile into the deployment manager cell:
1. Log on as the non-root user.
2. Federate the application server into the deployment manager cell by issuing the following command:
  - WC_profiledir/bin/addNode.sh deployment_manager_host_name SOAP_port
  - WC_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
  
  This is the fully-qualified host name of the deployment manager node.
  
  SOAP_port
  
  This is the SOAP port on which the deployment manager listens. This port number is defined when creating the deployment manager profile. The default deployment manager port is 8879.
You must reset the SOAP connection timeout to the original value. To adjust the SOAP timeout setting 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, refer to:
  - WebSphere Application Server Best Practices
3. Save the file, and exit.
If you had enabled security before you federated your WebSphere Commerce application, you must enable security again.
If you had enabled automatic Web server configuration file (plugin-cfg.xml) propagation before federating, you must configure it again. Running the addNode command removes the Web server definition.
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 > WebServers.
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 machine:
- Communicating with Web servers
- Starting or stopping an application server under WebSphere Application Server Network Deployment
  Note: The updated plugin-cfg.xml file must be copied to the Remote_configdir/httpconf directory on the remote Web server machine. Where Remote_configdir is the Remote Configuration Directory specified during instance creation.
Update the path to the plugin-cfg.xml file in the Web server configuration file on the WebSphere Commerce node agent.
Restart your Web server.