Add vertical cluster members to a static cluster on IBM i

You can add vertical cluster members to share the workload demands of cluster across multiple members running on the same physical machine.


Prerequisites


Install WebSphere Portal on IBM i on the additional cluster nodes
Add additional nodes to the cluster on IBM i

Add a vertical cluster member to clustered environment:

  1. Log into the dmgr console.

  2. Click Servers -> Clusters -> WebSphere application server clusters -> cluster_name -> Cluster members.

  3. Click New to create the cluster member.

    1. Define the name of cluster member.

        Do not use spaces in the cluster member name.

    2. Select an existing node where WebSphere Portal is installed.

    3. Check the box Generate Unique HTTP Ports.

    4. Click Apply and then click Next to view the summary.

    If you are not using an external web server in clustered environment, update the virtual host entries for the new port created when adding a cluster member. You can do this by updating the default_host virtual host in the administrative console and adding a new alias entry for the port number (use an "*" wildcard character for the host name). See Configure virtual hosts for information.

  4. Click Finish, and save the changes.

      The new cluster topology can be viewed from the Servers -> Clusters -> Cluster Topology view.

      The Servers -> Server Types -> WebSphere application servers view will list the new server cluster members.

  5. Complete the following steps to enable cache replication:

    1. From the dmgr console, navigate to Servers -> Server Types -> WebSphere application servers and then click the new vertical cluster member(s).

    2. Click Dynamic cache service under Container services.

    3. Change Cache size to 3000 entries.

    4. Check the Enable cache replication check box.

    5. Select NOT_SHARED from the Replication type drop-down menu.

    6. Click OK.

    7. Click Save to save changes to the master configuration.

  6. Complete the following steps on each vertical cluster member to clean up the server-scoped resources, caches, and resource providers:

    1. Run the ConfigEngine.sh cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, where unique vertical cluster servername is the name you specified when you created the cluster member.

    2. Restart the vertical cluster member referenced in the cluster-node-config-vertical-cluster-setup task.

  7. Access the Web Content Manager content through an external Web server:

    1. Log on to the dmgr console.

    2. Select Environment -> WebSphere Variables.

    3. From the Scope drop-down menu, select the Node=nodename, Server=servername option to narrow the scope of the listed variables, where Node=nodename is the node that contains the application server.

    4. Update the WCM_HOST variable with the fully qualified host name used to access the WebSphere Portal server through the Web server or On Demand Router.

    5. Update the WCM_PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.

    6. To synchronize the node with the dmgr:

      1. Select System Administration -> Nodes.

      2. Select the node that you want to synchronize from the list.

      3. Click Full Resynchronize.

    7. Log off of the dmgr console.

  8. Save changes and resynchronize the nodes.

    1. In the administrative console for the dmgr, click Save on the task bar, and save administrative configuration.

    2. Select System Administration -> Nodes, select the node from the list, and click Full Resynchronize.

  9. Regenerate the web server plug-in.

    1. Regenerate the web server plug-in using the dmgr console.

    2. If you are using a remote web server, copy the updated plug-in configuration file (plugin-cfg.xml) to the web server's plug-in configuration directory.

  10. Stop and start the web server.


Parent

Prepare additional nodes on IBM i


Previous

Add additional nodes to the cluster on IBM i

 


+

Search Tips   |   Advanced Search