Create the cluster

 

+

Search Tips   |   Advanced Search

 

After the primary node is installed and running as a managed node under deployment manager control, create the cluster.

1. On the primary node, edit...

   portal_server_root/config/wpconfig.properties

2. Ensure that the following properties are uncommented and specify appropriate values:
   • ClusterName

     Specify the cluster name you want to use when creating the cluster. Do not use spaces or special characters in the cluster name.

   • PrimaryNode

     Verify that value for this node is true.

3. Verify complete and accurate database information is in...
   • wpconfig_dbdomain.properties
   • wpconfig_dbtype.properties

   ...inlcuding database properties and password values.

4. Create the cluster.

   cd portal_server_root/config
   ./WPSconfig.sh cluster-setup -DWasPassword=password

   For i5/OS:

   cd portal_server_root/config
   WPSconfig.sh -profileName profile_root cluster-setup -DWasPassword=password

5. Configure the cluster to use an external Web server.
   • By default, WebSphere Portal uses its own HTTP service for client requests. However, an external Web server is required to take advantage of features such as workload management.

   • If you are using the recommended approach of installing and configuring the external Web server after the creation of the cell, install the Web server and adding the new Web server definition to the deployment manager.

     Follow the instructions contained in the section entitled...

     Set up a remote Web server installation in a cell

     ...if you are installing the Web server on a remote machine.

     If the Web server will be installed on the same machine as either the deployment manager or one of the portal cluster members, follow the instructions in the section entitled...

     Set up a local distributed Web server configuration

     • Windows and UNIX:

       Select a Web server topology diagram and roadmap

     • i5/OS:

       Select a Web server topology diagram and roadmap

     Windows and UNIX:

     In the table defining the installation steps for this process, note that the WAS Network Deployment installation and node federation steps (1-6) have already been completed as part of the WebSphere Portal instructions provided earlier. Therefore, begin the Web server configuration process at step 7 (Install IBM HTTP Server or another supported Web server).

    

   Web Content Management note

   If the users need to access content created by Web Content Management through a portal server that is configured to use an HTTP port other than the default internal HTTP port (for example, with a Web server), ensure that required substitution variables are set in the configuration for WebSphere Application Server.

   1. Log in to the administrative console for WebSphere Application Server. If you are using the Web server in a clustered environment, open the administrative console for the deployment manager machine.

   2. Select Environment | WebSphere Variables.

   3. Narrow the scope of the listed variables
      1. Click Browse Nodes in the Scope field.

      2. Select the node containing the application server.

      3. Click Browse Servers.

      4. Select the application server for WebSphere Portal (for example, WebSphere_Portal) and click OK.

      5. Click Apply to update the list of variables.

   4. Update the value of the WCM_HOST variable with the fully qualified host.name of the Web server.

   5. Update the value of the WCM_PORT variable with the port number used to access the Web server.

   6. Restart the portal server.

 

Parent topic:

Set up a cluster

 

Previous topic

Install and federating the primary node

 

Next topic

Install and federating secondary nodes

 

---