WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Adding members to a cluster

You create an application server as a member of a configured cluster.

Before you begin

You must create a cluster if you do not already have a configured cluster.

About this task

If you are migrating from a previous version of WebSphere Application Server, you can upgrade a portion of the nodes in a cell, while leaving others at the other release level. For a time, you might be managing servers that are at a previous release level and servers that are running at the newer release in the same cell.

When you create a cluster, you specify the node on which the first cluster member resides. In a mixed cell environment, you can use any server from within that node group to create a new cluster member. For example, if the node group to which the cluster belongs consists of a v6.1 node, and a v5.1, you can use a server from either the v5.1 or the v6.1 node to create a new cluster member.

To create a new cluster member, view information about existing cluster members, or manage existing cluster members:

Procedure

  1. In the administrative console, click Servers > Clusters > cluster_name > Cluster members. The Cluster members page lists members of a cluster, and for each member indicates:
    • The node on which the member resides.
    • The version of the application server. This information shows whether the cluster is a mixed cluster.
    • The configured weight for the member.
    • The runtime weight for the member. This weight indicates the proportionate workload that is currently directed to this cluster member.
    • Whether the member is started, stopped, or encountering problems.
  2. Click New to create a new cluster member.

    Clicking New starts the Create a new cluster member wizard. This wizard allows you to add new members to an already configured cluster.

    A copy of the first cluster member that you create is stored as part of the cluster data and becomes the template for all additional cluster members that you create. In a mixed environment, there is a separate template for each node version that is part of the cluster. For example, if the cluster includes a v5.1 node and a v6.1 node, a v5.1 and a V6.1 template is created. When you create a new cluster member, the node you select for the cluster members determines which template is used to create the cluster member.

    1. Specify a name for the cluster member (application server). The name must be unique within the node.
    2. Select the node for the cluster member.
    3. [z/OS] Specify a short name for this cluster member. The short name is the default z/OS job name and identifies the cluster member to the native facilities of the operating system, such as Workload Manager (WLM), Automatic Restart Manager, SAF (for example, RACF), started task control, and others.
    4. Specify the server weight.

      The weight value you specify controls the number of requests that are directed to the application server. Even though you specify a value of 0 to 20 as the weight of a server, the weight that is given to the server as a member of a cluster is a proportion that is based on the weight assigned to the server (the numerator) and the sum of the weights of all members of the cluster (the denominator).

      When you add a new member to a cluster, the number of requests that are sent to each server in the cluster decreases, assuming the number of requests coming into the cluster stays the same. Similarly when you remove a new member from a cluster, the number of requests that are sent to each server in the cluster increases, assuming the number of requests coming into the cluster stays the same.

      For example, if you have a cluster that consists of members A, B, and C with weights 2, 3, and 4, respectively, 2/9 of the requests are assigned to member A, 3/9 are assigned to member B, and 4/9 are assigned to member C. If a new member, member D, is added to the cluster and member D has a weight of 5, member A now gets 2/14 of the requests, member B gets 3/14 of the requests, member C gets 4/14 of the requests, and member D gets 5/14 of the requests.

      [z/OS] On the z/OS platform, weight is used to balance some of the workload types, but others are balanced by the z/OS system.
      • For HTTP requests, weights are used to distribute HTTP traffic between the Web server plug-in and the controller handling the clustered application server. Assign a higher weight value to the application server that should receive the HTTP traffic.
      • For Web services calls, information is transferred from a servant in one application server to a controller in another application server. The application server that receives the call has the highest weight value.
      • Weight has no affect on Internet Inter-ORB Protocol (IIOP) requests. IIOP requests are distributed to the correct application server using the sysplex distributor.
    5. Specify whether to generate unique HTTP ports.
    6. Click Add Member to finish defining the cluster member. The first cluster member for this cluster is used as the template for this cluster member. You can repeat these steps to define other cluster members.
    7. When you finish defining additional cluster members, review the summary information for the new cluster members. If you have to change any of the property settings for any of the new members, select that cluster member, and then click Edit. When you finish changing the property settings, click Update Member to save your changes.
    8. When you finish defining new cluster members, click Next to view the summary page for the cluster, and then click Finish to create these new cluster members.
  3. Click Review, select Synchronize changes with Nodes, and then click Save to save your changes.

Results

You created application servers that are members of an existing server cluster.

What to do next

If when you created the new members, you chose to generate unique ports, update the alias list for the virtual host that you plan to use with the new servers.

You can:

If any of the applications, that you plan to deploy on members of this cluster, require the functionality of one of the product feature packs, verify that the same level of that feature pack is installed on all of the cluster members. See the topic "Clusters and workload management" for more information about feature pack requirements in a cluster environment.




In this information ...


Related reference

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/trun_wlm_member.html