Create 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 static cluster to handle failover requests.

Create the cluster:

1. Run the ConfigEngine.bat cluster-node-config-post-federation -DWasPassword=dmgr_password

2. 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.bat 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.
   Attention: The password value for -DWasPassword is the Deployment Manager administrative password.

   Important: You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.

   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.

   • Fastpath: If the value for newAdminGroupId contains a space; for example Software Group, open wkplc.properties and add the values for newAdminId, newAdminPw, and newAdminGroupId. Save changes and run the ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=dmgr_password task.

   • Important: 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-cluster-setup (static cluster) or cluster-node-config-dynamic-cluster-setup (dynamic cluster) 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.

   • Note: 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.

3. Run the ConfigEngine.bat cluster-node-config-cluster-setup -DWasPassword=dmgr_password

4. If you entered passwords in any of the properties files while creating cluster, you should remove them for security purposes. See "Deleting passwords from properties files" under Related tasks for information.

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

       Table 1. Data store fields that need information.

   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.
       Tip: 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. Navigate to Resources -> JMS -> Topic Connection Factories-> JCRSeedTCF.

   19. For the Durable Subscription Home property, select the new bus member you created from the drop-down menu; for example, PortalCluster.000-JCRSeedBus.

   20. Click OK to confirm the update to JCRSeedTCF.

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

   22. Synchronize changes to the primary node.

       • NOTE:  If you previously configured a data store type of bus member, you need to remove it first before you recreate it. Also, follow the instructions in this tech note - . The tech note explains how to clean up the tables. If you do not clean up the tables, the bus member does not properly start.

6. Run the following tasks to propagate changes:
   Note: 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.bat WebSphere_Portal_servername -username admin_userid -password foo

     2. startServer.bat WebSphere_Portal_servername

Parent: Prepare to create the cluster on Windows

Related information

Delete passwords from properties files

February 7, 2012

  Added Hunter's steps back into step 5. 2011/12/15 documentation refresh Nov 4, 2011 10:35:11 AM Added additional steps to Step 5 for configuring the JCRSeedBus member Minor change

+

Search Tips   |   Advanced Search