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


Federate WebSphere Commerce

Overview

Federating the WebSphere Commerce environment allows you to...

An existing Commerce instance is required for this task.

If you create additional instances after you complete this federation process, you can manually add any new instance to the dmgr profile by following the steps in this task. When a new instance is created, the configuration manager does not automatically federate to the dmgr profile.


Procedure

  1. Create a WAS Deployment Manager profile on the WAS ND machine.

  2. On the WAS ND machine, start the dmgr profile.

  3. Create the WAS non-root user and group.

  4. Update the addNode script...

    1. Log on to the Commerce node as root and edit...

      cd WAS_HOME/bin/
      ./addNode.sh

    2. In the text file, find the following line of text:

      • "$JAVA_HOME"/bin/java \

      • (Windows) "%JAVA_HOME%\bin\java" -Dcmd.properties.file=%TMPJAVAPROPFILE% %WAS_DEBUG% %WAS_TRACE% %CONSOLE_ENCODING% "%CLIENTSOAP%" "%JAASSOAP%" "%CLIENTSAS%" "-classpath" "%WAS_CLASSPATH%" "-Dws.ext.dirs=%WAS_EXT_DIRS%" "-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager" "-Djava.util.logging.configureByServer=true" %USER_INSTALL_PROP% "-Dwas.install.root=%WAS_HOME%" "-DWAS_HOME=%WAS_HOME%" "com.ibm.ws.bootstrap.WSLauncher" "com.ibm.ws.management.tools.NodeFederationUtility" "%CONFIG_ROOT%" "%WAS_CELL%" "%WAS_NODE%" %*

    3. Complete one of the following steps:

      • Insert the following below the "$JAVA_HOME"/bin/java \ line of text:

        -Xms256m -Xmxmax_allowed \

        For example, one of the following lines can be inserted:

          -Xms256m -Xmx1024m \ indicates that the max_allowed is set to 1024m
          -Xms256m -Xmx12288k \ indicates that the max_allowed is set to 12288k

      • (Windows) Insert the following between the "-DWAS_HOME=%WAS_HOME%" and "com.ibm.ws.bootstrap.WSLauncher" entries:

        -Xms256m -Xmxmax_allowed

        For example, one of the following lines can be inserted:

          -Xms256m -Xmx1024m indicates that the max_allowed is set to 1024m
          -Xms256m -Xmx12288k indicates that the max_allowed is set to 12288k

      The max_allowed parameter represents the Java maximum heap size value allowed by the operating system. This value must a multiple of 1024. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.

    4. Save the changes and exit the text editor.

    5. Log on to the WAS ND dmgr Administrative Console.

    6. Expand...

      System Administration | Deployment Manager | Java and Process Management | Process Definition | Java Virtual Machine

    7. Change the Maximum Heap Size value to the maximum value supported by the operating system. For example, 1024 MB. You can reduce this number once you have completed the federation process.

    8. Restart the Deployment Manager.

  5. Set the SOAP connection timeout to 0.

    To adjust the SOAP timeout setting complete the following steps on the Commerce node:

    1. Edit...

      WC_PROFILE/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.

    3. Save the file, and exit.

  6. Verify the system clocks on the 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.

  7. On the Commerce node:

    1. Log on as the non-root user.

    2. Federate the commerce application server into the dmgr cell...

        cd WC_PROFILE/bin/
        ./addNode.sh dmgr_host SOAP_port -includeapps

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

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

  8. Reset the SOAP connection timeout to the original value.

    1. Edit...

      WC_PROFILE/properties/soap.client.props

    2. Search for the com.ibm.SOAP.requestTimeout entry. Reset the entry to the original value.

    3. Save the file, and exit.

  9. Copy...

    WebServerHost:/path/to/plugins/bin/configureweb_server_name.sh

    ...to...

    WAS_HOME/bin/

  10. Run the script file you copied:

    cd WAS_HOME/bin/
    ./configureweb_server_name.sh -user configAdminUser -password configAdminPassword

  11. If you are federating a profile that contains a Commerce instance, recreate the cell level documents, such as a remote Web server, on the Websphere Commerce node.

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

    To recreate these documents, on the Commerce node:

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

      su - WC_non_root_user

    2. Run the following command:

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

      On Windows, if you get the the following error...

      java.io.IOException: java.io.IOException

      ...the system cannot find the configuration file.

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

  13. If you had enabled automatic Web server configuration file propagation of plugin-cfg.xml before federating, configure it again.

    Running the addNode command removes the Web server definition.

  14. Regenerate the Web server plug-in for the Web server.

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

    2. Expand...

      Servers | WebServers

    3. To generate the plugin-cfg.xml file for the Web server, select webserver1 and click...

      Generate Plug-in

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

  16. Update the path to the plugin-cfg.xml file in the Web server configuration file on the Web server machine.

  17. Restart your Web server.


Results

Once you have federated the Commerce application server nodes into a dmgr cell, you can start and stop Commerce...


See Also

  1. Change the process execution properties
    Altering the process execution properties is a required step in the federation process.

  2. Remove an application server node from a cell
    Changes to the Commerce typology might require the removal of nodes from a cell. Ensure that steps are followed to successfully complete the removal.

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

  4. Commerce federation
    Federating your Commerce environment requires WAS ND. After you federate, you can configure clustering.


+

Search Tips   |   Advanced Search