WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Add horizontal cluster members

If you have installed WebSphere Portal Express on a secondary node, you can add the node as a horizontal cluster member to distribute a portion of the workload in the cluster to the secondary node.

  1. Add the secondary node to the cluster.

    1. Use a text editor to open the wpconfig.properties file.

    2. Ensure that the following properties are uncommented and specify appropriate values:

      • ClusterName property: Specify the name of the cluster to which you are adding the node.

      • ServerName property: Specify the cluster member name you want to use when adding this node to the cluster.

        The cluster member name you specify for this property must be unique within the cell and cannot have the same value as the ServerName property on the primary node or other secondary nodes.

      • PrimaryNode property: Verify that the value for this node is false.

    3. Add the node to the cluster.

      • Windows and Linux:

        Run the following command from the portal_server_root/config directory:

        • Windows:

          WPSconfig.bat cluster-setup -DWasPassword=password

        • Linux:

          ./WPSconfig.sh cluster-setup -DWasPassword=password

      • i5/OS:

        Run the following command from the portal_server_root_user/config directory: 

        WPSconfig.sh -profileName profile_root cluster-setup -DWasPassword=password
        where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.

      Because WebSphere Application Server typically creates unique ports for all servers, the default port number for the WebSphere Portal Express application server is changed when the node is added to the cluster. To determine the port number after creating the new cluster member, complete the following steps in the deployment manager administrative console.

      1. Click Servers > Application Servers in the navigation pane.

      2. Click the application server name for the secondary node.

      3. Click Ports under the Communications settings, and verify the port number listed for the WC_defaulthost port.

  2. Click Servers > Cluster Topology to view the updated cluster topology.

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

  4. Stop and start the Web server.

  5. Restart all cluster members, where each cluster member is a single application server in the cluster.
Web Content Management note: If your users need to access content created by Web Content Management through a 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

    1. Click Browse Nodes in the Scope field.

    2. Select the node containing your application server.

    3. Click Browse Servers.

    4. Select the application server for WebSphere Portal Express and click OK.

      Remember that server1 is not a cluster member, only the WebSphere Portal Express server will be a cluster member.

    5. Click Apply to update the list of variables.

  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 WebSphere Portal Express server.

If you are not using an external Web server in your 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). Refer to the WebSphere Application Server information center for more information:

 

Parent topic:

Adding cluster members