Intelligent Management: dynamic cluster administrative tasks
Use the dynamic cluster commands to view or edit the dynamic clusters, without using the administrative console.
Use the following commands to create dynamic clusters, add or remove servers from clusters, list dynamic clusters, or modify dynamic clusters:
- createDynamicCluster
- createPHPDynamicCluster
- createDynamicClusterFromStaticCluster
- createDynamicClusterFromForeignServers
- createODRDynamicCluster
- addForeignServersToDynamicCluster
- removeForeignServersFromDynamicCluster
- deleteDynamicCluster
- getDynamicClusterMembers
- getDynamicClusterOperationalMode
- getDynamicClusterMembershipPolicy
- getDynamicClusterServerType
- getDynamicClusterMinInstances
- getDynamicClusterMaxInstances
- getDynamicClusterVerticalInstances
- getDynamicClusterIsolationProperties
- listDynamicClusters
- listDynamicClusterIsolationGroups
- listDynamicClusterIsolationGroupMembers
- modifyDynamicClusterIsolationProperties
- setDynamicClusterOperationalMode
- setDynamicClusterMembershipPolicy
- setDynamicClusterMinInstances
- setDynamicClusterMaxInstances
- setDynamicClusterVerticalInstances
- testDynamicClusterMembershipPolicy
- createNonWASDynamicCluster
- Edit the dynamic cluster server template
createDynamicCluster
The createDynamicCluster command creates a new dynamic cluster.
Required parameters
- membershipPolicy: Membership policy. (String, required)
Optional parameters
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- numVerticalInstances: Number of instances that can start on the same node by creating vertical instances. Specify an integer value.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- clusterProperties: Cluster
properties. (String, optional) We can specify the following options:
- preferLocal: whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
- createDomain: Specifies that a replication domain is created for this cluster. Replication
domains can be created only for WebSphere Application Server application servers.
The valid values are true or false.
- coreGroup: Name of the core group for the dynamic cluster. You only need to specify the core group for WebSphere Application Server application servers. The value can be DefaultCoreGroup or the core group name.
- templateName: Name of the server template. The valid input includes the following values:
- For WebSphere Application Server dynamic clusters: default, cell_name/node/was_server_name
Deprecated feature: The defaultXD and defaultXDZOS server templates used when creating a dynamic cluster are deprecated. Use the default or defaultZOS server template instead.depfeat
- (zos) clusterShortName:
For z/OS platforms, specifies
the short name of the cluster. After the dynamic cluster has been created, we can use the AdminTask changeClusterShortName command to update this field.
- (zos) serverSpecificShortNames: For z/OS platforms, specifies the specific short name of cluster member in a comma-separated list format, for example: SSN1,SSN2. Use commas to separate multiple short names. If we do not provide enough short names to be used for all of the cluster members, then the remaining cluster members are assigned generated generic short names, such as BBOS001, BBOS002, and so on. After the dynamic cluster has been created, we can update this list with the serverSpecificShortNames custom property. This property is set on the dynamic cluster. To change this property after the dynamic cluster has been created, we can use the AdminTask changeServerSpecificShortName command.
- preferLocal: whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
Return value
The command returns javax.management.ObjectName value of the dynamic cluster created.
Batch mode example
- Jacl:
- $AdminTask createDynamicCluster dcName {-membershipPolicy node_nodegroup='ngName'}
or
$AdminTask createDynamicCluster dcName {-membershipPolicy "node_nodegroup = 'ngName'" -dynamicClusterProperties "{operationalMode automatic}{minInstances 0}{maxInstances -1}{numVerticalInstances 1}{serverInactivityTime 1440}" -clusterProperties "{preferLocal false}{createDomain false}{templateName default}{coreGroup DefaultCoreGroup} {clusterShortName BBOC001}{serverSpecificShortNames BBOS001,BBOS002}"} - Jython string...
AdminTask.createDynamicCluster(dcName,'[-membershipPolicy "node_nodegroup = \'ngName\'" -dynamicClusterProperties "{{operationalMode automatic}{minInstances 0}{maxInstances -1}{numVerticalInstances 1}{serverInactivityTime 1440}}" -clusterProperties "{{preferLocal false}{createDomain false}{templateName default}{coreGroup DefaultCoreGroup} {clusterShortName BBOC001}{serverSpecificShortNames BBOS001,BBOS002}}"]')or, if you are running on WAS v7 or later:
AdminTask.createDynamicCluster('dcName','[-membershipPolicy "node_nodegroup = \'ngName\'" -dynamicClusterProperties "[[operationalMode automatic][minInstances 0][maxInstances -1][numVerticalInstances 1][serverInactivityTime 1440]]" -clusterProperties "[[preferLocal false][createDomain false][templateName default][coreGroup DefaultCoreGroup] [clusterShortName BBOC001][serverSpecificShortNames BBOS001,BBOS002]]"]')
Interactive mode
- Jacl:
- $AdminTask createDynamicCluster {-interactive}
- Jython string...
- AdminTask.createDynamicCluster ('[-interactive]')
createPHPDynamicCluster
The createPHPDynamicCluster command creates a new PHP dynamic cluster.
Required parameters
- membershipPolicy: Membership policy subexpression. (String, required)
Optional parameters
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- numVerticalInstances: Number of instances that can start on the same node by creating vertical instances. Specify an integer value.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- clusterProperties: Name of the server template. The valid input includes the templateName value:
- For PHP dynamic clusters: APACHE13_PHP4, APACHE13_PHP5, APACHE20_PHP4, APACHE20_PHP5, APACHE22_PHP4, APACHE22_PHP5, cellName/nodeName/php_serverName.
Return value
The command returns javax.management.ObjectName value of the dynamic cluster created.
Batch mode example
- Jacl:
- $AdminTask createPHPDynamicCluster dcName {-membershipPolicy "node_property$APACHE_2_0 IS NOT NULL AND node_property$PHP_5 IS NOT NULL"}
or
$AdminTask createPHPDynamicCluster dcName {-membershipPolicy "node_property$APACHE_2_0 IS NOT NULL AND node_property$PHP_5 IS NOT NULL" -dynamicClusterProperties "{operationalMode automatic}{minInstances 1} {maxInstances -1}{numVerticalInstances 1}" -clusterProperties "{templateName APACHE20_PHP5}"} - Jython string...
AdminTask.createPHPDynamicCluster(dcName,'[-membershipPolicy "node_property$APACHE_2_0 IS NOT NULL AND node_property$PHP_5 IS NOT NULL" -dynamicClusterProperties "{{operationalMode automatic}{minInstances 1} {maxInstances -1}{numVerticalInstances 1}}" -clusterProperties "{{templateName APACHE20_PHP5}}"]')or, if you are running on WAS v7 or later:
AdminTask.createPHPDynamicCluster('dcName','[-membershipPolicy "node_property$APACHE_2_0 IS NOT NULL AND node_property$PHP_5 IS NOT NULL" -dynamicClusterProperties "[[operationalMode automatic][minInstances 1] [maxInstances -1][numVerticalInstances 1]]" -clusterProperties "[[templateName APACHE20_PHP5]]"]')
Interactive mode
- Jacl:
- $AdminTask createPHPDynamicCluster {-interactive}
- Jython string...
- AdminTask.createPHPDynamicCluster ('[-interactive]')
createDynamicClusterFromStaticCluster
The createDynamicClusterFromStaticCluster command creates a new dynamic cluster from an existing static cluster.
Optional parameters
- templateName: Name of the existing static cluster member template. The format of the name must be in the cell_name/node/server_name format.
If the template is not specified, an existing static cluster member
template is randomly chosen. If no members exist, the default server template is used. (String, optional)
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
Return value
The command returns the javax.management.ObjectName value of the dynamic cluster created.
Batch mode example
- Jacl:
- $AdminTask createDynamicClusterFromStaticCluster clusterName {-templateName cellName/nodeName/serverName}
- Jython string...
- AdminTask.createDynamicClusterFromStaticCluster('clusterName')
Interactive mode
- Jacl:
- $AdminTask createDynamicClusterFromStaticCluster {-interactive}
- Jython string...
- AdminTask.createDynamicClusterFromStaticCluster ('[-interactive]')
createDynamicClusterFromForeignServers
The createDynamicClusterFromForeignServers command creates a new dynamic cluster of assisted life-cycle servers. Create representations of these servers with an administrative task or in the administrative console before creating a dynamic cluster.
Required parameters
- foreignServers [[node1 server_name1 ][node2 server_name2] ...]: Node and server names of the existing other middleware servers. (String, required)
Optional parameters
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
Return value
The command returns the javax.management.ObjectName identification of the server type that you updated.
Batch mode example
- Jacl:
$AdminTask createDynamicClusterFromForeignServers dcName {-foreignServers {{nodeName1 serverName1} {nodeName2 serverName2}}} - Jython string...
- AdminTask.createDynamicClusterFromForeignServers('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode
- Jacl:
- $AdminTask createDynamicClusterFromForeignServers {-interactive}
- Jython string...
- AdminTask.createDynamicClusterFromForeignServers ('[-interactive]')
createODRDynamicCluster
Use the createODRDynamicCluster command to create on demand router dynamic clusters.
Target object:
Name of the dynamic cluster.
Required parameters
membershipPolicy: Membership policy.
Optional parameters
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- numVerticalInstances: Number of instances that can start on the same node by creating vertical instances. Specify an integer value.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- clusterProperties: Cluster
properties. (String, optional) We can specify the following options:
- preferLocal: whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
- createDomain: Specifies that a replication domain is created for this cluster. Replication
domains can be created only for WebSphere Application Server application servers.
The valid values are true or false.
- coreGroup: Name of the core group for the dynamic cluster. You only need to specify the core group for WebSphere Application Server application servers. The value can be DefaultCoreGroup or the core group name.
- templateName: Name of the server template. The valid input includes the following values:
- For WebSphere Application Server dynamic clusters: defaultXD, defaultXDZOS, cell_name/node/was_server_name
- (zos) clusterShortName:
For z/OS platforms, specifies
the short name of the cluster. After the dynamic cluster has been created, we can use the AdminTask changeClusterShortName command to update this field.
- (zos) serverSpecificShortNames: For z/OS platforms, specifies the specific short name of cluster member in a comma-separated list format, for example: SSN1,SSN2. Use commas to separate multiple short names. If we do not provide enough short names to be used for all of the cluster members, then the remaining cluster members are assigned generated generic short names, such as BBOS001, BBOS002, and so on. After the dynamic cluster has been created, we can update this list with the serverSpecificShortNames custom property. This property is set on the dynamic cluster. To change this property after the dynamic cluster has been created, we can use the AdminTask changeServerSpecificShortName command.
- preferLocal: whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
Batch mode example
- Jacl:
- $AdminTask createODRDynamicCluster dcName {parameters} {-membershipPolicy "node_nodegroup = 'DefaultNodeGroup' AND node_property$com.ibm.websphere.wxdopProductShortName = 'WXDOP'" -dynamicClusterProperties "{operationalMode automatic}{minInstances 2}" -clusterProperties "{templateName defaultXD}{preferLocal false}"}
- Jython string...
- AdminTask.createODRDynamicCluster('dcName', '[-membershipPolicy "node_nodegroup = 'DefaultNodeGroup' AND node_property$com.ibm.websphere.wxdopProductShortName = 'WXDOP'" -dynamicClusterProperties [[operationalMode automatic][minInstances 2]] -clusterProperties [[templateName defaultXD][preferLocal false]]]')
Interactive mode
- Jacl:
- $AdminTask createODRDynamicCluster {-interactive}
- Jython string...
- AdminTask.createODRDynamicCluster ('[-interactive]')
addForeignServersToDynamicCluster
The addForeignServersToDynamicCluster command adds foreign servers to an existing dynamic cluster.
Required parameters
- foreignServers [[node1 server_name1 ][node2 server_name1] ...]: Node and server names of the existing other middleware servers. (String, required)
Return value
The command returns the javax.management.ObjectName identification of the server type that you updated.
Batch mode example
- Jacl:
$AdminTask addForeignServersToDynamicCluster dcName {-foreignServers {{nodeName1 serverName1} {nodeName2 serverName2}}} - Jython string...
- AdminTask.addForeignServersToDynamicCluster('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode
- Jacl:
- $AdminTask addForeignServersToDynamicCluster {-interactive}
- Jython string...
- AdminTask.addForeignServersToDynamicCluster ('[-interactive]')
removeForeignServersFromDynamicCluster
The removeForeignServersFromDynamicCluster command removes foreign servers from the dynamic cluster
Required parameters
- foreignServers [[node1 server_name1 ][node2 server_name1] ...]: Node and server names of the existing other middleware servers. (String, required)
Return value
The command returns the javax.management.ObjectName identification of the server type that you updated.
Batch mode example
- Jacl:
- $AdminTask removeForeignServersFromDynamicCluster dcName {-foreignServers {{nodeName1 serverName1}{nodeName2 serverName2}}}
- Jython string...
- AdminTask.removeForeignServersFromDynamicCluster('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode
- Jacl:
- $AdminTask removeForeignServersFromDynamicCluster {-interactive}
- Jython string...
- AdminTask.removeForeignServersFromDynamicCluster ('[-interactive]')
deleteDynamicCluster
The deleteDynamicCluster deletes a dynamic cluster from the configuration.
Return value
The command returns the javax.management.ObjectName identification of the dynamic cluster that we deleted.
Batch mode example
- Jacl:
- $AdminTask deleteDynamicCluster dcName
- Jython string...
- AdminTask.deleteDynamicCluster('dcName')
Interactive mode
- Jacl:
- $AdminTask deleteDynamicCluster {-interactive}
- Jython string...
- AdminTask.deleteDynamicCluster ('[-interactive]')
getDynamicClusterMembers
The getDynamicClusterMembers command displays the members of the specified dynamic cluster and node name. If the node name is not specified, then all of the members of the dynamic cluster are displayed.
Optional parameters
- nodeName: Name of a node. (String, optional)
Return value
The command returns a list of ClusterMember objects.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterMembers dcName
- Jython string...
- AdminTask.getDynamicClusterMembers('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterMembers {-interactive}
- Jython string...
- AdminTask.getDynamicClusterMembers ('[-interactive]')
getDynamicClusterOperationalMode
The getDynamicClusterOperationalMode command displays the operational mode of the dynamic cluster.
Return value
The command returns the value of operationalMode. String.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterOperationalMode dcName
- Jython string...
- AdminTask.getDynamicClusterOperationalMode('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterOperationalMode {-interactive}
- Jython string...
- AdminTask.getDynamicClusterOperationalMode ('[-interactive]')
getDynamicClusterMembershipPolicy
The getDynamicClusterMembershipPolicy command displays the dynamic cluster membership policy.
Return value
The command returns the value of membershipPolicy. String.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterMembershipPolicy dcName
- Jython string...
- AdminTask.getDynamicClusterMembershipPolicy('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterMembershipPolicy {-interactive}
- Jython string...
- AdminTask.getDynamicClusterMembershipPolicy ('[-interactive]')
getDynamicClusterServerType
The getDynamicClusterServerType command displays the dynamic cluster server type.
Return value
The command returns the value of serverType. String.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterServerType dcName
- Jython string...
- AdminTask.getDynamicClusterServerType('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterServerType {-interactive}
- Jython string...
- AdminTask.getDynamicClusterServerType ('[-interactive]')
getDynamicClusterMinInstances
The getDynamicClusterMinInstances command displays the minimum number of cluster instances for the specified dynamic cluster.
Return value
The command returns the value of minInstances. Integer.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterMinInstances dcName
- Jython string...
- AdminTask.getDynamicClusterMinInstances('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterMinInstances {-interactive}
- Jython string...
- AdminTask.getDynamicClusterMinInstances ('[-interactive]')
getDynamicClusterMaxInstances
The getDynamicClusterMaxInstances command displays the maximum number of cluster instances for the specified dynamic cluster.
Return value
The command returns the value of maxInstances. Integer.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterMaxInstances dcName
- Jython string...
- AdminTask.getDynamicClusterMaxInstances('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterMaxInstances {-interactive}
- Jython string...
- AdminTask.getDynamicClusterMaxInstances ('[-interactive]')
getDynamicClusterVerticalInstances
The getDynamicClusterVerticalInstances command displays the number of dynamic cluster vertical stacking of instances on the node.
Return value
The command returns the value of numVerticalInstances. Integer.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterVerticalInstances dcName
- Jython string...
- AdminTask.getDynamicClusterVerticalInstances('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterVerticalInstances {-interactive}
- Jython string...
- AdminTask.getDynamicClusterVerticalInstances ('[-interactive]')
getDynamicClusterIsolationProperties
The getDynamicClusterVerticalInstances command displays the dynamic cluster isolation properties.
Return value
The command returns the value of isolationGroup and strictIsolationEnabled. String.
Batch mode example
- Jacl:
- $AdminTask getDynamicClusterIsolationProperties dcName
- Jython string...
- AdminTask.getDynamicClusterIsolationProperties('dcName')
Interactive mode
- Jacl:
- $AdminTask getDynamicClusterIsolationProperties {-interactive}
- Jython string...
- AdminTask.getDynamicClusterIsolationProperties ('[-interactive]')
listDynamicClusters
The listDynamicClusters command displays all the dynamic clusters in the cell.
Return value
The command returns each of the dynamic cluster names. String.
Batch mode example
- Jacl:
- $AdminTask listDynamicClusters
- Jython string...
- AdminTask.listDynamicClusters()
Interactive mode
- Jacl:
- $AdminTask listDynamicClusters {-interactive}
- Jython string...
- AdminTask.listDynamicClusters ('[-interactive]')
listDynamicClusterIsolationGroups
The listDynamicClusterIsolationGroups command displays all the dynamic cluster isolation groups in the cell.
Return value
The command returns a list of the dynamic cluster isolation groups. String.
Batch mode example
- Jacl:
- $AdminTask listDynamicClusterIsolationGroups
- Jython string...
- AdminTask.listDynamicClusterIsolationGroups()
Interactive mode
- Jacl:
- $AdminTask listDynamicClusterIsolationGroups {-interactive}
- Jython string...
- AdminTask.listDynamicClusterIsolationGroups ('[-interactive]')
listDynamicClusterIsolationGroupMembers
The listDynamicClusterIsolationGroupMembers command displays the dynamic cluster isolation group members for the specified isolation group.
Return value
The command returns a list of the dynamic cluster isolation group members. String.
Batch mode example
- Jacl:
- $AdminTask listDynamicClusterIsolationGroupMembers isolationGroupName
- Jython string...
- AdminTask.listDynamicClusterIsolationGroupMembers('isolationGroupName')
Interactive mode
- Jacl:
- $AdminTask listDynamicClusterIsolationGroupMembers {-interactive}
- Jython string...
- AdminTask.listDynamicClusterIsolationGroupMembers ('[-interactive]')
modifyDynamicClusterIsolationProperties
The modifyDynamicClusterIsolationProperties command modifies dynamic cluster isolation properties.
Optional parameters
- isolationGroup: Name of the isolation group. (String, optional)
- strictIsolationEnabled: Indicates if strict isolation is enabled. (String, optional)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask modifyDynamicClusterIsolationProperties dcName {-isolationGroup isolationGroupName -strictIsolationEnabled true}
- Jython string...
- AdminTask.modifyDynamicClusterIsolationProperties('dcName', '[-isolationGroup isolationGroupName -strictIsolationEnabled true]')
Interactive mode
- Jacl:
- $AdminTask modifyDynamicClusterIsolationProperties {-interactive}
- Jython string...
- AdminTask.modifyDynamicClusterIsolationProperties ('[-interactive]')
setDynamicClusterOperationalMode
The setDynamicClusterOperationalMode command sets the operational mode for the dynamic cluster.
Required parameters
- operationalMode: Specifies the operational mode of the dynamic cluster. Set the value to automatic, manual, or supervised. (String, required)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask setDynamicClusterOperationalMode dcName {-operationalMode manual}
- Jython string...
- AdminTask.setDynamicClusterOperationalMode('dcName', '[-operationalMode manual]')
Interactive mode
- Jacl:
- $AdminTask setDynamicClusterOperationalMode {-interactive}
- Jython string...
- AdminTask.setDynamicClusterOperationalMode ('[-interactive]')
setDynamicClusterMembershipPolicy
The setDynamicClusterMembershipPolicy command sets the membership policy for the dynamic cluster.
Required parameters
- -membershipPolicy
- Membership policy subexpression. (String, required)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask setDynamicClusterMembershipPolicy dcName {-membershipPolicy node_nodegroup='ngName'}
- Jython string...
- AdminTask.setDynamicClusterMembershipPolicy('dcName', '[-membershipPolicy node_nodegroup=\'ngName\']')
Interactive mode
- Jacl:
- $AdminTask setDynamicClusterMembershipPolicy {-interactive}
- Jython string...
- AdminTask.setDynamicClusterMembershipPolicy ('[-interactive]')
setDynamicClusterMinInstances
The setDynamicClusterMinInstances command sets the minimum number of cluster instances for the dynamic cluster.
Required parameters
- -minInstances
- Minimum number of cluster instances. (Integer, required)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask setDynamicClusterMinInstances dcName {-minInstances 1}
- Jython string...
- AdminTask.setDynamicClusterMinInstances('dcName', '[-minInstances 1]')
Interactive mode
- Jacl:
- $AdminTask setDynamicClusterMinInstances {-interactive}
- Jython string...
- AdminTask.setDynamicClusterMinInstances ('[-interactive]')
setDynamicClusterMaxInstances
The setDynamicClusterMaxInstances command sets the maximum number of cluster instances for the dynamic cluster.
Required parameters
- -maxInstances
- Minimum number of cluster instances. (Integer, required)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask setDynamicClusterMaxInstances dcName {-maxInstances -1}
- Jython string...
- AdminTask.setDynamicClusterMaxInstances('dcName', '[-maxInstances 1]')
Interactive mode
- Jacl:
- $AdminTask setDynamicClusterMaxInstances {-interactive}
- Jython string...
- AdminTask.setDynamicClusterMaxInstances ('[-interactive]')
setDynamicClusterVerticalInstances
The setDynamicClusterVerticalInstances command sets the number of dynamic cluster vertical stacking instances on the node.
Required parameters
- -numVerticalInstances
- Number of vertical stacking of instances on a node.(Integer, required)
Return value
The return value is void.
Batch mode example
- Jacl:
- $AdminTask setDynamicClusterVerticalInstances dcName {-numVerticalInstances 2}
- Jython string...
- AdminTask.setDynamicClusterVerticalInstances('dcName', '[-numVerticalInstances 2]')
Interactive mode
- Jacl:
- $AdminTask setDynamicClusterVerticalInstances {-interactive}
- Jython string...
- AdminTask.setDynamicClusterVerticalInstances ('[-interactive]')
testDynamicClusterMembershipPolicy
The testDynamicClusterMembershipPolicy command tests the dynamic cluster membership policy to see which nodes are returned.
Required parameters
- -membershipPolicy
- Membership policy subexpression. (String, required)
Return value
The command returns a String [] list of node names.
Batch mode example
- Jacl:
- $AdminTask testDynamicClusterMembershipPolicy {-membershipPolicy node_nodegroup='ngName'}
- Jython string...
- AdminTask.testDynamicClusterMembershipPolicy('[-membershipPolicy node_nodegroup=\'ngName\']')
Interactive mode
- Jacl:
- $AdminTask testDynamicClusterMembershipPolicy {-interactive}
- Jython string...
- AdminTask.testDynamicClusterMembershipPolicy ('[-interactive]')
createNonWASDynamicCluster
The createNonWASDynamicCluster command creates a new dynamic cluster of complete life-cycle management servers.
Required parameters
- serverType: Server type. (String, required)
To see the server types, view the app_server_root\profiles\dmgr_profile\config\templates\servertypes directory.
- membershipPolicy: Membership policy subexpression. (String, required)
Optional parameters
- dynamicClusterProperties:
Dynamic cluster properties. (String, optional) We can specify the following options:
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- minInstances: Minimum number of cluster instances as an integer.
- serverInactivityTime:
Time to wait before stopping instances, in minutes.
This value is valid only when the minInstances parameter value is set to 0.
- maxInstances: Maximum number of cluster instances as an integer. If we do not want a limit to the number of cluster instances that can start, specify -1.
- numVerticalInstances: Number of instances that can start on the same node by creating vertical instances. Specify an integer value.
- operationalMode: Specifies the operational mode. The valid values are: manual, supervised, and automatic.
- clusterProperties: Cluster
properties (String, optional)
- templateName: Name of the server template. The valid input includes the following values:
- For PHP dynamic clusters: APACHE13_PHP4, APACHE13_PHP5, APACHE20_PHP4, APACHE20_PHP5, APACHE22_PHP4, APACHE22_PHP5, cellName/nodeName/php_serverName.
- For WebSphere Application Server Community Edition dynamic clusters: wasce20, cell_name/node/wasce_server_name
- For PHP dynamic clusters: APACHE13_PHP4, APACHE13_PHP5, APACHE20_PHP4, APACHE20_PHP5, APACHE22_PHP4, APACHE22_PHP5, cellName/nodeName/php_serverName.
- templateName: Name of the server template. The valid input includes the following values:
Return value
The command returns the javax.management.ObjectName value of the dynamic cluster created.
Batch mode example
- Jacl:
$AdminTask createNonWASDynamicCluster dcName {-serverType WASCE_SERVER -membershipPolicy "node_property$com.ibm.websphere.wasceProductShortName = 'WASCE' OR node_property$WASCE_2.0.0.0 IS NOT NULL" -dynamicClusterProperties "{operationalMode automatic}{minInstances 1}{maxInstances -1} {numVerticalInstances 1}" -clusterProperties "{templateName wasce20}"} - Jython string...
AdminTask.createNonWASDynamicCluster(dcName,'[-serverType WASCE_SERVER -membershipPolicy "node_property$com.ibm.websphere.wasceProductShortName = \'WASCE\' OR node_property$WASCE_2.0.0.0 IS NOT NULL" -dynamicClusterProperties "{{operationalMode automatic}{minInstances 1}{maxInstances -1} {numVerticalInstances 1}}" -clusterProperties "{{templateName wasce20}}"]')or, if you are running on WAS v7 or later:
AdminTask.createNonWASDynamicCluster('dcName','[-serverType WASCE_SERVER -membershipPolicy "node_property$com.ibm.websphere.wasceProductShortName = \'WASCE\' OR node_property$WASCE_2.0.0.0 IS NOT NULL" -dynamicClusterProperties "[[operationalMode automatic][minInstances 1][maxInstances -1] [numVerticalInstances 1]]" -clusterProperties "[[templateName wasce20]]"]')
Interactive mode
- Jacl:
- $AdminTask createNonWASDynamicCluster {-interactive}
- Jython string...
- AdminTask.createNonWASDynamicCluster('[-interactive]'))
Edit the dynamic cluster server template
Identify the dynamic cluster server template and assign the template to the serverid variable.
Batch mode example
- Jacl:
- set serverid [$AdminConfig getid /Cell:mycell/DynamicCluster:mydynamiccluster/Server:mydynamiccluster/]
- Jython string...
- serverid = AdminConfig.getid('/Cell:mycell/DynamicCluster:mydynamiccluster/Server:mydynamiccluster/')
Use the serverid variable to modify, create, or delete configuration objects in the dynamic cluster server template.
Related tasks
Related information: