Install multiple clusters in a single cell on IBM i

Create a new, independent WebSphere Portal cluster in a cell where a WebSphere Portal cluster already exists.

In the following steps, Cluster A will be used to describe the existing cluster. Portal B will be used to describe the new server profile that will be the basis for the new cluster definition, Cluster B.

To install multiple clusters in a single cell:

  1. Upgrade Cluster A, including the Deployment Manager node, to the current, supported hardware and software levels and to the current version of IBM WebSphere Portal.

  2. Install and configure Portal B; see the "Preparing the primary node" topic and choose the appropriate OS for details; you can skip the steps in the "Preparing the WAS Deployment Manager" because the Deployment Manager is already operational.

    Maintain the same number of data sources with identical names to the Cluster A data sources so that data source bindings in the applications can be resolved on every cluster in which they run. If implementing database sharing across the clusters, the above statement refers to both the shared and non-shared domains; all domains should use the same names.

  3. Optional. Using the same database user ID and password for each identically named domain/data source will allow the existing JAAS Authentication Aliases to be functional. If unique database user ID and password are required, additional manual configuration is needed to create new JAAS Authentication Aliases for each data source and map these accordingly. On the primary node of Cluster A, run the ConfigEngine.sh create-alias-multiple-cluster -DauthDomainList=release,jcr -DWasPassword=dmgr_passwordfrom the WP_PROFILE/ConfigEngine to create the new JAAS Authentication Aliases.

      where authDomainList is set to a list of domains which use unique database user ID and passwords and those domain properties are set correctly in wkplc_comp.properties, including user ID and password.

  4. Optional. If necessary, upgrade Portal B to the current cumulative fix.

  5. Run the ConfigEngine.sh mapped-app-list-create -DWasPassword=foofrom the WP_PROFILE/ConfigEngine to build an inventory of Portal B enterprise applications and portlets.

  6. If the Deployment Manager is configured to use a stand-alone LDAP user registry, update ...

      WP_PROFILE/ConfigEngine/properties/wkplc.properties
    on the primary node with the stand-alone LDAP user registry property values from the Deployment Manager. You can find these settings under the VMM Stand-alone LDAP configuration heading.

    Ensure that you set WasUserid and WasPassword to the Deployment Manager user ID and password.

  7. Optional. Run the following command from the WP_PROFILE/bin directory to federate Portal B:

    If you chose the option to automatically federate this new profile to a Deployment Manager as part of the profile creation, then this step is not necessary. If you are not sure, go ahead and run the addNode command as documented below. The task will fail if the node is already federated. 

    addNode.sh dmgr_hostname dmgr_port -includeapps
	-username was_admin_user
	-password was_foo

    The above variables are defined as:

    • dmgr_hostname is the TCP/IP host name of the Deployment Manager server

    • dmgr_port is the SOAP port number of the Deployment Manager server

    • was_admin_user and was_foo are the user ID and password for the Deployment Manager administrator

    If the WAS administrator user ID and password for the local node are different than the Deployment Manager administrator user ID and password, add the following parameters to the addNode task:

    • -localusername local_was_admin_user

    • -localpassword local_was_foo

    See the addNode command file for more information about the addNode command and other optional parameters.
    Warning: If the addNode task fails for any reason, perform the following steps before rerunning the task:

    1. Remove the node if the AddNode task succeeded in creating the node.

    2. Log on to the dmgr and perform the following steps if the items exist:

      1. Remove all enterprise applications.

      2. Remove the WebSphere_Portal server definition.

      3. Remove the WebSphere Portal JDBC Provider.

  8. Stop the WebSphere_Portal server on the primary node and ensure that the following parameters are set correctly in ...

      WP_PROFILE/ConfigEngine/properties/wkplc.properties

      Although you can add these parameters directly to any task that you run while creating cluster, you may want to add them to the properties file while creating cluster and then remove them when you are finished to keep environment secure.

      1. Set WasSoapPort to the port used to connect remotely to the dmgr.

      2. Set WasRemoteHostName to the full host name of the server used to remotely connect to the dmgr.

      3. Verify that WasUserid is set to Deployment Manager administrator user ID.

      4. Verify that WasPassword is set to Deployment Manager administrator password.

      5. Verify that PortalAdminPwd is set to WebSphere Portal administrator password.

      6. Verify that ClusterName is set.

      7. Verify that PrimaryNode is set to true.

  9. Run the ConfigEngine.sh map-apps-to-server -DWasPassword=footo determine which applications from the inventory list are no longer mapped to Portal B. The task uses the application profiles already in the cell to restore the mappings. Wait 30 minutes after running this task to allow all EAR files to expand before proceeding to the next step.

  10. Run the ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=dmgr_password

  11. Since the WebSphere Portal node is now using security settings from the Deployment Manager cell, you need to update the WebSphere Portal administrative user ID and password to match an administrative user defined in the cell's user registry. Run the ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the WP_PROFILE/ConfigEngine, to update the WebSphere Portal administrative user ID if the Deployment Manager cell is using a different user registry.

    The password value for -DWasPassword is the Deployment Manager administrative password.

    You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.
    Additional parameter for stopped servers: This task verifies the user against a running server instance. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.
    Fastpath: If the value for newAdminGroupId contains a space; for example Software Group, open wkplc.properties and add the values for newAdminId, newAdminPw, and newAdminGroupId. Save changes and run the ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=dmgr_password

    If standalone LDAP security is already enabled on the Deployment Manager cell, delay running the wp-change-portal-admin-user task until after the cluster-node-config-cluster-setup (static cluster) or cluster-node-config-dynamic-cluster-setup (dynamic cluster) task completes. After running the wp-change-portal-admin-user task, start or restart the WebSphere_Portal server to use the updated administrator user ID. The WebSphere Portal administrative user ID and administrative group must exist in the Deployment Manager before running the wp-change-portal-admin-user task. -DnewAdminPw is an optional parameter to update the Administrative password in wkplc.properties if required.

  12. Restart the WebSphere_Portal server on Cluster A. Verify that Cluster A is functionally intact by spot checking pages and portlets and then verify that Portal B is functionally intact by spot checking pages and portlets that you deployed into Portal B before it was federated. Any discrepancies or errors should be corrected now before continuing.

      If Portal B is using a non-default Portal server administrative ID, not wpsadmin, the server will not be functional until the cluster configuration is complete and the Portal administrative ID has been configured to match the Cells security settings.

  13. Define a cluster using Portal B as the basis:

    1. Run the ConfigEngine.sh cluster-node-config-cluster-setup -DWasPassword=dmgr_password

    2. Configure the cluster to use an external Web server to take advantage of features such as workload management. Choose one of the following options:

    3. Access the Web Content Manager content through an external Web server:

      1. Log on to the dmgr console.

      2. Select Environment -> WebSphere Variables.

      3. From the Scope drop-down menu, select the Node=nodename, Server=servername option to narrow the scope of the listed variables, where Node=nodename is the node that contains the application server.

      4. Update the WCM_HOST variable with the fully qualified host name used to access the WebSphere Portal server through the Web server or On Demand Router.

      5. Update the WCM_PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.

    4. Add a new JCRSeedBus cluster bus member and remove the previous server bus member:

      1. Log on to the Deployment Manager Administrative Console.

      2. Navigate to Service Integration -> Buses and then click JCRSeedBus.

      3. Under the Topology heading, click Bus members.

      4. Click Add.

      5. Click the Cluster radio button to define the type of new bus member and then select the name of this newly created Portal cluster from the drop-down menu. Click Next to continue.

      6. Ensure that the Enable Messaging Engine Policy Assistance checkbox is checked. Then choose the required messaging engine policy setting; refer to Messaging engine policy assistance for information.

      7. Click Next.

      8. Select the Data store radio button and then click Next.

      9. Click the name of the first messaging engine listed in the table.

      10. Enter the following information on the Specify data store properties panel:

        Data store fields that need information.

        Field Value
        Data source JNDI name jdbc/data_source_name, where data_source_name is the value for the jcr.DataSourceName property in wkplc_dbdomain.properties file located in the WP_PROFILE/ConfigEngine/properties directory of the primary node.
        Schema name Value of the jcr.DbSchema property in wkplc_dbdomain.properties.
        Authentication alias Choose the entry in the drop-down list whose name contains the JCR data source name.

      11. Ensure that the Create tables checkbox is checked and then click Next to continue.

      12. The Configure messaging engines panel displays containing the list of messaging engines. If any additional messaging engines are displayed, repeat the steps to configure each additional messaging engine in the table. Then click Next to continue.

      13. Review the heap sizes on the Tune performance parameters panel. Click Next to continue.

          To change the values, click the Change heap sizes checkbox and enter new values in the Proposed heap sizes text fields.

      14. The Summary panel displays, which allows you to review the messaging engine configuration changes. Click Previous if you need to go back and make additional changes or click Finish to complete the configuration process.

      15. Click Save to save the changes to the master configuration.

      16. Synchronize changes to the primary node.

    5. Save changes and then restart the dmgr, the node agent(s), server1, and the WebSphere_Portal servers.

  14. Install any additional nodes to the cell to support additional cluster members for Cluster B identically to the primary node, and then federate as them as secondary nodes and define as cluster members on these nodes. For information about adding additional nodes navigate to Install WebSphere Portal -> Set up a cluster on IBM i -> Prepare additional nodes on IBM i. You can add additional nodes and/or vertical clusters.

  15. Restart the server1 and WebSphere_Portal servers on Cluster A and Cluster B.

  16. After setting up multiple clusters, there are additional tasks that you can perform to ensure a balanced workload and failover support.

    • Update the web server configuration to enable user requests to be routed to the new cluster. Refer "Routing requests across clusters" for information about using a web server with multiple clusters in a cell.

    • Update database configuration to share database domains between clusters. Refer to "Sharing database domains between clusters for information about redundancy and failover support.

  17. If you entered passwords in any of the properties files while creating cluster, you should remove them for security purposes. See "Deleting passwords from properties files" under Related tasks for information.

Installation of Cluster B is complete. It is now an independent cluster from Cluster A, which means that Cluster B can have its own configuration, set of end-user portlets, and target community. Any applications that are common between Cluster A and Cluster B are most likely infrastructure or related to administration, and special care needs to be taken to preserve their commonality between clusters and correct maintenance levels.


Parent

Set up multiple clusters on IBM i


Delete passwords from properties files

 


+

Search Tips   |   Advanced Search