Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Adding additional nodes to the cluster on Linux

After installing IBM^® WebSphere^® Portal Express on your secondary node, add the node to the cluster to create a highly available environment.

1. Verify that the following properties are set in the wkplc.properties file, located in the wp_profile/ConfigEngine/properties directory of the secondary node:

   1. Verify that WasPassword is set to your WebSphere Application Server password.
   2. Verify that PortalAdminPwd is set to your WebSphere Portal Express password.
   3. Verify that WasRemoteHostName is set to the fully qualified hostname of the deployment manager.
   4. Verify that WasSoapPort is set to 8879.
   5. Verify that LTPAPassword is set to your LTPA password.
   6. Verify that PrimaryNode is set to false.
   7. Verify that ClusterName is set to PortalCluster.
2. Set all database user ID and password properties in the wkplc_comp.properties file, located in the wp_profile/ConfigEngine/properties directory of the secondary node.
3. Run the ./ConfigEngine.sh cluster-node-config-pre-federation task, located in the wp_profile/ConfigEngine directory of the secondary node.
4. Run the following tasks to validate your database settings:

   1. ./ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds
   2. ./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds
5. Run the ./ConfigEngine.sh cluster-node-config-post-federation task.
6. Perform the following steps to update the security configuration on the secondary node:

   1. Update the wkplc.properties file on the secondary node with the LDAP user registry property values from the wkplc.properties file on the primary node.
   2. Run the ./ConfigEngine.sh enable-jcr-security -DPortalAdminId=portal_admin_id task on the secondary node, where portal_admin_id is the fully qualified distinguished name of the administrator; for example, uid=wpsadmin,cn=users,dc=example,dc=com.
   3. Run the following tasks to stop and restart server1 from the wp_profile_root/bin:

      1. ./stopServer.sh server1 -user admin_userid -password admin_password
      2. ./startServer.sh server1
7. Run the ./ConfigEngine.sh cluster-node-config-cluster-setup task.
8. Wait at least 30 minutes before stopping and restarting the deployment manager because the node agent runs a background thread to expand all EAR files into their target directories. Note: Attempting to restart the deployment manager while the expansion is in process can result in an unusable application. Although the time to complete an EAR expansion is environment-dependent, a 30 minute wait is sufficient for a typical environment.
9. Run the following tasks to stop and restart the deployment manager:

   1. ./stopManager.sh, located in the wp_profile_root/bin directory
   2. ./startManager.sh, located in the wp_profile_root/bin directory
10. Enter the following commands to stop and restart the WebSphere_Portal server from the wp_profile_root/bin:

    1. ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password
    2. ./startServer.sh WebSphere_Portal
11. Perform the following steps to synchronize the nodes:

    1. Log in to the deployment manager administrative console.
    2. Select System Administration > Nodes, select the node from the list, and then click Full Resynchronize.