Set up Member Manager in a clustered environment

The steps on this page describe how to set up Member Manager in a clustered environment.

Prerequisite

  1. WAS ND is installed on a node in your network, following the product installation instructions. This machine will be referred to as DM in the examples on this page.

  2. WebSphere Member Manager is installed on (at least) 2 nodes on your network, following the instructions in Install Member Manager. These machines will be referred to as WMM01 and WMM02 in the examples on this page.

  3. For WMM02, the configuration of WebSphere Member Manager should be same as the configuration of WMM01. If you are using LDAP, all nodes should point to the same physical LDAP server with the same settings. If you are using database, all nodes should connect to the same database instance.


To configure Member Manager in a Clustered Environment:

  1. Add the nodes to the cell:

    1. On DM01, start the Deployment Manager
      cd <WAS_ND_HOME>\bin
      startManager
      
      
      

    2. Stop server1 on all nodes
      cd  <WAS_HOME>\bin
      stopServer server1
      
      
      

    3. On WMM01, add the node to the cell with the following commands
      cd  <WAS_HOME>\bin
      addNode <DM_hostname> 8879 -includeapps
      
      
      

    4. On WMM02, add the node to the cell with the following commands
      cd  <WAS_HOME>\bin
      addNode <DM_hostname> 8879
      
      
      

      Do not include the -includeapps parameter for the second node or the rest of the nodes. All applications required for WMM02 were already included by WMM01.

    5. When the process is done you should get the following message
      Node node has been successfully federated.
      
      
      

    6. You can see the new nodes in the ND console by expanding System Administration and clicking Nodes. Check the status of the new node and make sure it is synchronized. If not, select the new node and click Synchronize.

  2. Create the cluster:

    1. Open the DM Administration Console: http://dm_hostname:9090/admin

    2. Expand Servers. Select Clusters. The Create a new Cluster window is displayed on the right side.

    3. Enter the value for the Cluster name. In this example, we use WMM_Cluster.

    4. Check the box Prefer local enabled.

    5. Check the box Create Replication Domain for this cluster.

    6. Select the option Select an existing server to add to this cluster.

    7. Choose the server server1 from node WMM01.

    8. Click Next.

    9. Create a cluster member on WMM02. Enter the name of the new cluster member and select the node WMM02.

    10. Check Generate Unique HTTP Ports box.

    11. check the box Create Replication Entry in this server.

    12. Click Apply. The cluster member will appear in the Application Servers list in the bottom as shown in the following figure.

    13. Click Next. The summary window is displayed.

    14. Click Finish to create the cluster.

    15. Save the changes to the master configuration.

  3. Start the cluster:

    1. In the DM Administrative Console, expand Servers and select Clusters.

    2. Select the Cluster name. Click Start. (This process may take a while because it will start all applications under this Cluster.)

  4. Test Member Manager in the cluster. From any machine which has WMM driver loaded:

    1. Open a command window and navigate to the WMM\bin directory.

    2. Modify addCURUser.xml. in wmmXMLClient tag
      providerURL="corbaloc:iiop:<DM_hostname>:9809"
      wmmEJBName="cell/clusters/<Name_of_WMM_Cluster>/ejb/memberServiceHome"
      
      
      

    3. Run the following commands
      xmlClient addCURUser.xml
      
      
      

    4. (Optional) Try to stop one cluster member and test WMM to see if the cluster environment is working

 

Related Concepts


Directory services and WebSphere Commerce

 

Related tasks


Configure directory services (LDAP) with WebSphere Commerce
Install Member Manager on i5/OS
Configure the WebSphere Commerce database when using customized DNs
Configure Member Manager