Set up farm instances as unique installations

Choose this option if you want all portal farm instances to be unique installations. This option allows you to have more control over the server-specific configuration as they are unique from server to server. For example, this allows you to 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.

To set up farm instances as unique installations: All steps are repeated for each instance that you add to the portal farm except for the create-wcm-jms-resources step; that step is only performed once on the server identified as the WCM SUBSCRIBER used in the portal farm.

Create a different database instance for the Release database because all farm members must have their own Release database. They can share all other databases, including the JCR database because of the messaging support contained in the above steps. Use the connect-database task to connect these instances to the other common database domains already established by the first farm instance.

  1. Install and configure WebSphere Portal on the initial system as a stand-alone server; see the appropriate Setting up a stand-alone server topic in the Related task section below.

    Create a different database instance for the Release database because all farm members must have their own Release database. They can share all other databases.

  2. Ensure the server1 and WebSphere_Portal servers are started.

  3. Log on to the IBM WAS administrative console and perform the following steps:

    1. Navigate to Servers -> Server Types -> WebSphere application servers -> WebSphere_Portal -> Web container settings -> Web Container and then click Custom properties under the Additional Properties section .

    2. Click 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.

    3. Click OK.

    4. Click Save to save changes.

    5. Log out of the IBM WAS administrative console.

  4. Optional. If you are using IBM Web Content Manager, run the following task, from the WP_PROFILE/ConfigEngine, to set up the local messaging bus and queue:

      To avoid the system receiving all content updates from the authoring system, one server outside the farm needs to be identified as the subscriber. This server also requires a message queue where content update messages are posted from members to the farm. All farm servers will listen for these messages to update their own content caches.

      This step is only performed once when setting up the portal farm; it is not performed on each server in the farm. This step is only executed on the server identified as the WCM SUBSCRIBER used in the portal farm.

      • UNIX™: ./ConfigEngine.sh create-wcm-jms-resources -DWasPassword=foo

      • IBM i: ConfigEngine.sh create-wcm-jms-resources -DWasPassword=foo

      If you are using a remote content environment, see the "Working with syndicators and subscribers" link below under Related concepts.

  5. Optional. If you are using Web Content Manager, perform the following steps to set up additional farm instances to listen for content update messages:

      This step is performed on each server in the farm.

      1. Open the prepreq.wcm.properties file, located in the WP_PROFILE/PortalServer/wcm/config/properties/ directory and update the following properties with the appropriate information for the farm servers:

          See the prepreq.wcm.properties file for specific information about the required parameters.

            remoteJMSHost
            remoteJMSBootstrapPort
            remoteJMSNodeName
            remoteJMSServerName

      2. Run the following task to set up the remote messaging bus and queue:

        • UNIX: ./ConfigEngine.sh create-wcm-jms-resources-remote -DWasPassword=foo

        • IBM i: ConfigEngine.sh create-wcm-jms-resources-remote -DWasPassword=foo

WebSphere Portal is now managed the same as a stand-alone server in terms of starting, stopping, and maintaining the configuration.


Parent

Choose the type of portal farm to create
Work with syndicators and subscribers


Related tasks


Set up a stand-alone production server


Database sharing and load balancing for portal farms

 


+

Search Tips   |   Advanced Search