WebSphere

 

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

 

Create the cluster

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

  1. Use a text editor to open the wpconfig.properties file on the primary node.

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

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

    • PrimaryNode property: Verify that value for this node is true.

  3. Create the cluster.

    The cluster-setup task requires complete and accurate database information in the wpconfig_dbdomain.properties and wpconfig_dbtype.properties files. Before running the task, ensure that the database properties are correct and that password values are specified.

    • Windows and Linux:

      Run the following command from the portal_server_root/config directory:

      • Windows:

        WPSconfig.bat cluster-setup -DWasPassword=password

      • Linux:

        ./WPSconfig.sh cluster-setup -DWasPassword=password

    • i5/OS:

      Run the following command from the portal_server_root_user/config directory: 

      WPSconfig.sh -profileName profile_root cluster-setup -DWasPassword=password

      where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.

  4. Configure the cluster to use an external Web server.

    • By default, WebSphere Portal Express 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, refer to the information center for WebSphere Application Server to complete this configuration by installing the Web server and adding the new Web server definition to the deployment manager. From the link below, 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 instead 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 Linux:

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

     

    Deployment Manager Security

    If you want to log in to the deployment manager administrative console using the WebSphere Application Server short ID, complete the following steps on the deployment manager machine. If you want to give all nodes in the cell access to the Member Manager database, the following steps must be performed on each non-portal node. While access to the database is not required in all setups, it is recommended to perform these steps in all cases because some configuration changes may required the use of the database:

    1. Ensure that the database software required for the Member Manager domain is installed. The software is installed locally on the non-portal node.

      If you are using DB2 Type 2 drivers catalog the Member Manager User Registry database on the non-portal node.

    2. This step may be skipped if access is being set up on non-portal nodes. Create a connection for the deployment manager to the Member Manager database.

      • First establish a unique datasource name for the database by setting the following property in the wpconfig_dbdomain.properties file: 

        wmm.DataSourceName=wmmdbDS

      • Create the connection by running the following command on the cluster's primary node, from the portal_server_root/config directory, or for i5/OS, from the portal_server_root_user/config directory:

        • Windows:

          WPSconfig.bat connect-database-wmm

        • Linux:

          ./WPSconfig.sh connect-database-wmm

        • i5/OS:

          WPSconfig.sh -profileName profile_root connect-database-wmm -DWasPassword=password

          where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.

    3. Log in to the deployment manager administrative console, and click Resources > JDBC Providers. View the resources at Cell scope by verifying the Node and Server fields are empty and click Apply.

    4. Click on the JDBC provider that contains the Member Manager data source.

    5. In the Classpath field, note the name of the environment variable specified. For example, ${ DB2_JDBC_DRIVER_CLASSPATH}.

    6. Select Environment > WebSphere Variables in the navigation tree.

    7. Select either the deployment manager or the non-portal node to filter the list of variables. Select Browse Nodes, then select either the deployment manager Node or the non-portal Node, and then click Apply.

    8. Click New.

    9. Enter the name of the variable previously specified by the JDBC provider, for example DB2_JDBC_DRIVER_CLASSPATH.

    10. In the Value field, enter the directory and name of the ZIP or JAR file that contains the JDBC driver class. For example: db2_install/java/db2java.zip.

    11. Save your changes to the deployment manager configuration.
    Web Content Management note: If your users need to access content created by Web Content Management through a 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 your application server.

      3. Click Browse Servers.

      4. Select the application server for WebSphere Portal Express and click OK.

        Remember that server1 is not a cluster member, only the WebSphere Portal Express server will be a cluster member.

      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 WebSphere Portal Express server.

  5. After creating the cluster, change the Task List settings to point to the cluster instead of a single server. Refer to the topic Changing task list settings for details on specifying the setting for a cluster.

 

Parent topic:

Setting up a cluster

 

Previous topic

Installing and federating the primary node

 

Next topic

Installing and federating secondary nodes