+

Search Tips   |   Advanced Search

Add secondary nodes to a clustered environment

The standard process of adding IBM WebSphere Portal server nodes to a cluster is to set up a stand-alone WebSphere Portal server with the correct database settings, and run the enable-profiles task to generate profile templates used to create the secondary node profiles. However, there is a limitation with the enable-profiles task and it cannot be run in a clustered environment.

To create additional secondary nodes after you migrate a cluster, create a stand-alone WebSphere Portal server that is the same version of the migrated WebSphere Portal cluster, and run the enable-profiles task on that server.

AIX, Linux, and Solaris only: If we installed WebSphere Portal as a non-root user, run the chmod -R u+rwx PORTAL_HOME/ task to modify permissions for the Portal server directory before you begin. Then, run the chmod -R u+rx PORTAL_HOME/ task to restore the non-root permissions to the Portal server directory when after completing the following steps.

Complete the following steps on the stand-alone server:

  1. Install a stand-alone WebSphere Portal server that is the same version of the migrated WebSphere Portal cluster.

  2. Update the database settings to match the settings of the cluster database configuration, and run the ConfigEngine validate-database task to verify the settings are correct.

  3. Run the ConfigEngine connect-database task to update the WebSphere data source configuration of the stand-alone server.

  4. Run the ConfigEngine enable-profiles -DWasPassword=foo task from the profile on the stand-alone server we installed. This command creates a configuration archive (CAR) file used to create extra WebSphere Portal profiles. The Portal.car file is saved to the PORTAL_HOME/profileTemplates/default.portal/configArchives directory.

    If we configured WebSphere Portal for a remote database and placed the database drivers inside of the WP_PROFILE/PortalServer directory, they are included in the configuration archive file created when running the enable-profiles script. If the database drivers are outside of WP_PROFILE/PortalServer, make sure that you copy them to any additional nodes we are creating.

  5. Run the ConfigEngine package-profiles -DWasPassword=foo task to compress the profileTemplates directory and create a profileTemplates.zip file in the PORTAL_HOME/profileTemplates directory.

Complete the following steps on the secondary node:

  1. Install the WebSphere Portal server binary-only on the secondary node machine.

  2. Access the Configuration Wizard. Go to: http://your_server:10200/ibm/wizard.

  3. Click Set Up a Cluster > Create an Additional Cluster Node and following the instructions to create the secondary node profile, and add it the cluster.

    For the Install profile templates manual step, copy the profileTemplates.zip from the stand-alone server installed and ran the enable-profiles task on, not from the primary node.


Parent Administrative tasks