Administer > Manage instances > WCS instance > Cluster with horizontal cluster members


Federate additional WebSphere Commerce nodes

Overview

Federating additional WebSphere Commerce nodes allows one to manage multiple WCS instances from a single console.

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


Procedure

  1. On the dmgr machine, start the deployment manager profile.

  2. On the WebSphere Commerce node, create the non-root user and group.

  3. Set the SOAP connection timeout to 0.

    Edit...

    WC_PROFILE/properties/soap.client.props

    ...and set com.ibm.SOAP.requestTimeout to 0...

    com.ibm.SOAP.requestTimeout=0

  4. Verify the system clock on the WebSphere Commerce node and the 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, log on as the non-root user.

  6. Federate the WebSphere Commerce application server into the deployment manager cell...

    WC_PROFILE/bin/addNode.sh dmgr_host SOAP_port -includeapps

    Your WCS instance is stopped automatically during the federation process.

    The default deployment manager port is 8879.

    After federating a WAS profile, the node agent must be managed by the non-root user.

  7. Reset SOAP connection timeout to original value.

  8. To federate a profile containing a WCS instance, recreate the cell level documents on the deployment manager node.

    1. Switch to the non-root user...

      su - WC_non_root_user

    2. Start WCS instance

    3. Run...

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

  9. If you had enabled security before you federated the WebSphere Commerce application, enable security again.

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

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

  12. Regenerate the Webserver plug-in for the Web server.

    1. Log on to the WAS ND console.

    2. Expand....

      Servers | Server Types | WebServers

    3. Generate plugin-cfg.xml by selecting webserver1 and clicking...

      Generate Plug-in

  13. Copy the updated plugin-cfg.xml file to...

    WebServer_Host:/REMOTE_CONFIGDIR/httpconf
    ...where REMOTE_CONFIGDIR is the Remote Configuration Directory specified during instance creation.

  14. Update the path to the plugin-cfg.xml file in the Web server configuration file on the WebSphere Commerce node agent.

  15. Restart the Web server.


+

Search Tips   |   Advanced Search