Create a dynamic cluster on Linux using WebSphere Virtual Enterprise

After installing and configuring WebSphere Portal on primary node and all additional nodes, you can create a new dynamic cluster. A dynamic cluster monitors performance and load information and is able to dynamically create and remove cluster members based on the workload.

Before creating dynamic cluster, you should have already installed and configured the Deployment Manager and performed all the tasks under “Preparing the primary node.” On the Deployment Manager system, install WebSphere Virtual Enterprise, apply all required ifixes, and augment the dmgr profile to make it compatible with WebSphere Extended Deployment Operations Optimization. On the WebSphere Portal primary node, install WebSphere Virtual Enterprise, apply all required ifixes, and augment the wp_profile profile to make it compatible with WebSphere Extended Deployment Operations Optimization. See the Planning the product installation link below for information about installing WebSphere Virtual Enterprise. Profile augmentation is performed using the Profile Management Tool (PMT) graphical interface on systems that support it or through the manageprofiles command that is available on all systems. When using the graphical interface as discussed in the link below, make sure you select Operations Optimization when choosing the type of augmentation to perform. When using the manageprofiles command as discussed in the link below, be sure to follow the instructions to augment a stand-alone application server profile.


Prerequisites

Recommended fixes for WebSphere Extended Deployment

Plan the product installation

Use the graphical user interface to augment profiles

Use the manageprofiles command to augment and unaugment profiles

