Set up farm instances as unique installations

Choose this option to have all portal farm instances to be unique installations. We have more control over the server-specific configuration because they are unique from server to server. For example, we can apply and test changes or application updates to one server on the farm at a time. The disadvantage to this option is that all administrative actions must be repeated on every server in the farm.

Set up farm instances as unique installations

1. Install and configure IBM WebSphere Portal on the initial system as a stand-alone server.

   Create a different database instance for the Release database. All farm members must have their own Release database. They can share all other databases. To connect new instances to the common database domains established by the first farm instance, use the connect-database task.

2. Start the WebSphere_Portal server.

3. From the WAS console go to...
   Servers | Server Types | WebSphere application servers | WebSphere_Portal | Web container settings | Web Container | Custom properties | New

   ...and add the HttpSessionCloneId custom property, with a value of WpServer1, where WpServer1 is the correct clone ID for that server instance. This ID uniquely identifies this server to the HTTP server plug-in for load balancing purposes.

   Click Save, then log out of the console.

4. If we are using WCM, set up the local messaging bus and queue.

   This step is run once on the server identified as the WCM SUBSCRIBER. This server is outside the farm and requires a message queue where content update messages are posted from members to the farm. All farm servers listen for these messages to update their own content caches. Run this step once when we set up the portal farm. It is not completed on each server in the farm. This step is only run on the server identified as the WCM SUBSCRIBER.

   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh create-wcm-jms-resources -DWasPassword=foo

5. For WCM, on each server in the farm, set the farm instance to listen for content update messages:

   1. Edit...
      WP_PROFILE/PortalServer/wcm/config/properties/prepreq.wcm.properties

      ...and update the following properties with the appropriate information for the farm servers...

      • remoteJMSHost
      • remoteJMSBootstrapPort
      • remoteJMSNodeName
      • remoteJMSServerName

   2. Set up the remote messaging bus and queue:
      ./ConfigEngine.sh create-wcm-jms-resources-remote -DWasPassword=foo

Subtopics

• Set up a virtual portal in a portal farm
  

Parent Choose the type of portal farm to create