Creating a static cluster on Windows

After installing IBM® WebSphere® Portal on the primary node, configuring a remote database, and preparing the primary node to communicate with the Deployment Manager, you can create your static cluster to handle failover requests.

1. Run the ConfigEngine.bat cluster-node-config-post-federation -DWasPassword=dmgr_password task.
2. The WebSphere Portal node is federated and using the Deployment Manager cell and its user registry. If the administrative user ID and group name are different in the WebSphere Portal and Deployment Manager configurations, choose one of the following options depending on your security policies:
   • Add the existing administrative user ID and group to the Deployment Manager security configuration
   • Complete the following steps to change the values in the WebSphere Portal configuration to match the Deployment Manager values:
   Restriction: If your Deployment Manager cell is using a stand-alone LDAP user registry, complete these steps after the cluster-node-config-cluster-setup (static cluster) or cluster-node-config-dynamic-cluster-setup (dynamic cluster) task completes.
   1. If necessary, start the WebSphere_Portal server.
   2. Verify that the required WebSphere Portal administrative user ID and group ID are defined in the Deployment Manager user registry that provides security for the cell.
   3. Run the ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid task, from the wp_profile_root\ConfigEngine directory, where:
      Important: If the value for newAdminGroupId contains a space; for example Software Group, open the wkplc.properties file and add the values for newAdminId, newAdminPw, and newAdminGroupId. Save your changes and then run the ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=dmgr_password task.
      • WasPassword is set to the administrative password for the Deployment Manager cell
      • newAdminId is set to the fully qualified distinguished name (DN) of the WebSphere Portal administrative user ID in the cell
      • newAdminGroupId is set to the fully qualified DN of the group for the WebSphere Portal administrative user ID in the cell
   4. After the task completes, stop the WebSphere_Portal server.
   5. 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.
3. Run the ConfigEngine.bat cluster-node-config-cluster-setup -DWasPassword=dmgr_password task.
4. If you entered passwords in any of the properties files while creating your cluster, you should remove them for security purposes. See "Deleting passwords from properties files" under Related tasks for information.