Create a dynamic cluster:

  1. Perform the following steps for on the primary node of the dynamic cluster:


      ./ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=dmgr_password

    1. Since the WebSphere Portal node is now using security settings from the Deployment Manager cell, you need to update the WebSphere Portal administrative user ID and password to match an administrative user defined in the cell's user registry. Run the ./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the WP_PROFILE/ConfigEngine, to update the WebSphere Portal administrative user ID if the Deployment Manager cell is using a different user registry.

        Additional parameter for stopped servers: This task verifies the user against a running server instance. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.

        If standalone LDAP security is already enabled on the Deployment Manager cell, delay running the wp-change-portal-admin-user task until after the cluster-node-config-dynamic-cluster-setup task completes. After running the wp-change-portal-admin-user task, start or restart the WebSphere_Portal server to use the updated administrator user ID. The WebSphere Portal administrative user ID and administrative group must exist in the Deployment Manager before running the wp-change-portal-admin-user task. -DnewAdminPw is an optional parameter to update the Administrative password in wkplc.properties if required.

  2. Log on to the dmgr console.

  3. Create a node group:

    1. Click System administration -> Node groups.

    2. Click New.

    3. Type the node group Name.

    4. Optional. Type any information about the node group in the Description text box.

    5. Click OK.

    6. Click the Save link to save changes to the master configuration.

  4. Add members to the node group:

    1. Click System administration -> Node groups.

    2. Click on the name of the node group that you want to add members to.

    3. Click Node group members under Additional Properties.

    4. Click Add.

    5. Select the primary node and then click Add.

    6. Click the Save link to save changes to the master configuration.

  5. Create a dynamic cluster in the node group:

    1. Click Servers -> Clusters -> Dynamic clusters.

    2. Click New.

    3. Select WAS from the Server Type pull-down menu and then click Next.

    4. Select the Automatically define cluster members with rules radio button.

    5. Type the cluster name in the Dynamic cluster name text box and then click Next. Type the same value that you provided for the ClusterName parameter in wkplc.properties of primary node.

    6. Remove all default membership policies and then click Subexpression builder.

    7. Enter the following information in the Subexpression builder window:

      1. Select and from the Logical operator pull-down menu.

      2. Select Nodegroup from the Select operand pull-down menu.

      3. Select Equals (=) from the Operator pull-down menu.

      4. Type the nodegroup name you created in the previous step in the Value text box.

      5. Click Generate subexpression.

      6. Click Append.

    8. Click Preview membership to verify that all nodes included in the nodegroup display and then click Next.

    9. Click the Create the cluster member using an existing server as a template radio button and then select the WebSphere_Portal server for the primary node from the pull-down menu.

    10. Click Next.

    11. Specify the required dynamic cluster properties for minimum and maximum number of server instances.

        If you choose to configure vertical stacking to allow multiple server instances on a single node, see Adding vertical cluster members to a dynamic cluster for information on additional required configurations.

    12. When you are done configuring the dynamic cluster properties, click Next.

    13. Review the summary page to verify actions and then click Finish.

    14. Click the Save link to save changes to the master configuration.

  6. Define or verify the following parameters in ...

      WP_PROFILE/ConfigEngine/properties/wkplc.properties

    1. Verify that CellName is set to the dmgr cell.

    2. Verify that NodeName is set to the local WebSphere Portal node.

    3. Set ServerName to the server that will be used for the dynamic cluster member on this node.

        Log on to the dmgr console and click Servers -> Clusters -> Dynamic Clusters -> PortalCluster -> Dynamic cluster members to find the name of the server used for the dynamic cluster.

    4. Verify that PrimaryNode is set to true.

  7. Run the ./ConfigEngine.sh cluster-node-config-dynamic-cluster-setup -DWasPassword=dmgr_passwordfrom the WP_PROFILE/ConfigEngine to create the dynamic cluster.

      This task may display a warning message since the cluster already exists but it will proceed to create the new dynamic cluster; therefore, the warning can be ignored.

  8. Add a new JCRSeedBus cluster bus member and remove the previous server bus member:

    1. Log on to the Deployment Manager Administrative Console.

    2. Navigate to Service Integration -> Buses and then click JCRSeedBus.

    3. Under the Topology heading, click Bus members.

    4. Click Add.

    5. Click the Cluster radio button to define the type of new bus member and then select the name of this newly created Portal cluster from the drop-down menu. Click Next to continue.

    6. Ensure that the Enable Messaging Engine Policy Assistance checkbox is checked. Then choose the required messaging engine policy setting; refer to Messaging engine policy assistance for information.

    7. Click Next.

    8. Select the Data store radio button and then click Next.

    9. Click the name of the first messaging engine listed in the table.

    10. Enter the following information on the Specify data store properties panel:

      Data store fields that need information.

      Field Value
      Data source JNDI name jdbc/data_source_name, where data_source_name is the value for the jcr.DataSourceName property in wkplc_dbdomain.properties file located in the WP_PROFILE/ConfigEngine/properties directory of the primary node.
      Schema name Value of the jcr.DbSchema property in wkplc_dbdomain.properties.
      Authentication alias Choose the entry in the drop-down list whose name contains the JCR data source name.

    11. Ensure that the Create tables checkbox is checked and then click Next to continue.

    12. The Configure messaging engines panel displays containing the list of messaging engines. If any additional messaging engines are displayed, repeat the steps to configure each additional messaging engine in the table. Then click Next to continue.

    13. Review the heap sizes on the Tune performance parameters panel. Click Next to continue.

        To change the values, click the Change heap sizes checkbox and enter new values in the Proposed heap sizes text fields.

    14. The Summary panel displays, which allows you to review the messaging engine configuration changes. Click Previous if you need to go back and make additional changes or click Finish to complete the configuration process.

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

    16. The table of bus members displays. Select the Server bus member type with the name of the Portal server from the primary node and click Remove.

    17. Click OK to verify the removal of the server bus member.

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

    19. Synchronize changes to the primary node.

  9. Run the following tasks to propagate changes:

      WebSphere_Portal_servername is the name of the node's WebSphere Portal server; but if you customized the server name, the default name changes. If you are uncertain of the server name, run the serverstatus -all task to get a list of the server names and their status.

      1. ./stopServer.sh WebSphere_Portal_servername -username admin_userid -password foo

      2. ./startServer.sh WebSphere_Portal_servername


Parent

Prepare to create the cluster on Linux

  Nov 4, 2011 10:31:14 AM Added additional steps to Step 5 for configuring the JCRSeedBus member


+

Search Tips   |   Advanced Search