Modify cluster member templates using scripting

 

+

Search Tips   |   Advanced Search

 

 

Overview

You can create cluster members using the AdminConfig object and scripting.

Before starting this task, the wsadmin tool must be running.

A copy of the first cluster member that you create is stored in the cluster scope as a template. You can create the first cluster member using any existing server as a template or a default server template.

You can also create a first cluster member when you create the cluster by converting a server to a cluster. When you create a first cluster member, the template of the cluster member is stored under the scope of the cluster. Additional cluster members are created using the cluster member template stored in the cluster scope.

A cluster can be either homogeneous or heterogeneous in nature. A homogeneous cluster spans nodes that are of the same WAS version. A heterogeneous cluster spans nodes of different WAS versions. Since a cluster can contain members from nodes that run on different versions of WAS, one template will be stored for each version of the WAS node that is configured as a cluster member. The cluster member template will not exist for a given node version until you create a first member in a node of the same version. For example, if a cluster contains several V6.1 nodes and several V6 nodes, there will be one cluster member template for the V6.1 node and one for the V6 node, such as the following:

Therefore, when you make a configuration change to cluster members, make the same configuration change to the template that is stored in the corresponding cluster scope in order to keep the template in sync with the existing members. Similarly, when you make a configuration change to the template, you should make the same configuration change to existing cluster members.

You can modify a cluster member template using the wsadmin tool similar to how you modify a server. You cannot modify a cluster member template using the console.

To modify a cluster member template using wsadmin...

 

Procedure

  1. Obtain the cluster template under the cluster scope and modify the attributes of the template.

    Use Jacl:

    set c [$AdminConfig listTemplates Server cluster/servers/V6.1]
    puts [$AdminConfig showall $c]
    $AdminConfig modify $c {{attrName attrVal}}

    Use Jython:

    c = AdminConfig.listTemplates('Server','cluster/servers/V6.1')
    print AdminConfig.showall(c)
    AdminConfig.modify(c, [[attrName, attrval]])

  2. Save the configuration changes.

  3. In a network deployment environment only, synchronize the node.

Create cluster members using scripting
Use the AdminConfig object for scripted administration

 

Related Reference

Commands for the AdminConfig object