+

Search Tips   |   Advanced Search

Portal, V6.1

 

Create a new WebSphere Extended Deployment dynamic cluster on Windows

After installing and configuring IBM WebSphere Portal on your primary node and all additional nodes, you can create a new dynamic cluster. Instead of simply handling requests if the primary cluster fails, a dynamic cluster balances the workloads of its members based on performance information collected from the members. Before creating your dynamic cluster, install and configure the Deployment Manager and perform all the tasks under “Preparing the primary node”. On the Deployment Manager system, install WebSphere Extended Deployment and augment the deployment manager profile. On all WebSphere Portal nodes, install WebSphere Extended Deployment and augment the wp_profile profile. See Installing and configuring the product for information about installing WebSphere Extended Deployment. See Augmenting profiles for information about augmenting the Deployment Manager and wp_profile profiles.

To create a dynamic cluster:

  1. On the primary node of the dynamic cluster:

    1. Prepare the node for the dynamic cluster; perform all tasks under Preparing the primary node.

    2. If the Deployment Manager is configured to use a stand-alone LDAP user registry, update the wkplc.properties file in WP_PROFILE\ConfigEngine\properties directory on the primary node with the stand-alone LDAP user registry property values from the Deployment Manager. You can find these settings under the VMM Stand-alone LDAP configuration heading.

    3. Run the ConfigEngine.bat cluster-node-config-pre-federation task from the WP_PROFILE\ConfigEngine directory of the primary node. Add the...

      -DDMgrUserid=dmgrid -DDMgrPassword=dmgrpassword

      ...parameters to the cluster-node-config-pre-federation if the WAS administrative credentials in the Deployment Manager cell is different from the local node you are adding to the Deployment Manager cell.

      If you specify the -DDMgrUserid parameter when running the cluster-node-config-pre-federation it resets the WasUserid parameter in the wkplc.properties file to the -DDMgrUserid value.

    4. Run the following task for EACH WebSphere Portal node that participates in the cluster to set up access to the database drivers; if multiple nodes share the same database library path you can submit a comma separated list of node names:

      This task does not need to be executed from the node identified in the VmmNodeName parameter.

      1. Set the property value for federated.db.DbType if using a database user registry or if the cell is migrated from a previous version and set the property value for la.DbType if using a property extension database in the wkplc.properties file.

      2. Run the ConfigEngine.bat wp-node-prep-vmm-db-secured-environment -DWasPassword=wpsadmin -DDbDomain=la|federated.db -DVmmNodeName=node -Ddb_type.NodeDbLibrary/path/to/DB/jars from the WP_PROFILE\ConfigEngine directory on each node to create the variable used to access the VMM database jars.

        Where DbDomain is either la or federated.db depending on whether you are using a property extension database (la) or a database user registry (federated.db). VmmNodeName is a list of one or more WebSphere Portal nodes names in the cell which share the same database driver paths. The db_type in db_type.NodeDbLibrary should be set to the type of database you are using, for example db2. The local full path of the database jars should be one of the following options:

        • DB2 Type 2 driver: db2java.zip

        • DB2 Type 4 driver: db2jcc.jar;db2jcc_license_cu.jar

        • DB2 for z/OS Type 2 driver: db2java.zip

        • DB2 for z/OS Type 4 driver: db2jcc.jar;db2jcc_license_cisuz.jar;db2jcc_javax.jar

        • Oracle: ojdbc14.jar

    5. Run the ConfigEngine.bat cluster-node-config-post-federation task.

    6. Since the WebSphere Portal node is now using security settings from the Deployment Manager cell, you may 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.bat wp-change-portal-admin-user -DnewAdminId=newadminid –DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroup from the WP_PROFILE\ConfigEngine directory, to update the WebSphere Portal administrative user ID if the Deployment Manager cell is using a different user registry.

      This task verifies the user against a running LDAP server instance when LDAP security is enabled. If the LDAP server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.

      If stand-alone LDAP security is already enabled on the Deployment Manager cell, delay running the wp-change-portal-admin-user until after the cluster-node-config-cluster-setup completes. After running the wp-change-portal-admin-user 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 the wkplc.properties file if required.

  2. Log on to the "WebSphere Extended Deployment" deployment manager.

  3. To 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 your changes to the master configuration.

  4. To 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 your changes to the master configuration.

  5. To create a dynamic cluster in the node group:

    1. Click Servers > Dynamic clusters.

    2. Click New.

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

    4. 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 the wkplc.properties file of your primary node.

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

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

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

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

    9. Click Next.

    10. Specify the dynamic cluster.properties and then click Next.

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

  6. Define or verify the following parameters in the wkplc.properties located in WP_PROFILE\ConfigEngine\properties directory:

    1. Set ClusterName to the name of the new dynamic cluster.

    2. Verify that CellName is set to the Extended Deployment cell.

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

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

    5. Verify that PrimaryNode is set to true on the primary node and false for all additional nodes.

  7. Run the ConfigEngine.bat cluster-node-config-dynamic-cluster-setup from the WP_PROFILE\ConfigEngine directory 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. To access the WCM content through an external Web server:

    1. Log on to the deployment manager administrative console.

    2. Select Environment > WebSphere Variables.

    3. From the Scope drop-down menu, select the Node=node, Server=WebSphere_Portal option to narrow the scope of the listed variables, where Node=node 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. Save changes and then restart the deployment manager, the node agent(s), server1, and the WebSphere_Portal servers.

  9. If you are using a Web server to connect to the On Demand Router (ODR), configure the web server as a trusted proxy on the ODR. Refer to Configure a Web server as a trusted proxy server for instructions. Tip: You can also configure the ODR to dynamically update the Web server configuration when changes occur. Refer to Configure an on demand router to dynamically update the Web server plug-in configuration for instructions.

 

Parent topic

Choosing the type of cluster to create on Windows