Setting up a clustered production environment on z/OS

When creating a cluster of IBM® WebSphere® Portal servers, you can start with a standalone production server as your primary node or you can start with an existing IBM WebSphere Application Server managed server node. After creating the cluster with either option as the starting point, you can begin to add additional nodes to meet your business needs.

About this task

Choose one of the following options to set up your clustered production environment on z/OS®:
  • Creating a cluster using a standalone production server
    After configuring your standalone production server, you may find that your business needs have grown and that a clustered production server will meet your company's growing demands. With a few additional steps, you can cluster your standalone production server.
  • Creating a cluster using managed server nodes
    You can install and configure IBM WebSphere Portal into a IBM WebSphere Application Server for z/OS managed server node in an existing Network Deployment cell instead of creating a standalone WebSphere Portal production server. You can then proceed to create a cluster using the primary node and adding additional nodes to the cluster now or in the future to meet your needs for a highly available production environment.
  • Preparing additional nodes on z/OS
    After installing and configuring your primary node and creating the cluster, using either the standalone server or a managed server node, you can create your secondary nodes. You must install IBM WebSphere Portal on each node and then configure the node to access the database and user registry before adding it to the cluster.
  • Configuring the HTTP session failover
    Enable HTTP session failover in your cluster to enable multiple cluster members to serve data in the event that one of them fails. Use the following information to configure your IBM WebSphere Portal for HTTP session failover. This information includes instructions on configuring the HTTP server for the sysplex distributor. If horizontal clustering is used in a sysplex, it is recommended to configure an internal or external HTTP server with the WebSphere Application Server for z/OS plug-in and the sysplex distributor. The sysplex distributor provides real load balancing and high availability within a sysplex and defines a Dynamic Virtual IP Address (DVIPA). DVIPA is also called a cluster address. The DVIPA distributes TCP/IP requests within a sysplex depending on the workload.
  • Configuring search in a cluster on z/OS
    IBM WebSphere Portal provides two distinct search capabilities. You can use both types of search capabilities in a clustered environment.
  • Setting up multiple clusters on z/OS
    When configuring multiple clusters, you must plan for this configuration in advance. In a single cluster deployment, you create the primary server and secondary, or additional, nodes. In a multiple cluster deployment, you create the primary (or first) cluster and then you create secondary (or subsequent) clusters. First you install the primary server to create the first cluster in the cell. All multiple clusters are installed into a managed node.
  • Parent topic: Installing on z/OS
    • Related tasks:
  • Secondary node fails to start after being added to the cluster with javax.jcr.RepositoryException exception

    • Related information