Page tree
Skip to end of metadata
Go to start of metadata

To address cluster members individually during an installation operation, you can tokenize the value of the Server element's name attribute within the IBM WebSphere Configuration, using a special type of token that resembles printf argument specifiers. The BMC Middleware Automation product substitutes values for the specifiers at installation time, making it possible to reuse the Configuration on different cells, nodes, clusters, and servers without having to specify names in Server Profiles. The specifiers are designed to allow you to deploy on both vertical and horizontal clusters.

The following table lists the specifiers:

Specifier

Description

%h

Host name

Note

This token is available starting with BMC Middleware Automation version 8.6.00.010.

%c

Cell name

%n

Node name

%l

Cluster name (inherited from the ClusterName attribute)

%x

Cluster member number on current node, restarts at 1 on each node

Note

Starting with BMC Middleware Automation version 8.6.00.010, you can extend the existing number identifier %x to contain the leading zeros before the identifier numbers:

%.3x -> 001

%i

Cluster member number on current node, does not restart on each node. The default start number is 1.
You can define a custom start number, by setting the ph.wildcardClusterMemberStartNum launcher property to a positive integral value or zero.

Note

Starting with BMC Middleware Automation version 8.6.00.010, you can extend the existing number identifier %i to contain the leading zeros before the identifier numbers:

%.3i -> 001

For example, in the following XML lines of the Configuration, the Server element's name attribute has a value of %c_%n_%x. The first member that BMC Middleware Automation installs using this Configuration will have the server name cell1_Node1_Srv1. The second member on the first node will have the name cell1_Node1_Srv2. The first member on the second node will have the name cell1_Node2_Srv1.

Example

<Server developmentMode="false" name="%c_%n_%x"
    CreateCluster="true" parallelStartEnabled="true"
    serverType="APPLICATION_SERVER"
    MembersPerNode="2" ClusterName="clusterH">
</Server>

In the following example, the Server element's name attribute has a value of %c_%n_%i. In this case, the members on the first node will have the same names as in the preceding example, but the first cluster member on the second node will have the name cell1_Node2_Srv3.

Example

<Server developmentMode="false" name="%c_%n_%i"
    CreateCluster="true" parallelStartEnabled="true"
    serverType="APPLICATION_SERVER"
    MembersPerNode="2" ClusterName="clusterH">
</Server>