Federating additional WebSphere Commerce nodes

Federating any additional WebSphere Commerce nodes that you might have created allows you the option to manage multiple WebSphere Commerce instances from a single console. Review this information if your console environment will be used for managing multiple WebSphere Commerce instances.

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

• Federating WebSphere Commerce

• Prepare additional nodes

To federate an additional WebSphere Commerce node into a deployment manager cell:

1. On the WAS ND machine, start the deployment manager profile.

   • AIX|Linux|Solaris|Windows:

     Start the Deployment Manager

   • I5/OS:

     Start the Deployment Manager

2. AIX|Linux|Solaris|Optional: Create the WAS non-root user and group if they do not already exist on the WebSphere Commerce node. Follow the instructions in the Creating required WAS users and groups section of the WebSphere Commerce Installation Guide.

3. 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.

      • AIX|Linux|Solaris|Windows:

        WAS Best Practices

      • I5/OS:

        WAS Best Practices

   3. Save the file, and exit.

4. Ensure that the system clock on your WebSphere Commerce node and your WAS ND node are synchronized within 5 minutes of each other and are set to the same time zone. If they are not, federation will fail.

5. On the WebSphere Commerce node:

   1. AIX|Linux|Solaris|Log on as the non-root user.

   2. I5/OS|Start a QShell session by typing QSH at the i5/OS command prompt.

   3. Federate the WebSphere Commerce application server into the deployment manager cell by issuing the following command:

      • AIX|Linux|Solaris|WC_profiledir/bin/addNode.sh deployment_manager_host_name SOAP_port -includeapps

      • I5/OS:

        WC_profiledir/bin/addNode deployment_manager_host_name SOAP_port -includeapps

      • Windows: WC_profiledir/bin/addNode.bat deployment_manager_host_name SOAP_port -includeapps

      
      

      Your WebSphere Commerce instance is stopped automatically during the federation process. The command is shown on multiple lines for display purposes only, enter the command on one line.

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

      WC_profiledir

      This directory is created for the WAS profile that is used by a WebSphere Commerce instance.

      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.

      -includeapps

      When federating a WebSphere Commerce profile that contains a WebSphere Commerce instance, include this parameter to ensure that the WebSphere Commerce application (EAR) file is transferred to the new configuration.

   
   

   AIX|Linux|Solaris|After federating a WebSphere Application Server profile, the node agent must be managed by the non-root user. For more information, refer to the following topic in the WAS Information Center:

   • Using a non-root user to run an application server and node agent

6. 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:

      • AIX|Linux|Solaris|Windows:

        WAS Best Practices

      • I5/OS:

        WAS Best Practices

   3. Save the file, and exit.

7. If you are federating a profile that contains a WebSphere Commerce instance, recreate the cell level documents on your deployment manager node. To recreate these documents, complete the following steps on the WebSphere Commerce node:
   

   • Ensure your WebSphere Commerce instance is started.

   • This step is not required if you are adding a WAS node that does not contain WebSphere Commerce information

   1. AIX|Linux|Solaris: Switch to the WebSphere Commerce non-root user by running the following command in a terminal window: su - WC_non_root_user

   2. I5/OS:

      Start a QShell session by typing QShell at the i5/OS command prompt.

   3. Run the following command:

      AIX|Linux|

      WC_installdir/bin/config_ant.sh -DinstanceName=instance ReconfigureCell
      
      
      

      

      WC_installdir/bin/config_ant.sh -DinstanceName=instance ReconfigureCell
      
      
      

      

      WC_installdir/bin/config_ant.bat -DinstanceName=instance ReconfigureCell
      
      
      

8. If you had enabled security before you federated your WebSphere Commerce application, enable security again.

9. If you had enabled automatic Web server configuration file (plugin-cfg.xml) propagation before federating, configure it again. Running the addNode command removes the Web server definition.

10. If you are federating a non-WebSphere Commerce profile into the deployment manager cell:

    1. AIX|Linux|Solaris|Log on as the non-root user.

    2. I5/OS|Start a QShell session by typing QShell at the i5/OS command prompt.

    3. Federate the application server into the deployment manager cell by issuing the following command:

       • AIX|Linux|Solaris|WAS_profiledir/bin/addNode.sh deployment_manager_host_name SOAP_port -includeapps

       • I5/OS|WAS_profiledir/bin/addNode deployment_manager_host_name SOAP_port -includeapps

       • Windows: WAS_profiledir/bin/addNode.bat deployment_manager_host_name SOAP_port -includeapps

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

       WAS_profiledir

       This directory is created for the WAS profile.

       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.

       -includeapps

       When federating a WebSphere Commerce profile that contains a WebSphere Commerce instance, include this parameter to ensure that the WebSphere Commerce application (EAR) file is transferred to the new configuration.

11. Regenerate the Webserver plug-in for your Web server.

    1. Log on the the WAS ND
       Administration Console server.

    2. Expand Servers > WebServers.

    3. Select webserver1 and click Generate Plug-in to generate the plugin-cfg.xml file for the Web server.

12. Copy the updated plugin-cfg.xml file to your Web server machine:

    • AIX|Linux|Solaris|Windows:

      Communicating with Web servers

    • I5/OS:

      Communicating with Web servers
      

      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.

13. Update the path to the plugin-cfg.xml file in the Web server configuration file on the WebSphere Commerce node agent. For more information refer to the WebSphere Commerce Installation Guide.

14. Restart your Web server.