Install multiple clusters in a single cell on z/OS

When creating multiple clusters in a single cell, you create the first cluster in the cell, which includes installing the primary server, transferring database, configuring security, creating the cluster, and validating the cluster. You then create the subsequent clusters, which includes installing the primary server, transferring database, creating the cluster, and validating the cluster; you do not configure security on the subsequent clusters. You can then add additional nodes to the clusters that you created.

To install multiple clusters in a single cell:

  1. Create the first cluster in the cell:

    1. Start the WebSphere Portal Customization Dialog.

    2. In the Portal configuration panel, select Basic configuration tasks.

    3. Select Configure base portal into a federated WAS profile.

    4. Select Configure base portal into primary node.

    5. Select Define variables.

      • Review WebSphere variables (mandatory)

      • System locations

      • System environment configuration

      • Server configuration

      • Portal configuration

      On the Server configuration panel, set Multiple cluster configuration and Node is in the first cluster to Y.

    6. Generate the customization jobs.

    7. Follow the Customization Dialog instructions for submitting the customization jobs.

    8. After running all required jobs to install the primary server, set up database, change driver type, if necessary, and transfer data. See Related tasks for links to the appropriate information.

    9. After running all required jobs to transfer database, configure security. See Configuring WebSphere Portal to use a user registry in a cluster.

    10. After running all required jobs to configure security, perform the following steps to create a new cluster in a Network Deployment cell:

      1. Start the WebSphere Portal Customization Dialog.

      2. In the Portal configuration panel, select Advanced configuration tasks.

      3. Select Advanced Cluster Scenarios.

      4. Select one of the following options depending on the type of cluster you are creating:

        • Configure a WebSphere Portal static cluster

        • Configure a WebSphere Portal dynamic cluster

      5. Select Define variables.

      6. Select the option for the variables you want to define and follow the panels to define the variables. The following options are available:

        • Database variables

        • Deployment manager variables

        • Stand-alone LDAP variables (conditionally)

        • VMM database variables (conditionally)

      7. Generate the customization jobs.

      8. Follow the Customization Dialog instructions for submitting the customization jobs.

    11. Validate the cluster.

  2. If you are adding a dynamic cluster and IBMWebSphere Virtual Enterprise is not already installed on Portal B, install it, apply all required ifixes, and augment the wp_profile profile to make it compatible with WebSphere Extended Deployment Operations Optimization. See the "Planning the product installation" link below for information about installing WebSphere Virtual Enterprise. Profile augmentation is performed using the Profile Management Tool (PMT) graphical interface on systems that support it or through the manageprofiles command that is available on all systems. When using the graphical interface as discussed in the link below, make sure you select Operations Optimization when choosing the type of augmentation to perform. When using the manageprofiles command as discussed in the link below, be sure to follow the instructions to augment a stand-alone application server profile.

  3. Create the next cluster in the cell:

      Repeat this step until all required clusters are created in the cell.

      1. Start the WebSphere Portal Customization Dialog.

      2. In the Portal configuration panel, select Basic configuration tasks.

      3. Select Configure base portal into a federated WAS profile.

      4. Select Configure base portal into primary node.

      5. Select Define variables.

        • Review WebSphere variables (mandatory)

        • System locations

        • System environment configuration

        • Server configuration

        • Portal configuration

        On the Server configuration panel, set Multiple cluster configuration to Y and set Node is in the first cluster to N.

  4. Generate the customization jobs.

  5. Follow the Customization Dialog instructions for submitting the customization jobs.

  6. After running all required jobs to install the primary server, set up database, change driver type, if necessary, and transfer data. See Related tasks for links to the appropriate information.

  7. After running all required jobs to transfer database, perform the following steps create a new cluster in the Network Deployment cell:

    1. Start the WebSphere Portal Customization Dialog.

    2. In the Portal configuration panel, select Advanced configuration tasks.

    3. Select Advanced Cluster Scenarios.

    4. Select one of the following options depending on the type of cluster you are creating:

      • Configure a WebSphere Portal static cluster

      • Configure a WebSphere Portal dynamic cluster

    5. Select Define variables.

    6. Select the option for the variables you want to define and follow the panels to define the variables. The following options are available:

      • Database variables

      • Deployment manager variables

      • Stand-alone LDAP variables (conditionally)

      • VMM database variables (conditionally)

    7. Generate the customization jobs.

    8. Follow the Customization Dialog instructions for submitting the customization jobs.

  8. Validate the cluster.

  • Configure additional cluster nodes for the first and subsequent clusters:

      Repeat this step until all additional nodes are configured for the required clusters in the cell.
      Restriction: If primary node is a static cluster, choose the static option for additional cluster nodes. If primary node is a dynamic cluster, choose the dynamic option for additional cluster nodes.

      1. Start the WebSphere Portal Customization Dialog.

      2. In the Portal configuration panel, select Basic configuration tasks.

      3. Select Configure base portal into a federated WAS profile.

      4. Select Configure base portal into secondary node.

      5. Select Define variables.

        • Review WebSphere variables (mandatory)

        • System locations

        • System environment configuration

        • Server configuration

        • Portal configuration

        On the Server configuration panel, set Multiple cluster configuration to Y.

  • Generate the customization jobs.

  • Follow the Customization Dialog instructions for submitting the customization jobs.

  • Add the additional node into the appropriate existing cluster:

    If you are creating a multiple, dynamic cluster, remember to install WebSphere Virtual Enterprise on the additional node and augment the Portal profile with WebSphere Virtual Enterprise.

    1. Start the WebSphere Portal Customization Dialog.

    2. In the Portal configuration panel, select Advanced configuration tasks.

    3. Select Advanced Cluster Scenarios.

    4. Select one of the following options depending on the type of cluster you are creating:

      • Configure a WebSphere Portal static cluster

      • Configure a WebSphere Portal dynamic cluster

    5. Select Define variables.

    6. Select the option for the variables you want to define and follow the panels to define the variables. The following options are available:

      • Database variables

      • Deployment manager variables

      • Stand-alone LDAP variables (conditionally)

      • VMM database variables (conditionally)

    7. Generate the customization jobs.

    8. Follow the Customization Dialog instructions for submitting the customization jobs.

  • Validate the cluster.

    The multiple cluster configuration is now complete. Each cluster is independent from the other clusters, which means that each cluster can have its own configuration, set of end-user portlets, and target community. Applications that are common between the clusters are most likely infrastructure or related to administration and special care needs to be taken to preserve their commonality.

     


    +

    Search Tips   |   Advanced Search