Create a static cluster on Windows

 

+

Search Tips   |   Advanced Search

 

After...

...you can create your static cluster to handle failover requests.

To create the cluster:

  1. If the Deployment Manager is configured to use a stand-alone LDAP user registry, update...

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

  2. Stop the server1 and WebSphere_Portal servers on the primary node and ensure that the following parameters are set correctly in...

    • Set WasSoapPort to the port used to connect remotely to the WAS.

    • Set WasRemoteHostName to the full hostname of the server used to remotely connect to the WAS.

  3. On the primary node, run...

    Add the parameters...

      -DDMgrUserid=dmgrid -DDMgrPassword=dmgrpassword

    ...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 -DDMgrUserid 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:

    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. On each node, to create the variable used to access the VMM database jars...

        cd WP_PROFILE\ConfigEngine
        ConfigEngine.bat wp-node-prep-vmm-db-secured-environment -DWasPassword=wpsadmin -DDbDomain=la|federated.db -DVmmNodeName=node -Ddb_type.NodeDbLibrary=/path/to/DB/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

      For example...

        ConfigEngine.bat wp-node-prep-vmm-db-secured-environment -DWasPassword=wpsadmin -DDbDomain=la -DVmmNodeName=F32BC -Ddb2.NodeDbLibrary=c:/IBM/SQLLIB/db2java.zip

  5. Run...

      ConfigEngine.bat cluster-node-config-post-federation

  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.

    To update the WebSphere Portal administrative user ID if the Deployment Manager cell is using a different user registry.

      cd WP_PROFILE\ConfigEngine
      ConfigEngine.bat wp-change-portal-admin-user -DnewAdminId=newadminid –DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroup

    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.

  7. Run...

      ConfigEngine.bat cluster-node-config-cluster-setup

  8. Configure the cluster to use an external Web server to take advantage of features such as workload management. Choose one of the following options:

    Start with the step about launching the Plug-ins installation wizard.

  9. To access the WCM content through an external Web server:

    1. Log on to the deployment manager administrative console.

    2. Select...

    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.

  10. Change the task list settings to point to the cluster instead of a single server.

 

Parent topic

Choosing the type of cluster to create on Windows