Add vertical cluster members

 

+

Search Tips   |   Advanced Search

 

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

1. Access the administrative console on the deployment manager. For example...

   http://DM01:9060/ibm/console

   ...in the address bar, where DM01 is the deployment manager node or host.name. The port number might differ based on the installation.

2. Click...

   Servers | Clusters | cluster_name | Cluster members | New

   1. Define the name of cluster member.

      Do not use spaces in the cluster member name.

   2. Select an existing node where IBM 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 the clustered environment, update the virtual host entries for the new port created when adding a cluster member. We 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).

3. Click Finish, and save the changes.
   • The new cluster topology can be viewed from the Servers > Cluster Topology view.

   • The Servers > Application Servers view will list the new server cluster members.

4. Save the changes and resynchronize the nodes.
   1. In the administrative console for the deployment manager, click Save on the task bar, and save the administrative configuration.

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

5. Regenerate the Web server plug-in.
   1. Regenerate the Web server plug-in using the deployment manager administrative 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.

6. Stop and start the Web server.

Web Content Management note: If the users need to access content created by Web Content Management through a portal server that is configured to use an HTTP port other than the default internal HTTP port (for example, with a Web server), ensure that required substitution variables are set in the configuration for WebSphere Application Server.

1. Log in to the administrative console for WebSphere Application Server. If you are using the Web server in a clustered environment, open the administrative console for the deployment manager machine.

2. Select...

   Environment | WebSphere Variables

3. Narrow the scope of the listed variables

   Browse Nodes | node_name | Browse Servers | WebSphere_Portal | OK | Apply

4. Update the value of the WCM_HOST variable with the fully qualified host.name of the Web server.

5. Update the value of the WCM_PORT variable with the port number used to access the Web server.

6. Restart the portal server.

 

Parent Topic

Adding cluster members

 

---