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.
After using any of these commands that changes the configuration, be sure to use the AdminConfig.save() command to save the changes.
createDynamicCluster
Create 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: 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.
- -clusterProperties: Cluster properties. (String, optional) We can specify the following options:
- preferLocal: Specifies whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
- createDomain: 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 WAS 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 WAS dynamic clusters: default, cell/node/was_server
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
- 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.
- 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. Set on the dynamic cluster. To change this property with scripting after the dynamic cluster has been created, we can use the AdminTask changeServerSpecificShortName command.
Return value.
The command returns javax.management.ObjectName value of the dynamic cluster that we created.
Batch mode example usage
- Use 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} (ZOS) {clusterShortName BBOC001}{serverSpecificShortNames BBOS001,BBOS002}"}
- Use 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} (ZOS) {clusterShortName BBOC001}{serverSpecificShortNames BBOS001,BBOS002}}"]')
or, if we are running on WAS v7.0 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] (ZOS) [clusterShortName BBOC001][serverSpecificShortNames BBOS001,BBOS002]]"]')
Interactive mode example usage
- Use Jacl:
$AdminTask createDynamicCluster {-interactive}
- Use Jython string:
AdminTask.createDynamicCluster ('[-interactive]')
createPHPDynamicCluster
Create 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: 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.
- -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 that we created.
Batch mode example usage
- Use 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}"}
- Use 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 we are running on WAS v7.0 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 example usage
- Use Jacl:
$AdminTask createPHPDynamicCluster {-interactive}
- Use Jython string:
AdminTask.createPHPDynamicCluster ('[-interactive]')
createDynamicClusterFromStaticCluster
Create 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/node/server 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: 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.
Return value.
The command returns the javax.management.ObjectName value of the dynamic cluster that we created.
Batch mode example usage
- Use Jacl:
$AdminTask createDynamicClusterFromStaticCluster clusterName {-templateName cellName/nodeName/serverName}
- Use Jython string:
AdminTask.createDynamicClusterFromStaticCluster('clusterName')
Interactive mode example usage
- Use Jacl:
$AdminTask createDynamicClusterFromStaticCluster {-interactive}
- Use Jython string:
AdminTask.createDynamicClusterFromStaticCluster ('[-interactive]')
createDynamicClusterFromForeignServers
Create 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.
Deprecated feature: Assisted and Complete Lifecycle servers have been deprecated in WAS v9.0. Migrate WebSphere Liberty servers to a Liberty Collective configuration. There is no recommended migration action for other server types.depfeat
Required parameters
- -foreignServers [[node1 server1 ][node2 server2] ...]: 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: 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.
Return value.
The command returns the javax.management.ObjectName identification of the server type that you updated.
Batch mode example usage
- Use Jacl:
$AdminTask createDynamicClusterFromForeignServers dcName {-foreignServers {{nodeName1 serverName1} {nodeName2 serverName2}}}
- Use Jython string:
AdminTask.createDynamicClusterFromForeignServers('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode example usage
- Use Jacl:
$AdminTask createDynamicClusterFromForeignServers {-interactive}
- Use Jython string:
AdminTask.createDynamicClusterFromForeignServers ('[-interactive]')
createODRDynamicCluster
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: 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.
- -clusterProperties: Cluster properties. (String, optional) We can specify the following options:
- preferLocal: Specifies whether enterprise bean requests are routed to the node on which the client resides when possible. The valid values are true or false.
- createDomain: That a replication domain is created for this cluster. Replication domains can be created only for WAS 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 WAS 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 WAS dynamic clusters: defaultXD, defaultXDZOS, cell/node/was_server
- 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.
- 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. Set on the dynamic cluster. To change this property with scripting after the dynamic cluster has been created, we can use the AdminTask changeServerSpecificShortName command.
Batch mode example usage
- Use 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}"}
- Use 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 example usage
- Use Jacl:
$AdminTask createODRDynamicCluster {-interactive}
- Use Jython string:
AdminTask.createODRDynamicCluster ('[-interactive]')
addForeignServersToDynamicCluster
Add foreign servers to an existing dynamic cluster.
Required parameters
- -foreignServers [[node1 server1 ][node2 server1] ...]: 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 usage
- Use Jacl:
$AdminTask addForeignServersToDynamicCluster dcName {-foreignServers {{nodeName1 serverName1} {nodeName2 serverName2}}}
- Use Jython string:
AdminTask.addForeignServersToDynamicCluster('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode example usage
- Use Jacl:
$AdminTask addForeignServersToDynamicCluster {-interactive}
- Use Jython string:
AdminTask.addForeignServersToDynamicCluster ('[-interactive]')
removeForeignServersFromDynamicCluster
Remove foreign servers from the dynamic cluster
Required parameters
- -foreignServers [[node1 server1 ][node2 server1] ...]: 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 usage
- Use Jacl:
$AdminTask removeForeignServersFromDynamicCluster dcName {-foreignServers {{nodeName1 serverName1}{nodeName2 serverName2}}}
- Use Jython string:
AdminTask.removeForeignServersFromDynamicCluster('dcName', '[-foreignServers [[nodeName1 serverName1] [nodeName2 serverName2]]]')
Interactive mode example usage
- Use Jacl:
$AdminTask removeForeignServersFromDynamicCluster {-interactive}
- Use Jython string:
AdminTask.removeForeignServersFromDynamicCluster ('[-interactive]')
deleteDynamicCluster
Delete a dynamic cluster from the configuration.
Return value.
The command returns the javax.management.ObjectName identification of the dynamic cluster that you deleted.
Batch mode example usage
- Use Jacl:
$AdminTask deleteDynamicCluster dcName
- Use Jython string:
AdminTask.deleteDynamicCluster('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask deleteDynamicCluster {-interactive}
- Use Jython string:
AdminTask.deleteDynamicCluster ('[-interactive]')
getDynamicClusterMembers
Display 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 usage
- Use Jacl:
$AdminTask getDynamicClusterMembers dcName
- Use Jython string:
AdminTask.getDynamicClusterMembers('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMembers {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterMembers ('[-interactive]')
getDynamicClusterOperationalMode
Display the operational mode of the dynamic cluster.
Return value.
The command returns the value of operationalMode. String.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterOperationalMode dcName
- Use Jython string:
AdminTask.getDynamicClusterOperationalMode('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterOperationalMode {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterOperationalMode ('[-interactive]')
getDynamicClusterMembershipPolicy
Display the dynamic cluster membership policy.
Return value.
The command returns the value of membershipPolicy. String.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMembershipPolicy dcName
- Use Jython string:
AdminTask.getDynamicClusterMembershipPolicy('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMembershipPolicy {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterMembershipPolicy ('[-interactive]')
getDynamicClusterServerType
Display the dynamic cluster server type.
Return value.
The command returns the value of serverType. String.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterServerType dcName
- Use Jython string:
AdminTask.getDynamicClusterServerType('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterServerType {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterServerType ('[-interactive]')
getDynamicClusterMinInstances
Display the minimum number of cluster instances for the specified dynamic cluster.
Return value.
The command returns the value of minInstances. Integer.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMinInstances dcName
- Use Jython string:
AdminTask.getDynamicClusterMinInstances('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMinInstances {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterMinInstances ('[-interactive]')
getDynamicClusterMaxInstances
Display the maximum number of cluster instances for the specified dynamic cluster.
Return value.
The command returns the value of maxInstances. Integer.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMaxInstances dcName
- Use Jython string:
AdminTask.getDynamicClusterMaxInstances('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterMaxInstances {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterMaxInstances ('[-interactive]')
getDynamicClusterVerticalInstances
Display 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 usage
- Use Jacl:
$AdminTask getDynamicClusterVerticalInstances dcName
- Use Jython string:
AdminTask.getDynamicClusterVerticalInstances('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterVerticalInstances {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterVerticalInstances ('[-interactive]')
getDynamicClusterIsolationProperties
Display the dynamic cluster isolation properties.
Return value.
The command returns the value of isolationGroup and strictIsolationEnabled. String.
Batch mode example usage
- Use Jacl:
$AdminTask getDynamicClusterIsolationProperties dcName
- Use Jython string:
AdminTask.getDynamicClusterIsolationProperties('dcName')
Interactive mode example usage
- Use Jacl:
$AdminTask getDynamicClusterIsolationProperties {-interactive}
- Use Jython string:
AdminTask.getDynamicClusterIsolationProperties ('[-interactive]')
listDynamicClusters
Display all the dynamic clusters in the cell.
Return value.
The command returns each of the dynamic cluster names. String.
Batch mode example usage
- Use Jacl:
$AdminTask listDynamicClusters
- Use Jython string:
AdminTask.listDynamicClusters()
Interactive mode example usage
- Use Jacl:
$AdminTask listDynamicClusters {-interactive}
- Use Jython string:
AdminTask.listDynamicClusters ('[-interactive]')
listDynamicClusterIsolationGroups
Display 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 usage
- Use Jacl:
$AdminTask listDynamicClusterIsolationGroups
- Use Jython string:
AdminTask.listDynamicClusterIsolationGroups()
Interactive mode example usage
- Use Jacl:
$AdminTask listDynamicClusterIsolationGroups {-interactive}
- Use Jython string:
AdminTask.listDynamicClusterIsolationGroups ('[-interactive]')
listDynamicClusterIsolationGroupMembers
Display 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 usage
- Use Jacl:
$AdminTask listDynamicClusterIsolationGroupMembers isolationGroupName
- Use Jython string:
AdminTask.listDynamicClusterIsolationGroupMembers('isolationGroupName')
Interactive mode example usage
- Use Jacl:
$AdminTask listDynamicClusterIsolationGroupMembers {-interactive}
- Use Jython string:
AdminTask.listDynamicClusterIsolationGroupMembers ('[-interactive]')
modifyDynamicClusterIsolationProperties
Modify 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 usage
- Use Jacl:
$AdminTask modifyDynamicClusterIsolationProperties dcName {-isolationGroup isolationGroupName -strictIsolationEnabled true}
- Use Jython string:
AdminTask.modifyDynamicClusterIsolationProperties('dcName', '[-isolationGroup isolationGroupName -strictIsolationEnabled true]')
Interactive mode example usage
- Use Jacl:
$AdminTask modifyDynamicClusterIsolationProperties {-interactive}
- Use Jython string:
AdminTask.modifyDynamicClusterIsolationProperties ('[-interactive]')
setDynamicClusterOperationalMode
Set the operational mode for the dynamic cluster.
Required parameters
- -operationalMode: 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 usage
- Use Jacl:
$AdminTask setDynamicClusterOperationalMode dcName {-operationalMode manual}
- Use Jython string:
AdminTask.setDynamicClusterOperationalMode('dcName', '[-operationalMode manual]')
Interactive mode example usage
- Use Jacl:
$AdminTask setDynamicClusterOperationalMode {-interactive}
- Use Jython string:
AdminTask.setDynamicClusterOperationalMode ('[-interactive]')
setDynamicClusterMembershipPolicy
Set 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 usage
- Use Jacl:
$AdminTask setDynamicClusterMembershipPolicy dcName {-membershipPolicy node_nodegroup='ngName'}
- Use Jython string:
AdminTask.setDynamicClusterMembershipPolicy('dcName', '[-membershipPolicy node_nodegroup=\'ngName\']')
Interactive mode example usage
- Use Jacl:
$AdminTask setDynamicClusterMembershipPolicy {-interactive}
- Use Jython string:
AdminTask.setDynamicClusterMembershipPolicy ('[-interactive]')
setDynamicClusterMinInstances
Set 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 usage
- Use Jacl:
$AdminTask setDynamicClusterMinInstances dcName {-minInstances 1}
- Use Jython string:
AdminTask.setDynamicClusterMinInstances('dcName', '[-minInstances 1]')
Interactive mode example usage
- Use Jacl:
$AdminTask setDynamicClusterMinInstances {-interactive}
- Use Jython string:
AdminTask.setDynamicClusterMinInstances ('[-interactive]')
setDynamicClusterMaxInstances
Set 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 usage
- Use Jacl:
$AdminTask setDynamicClusterMaxInstances dcName {-maxInstances -1}
- Use Jython string:
AdminTask.setDynamicClusterMaxInstances('dcName', '[-maxInstances 1]')
Interactive mode example usage
- Use Jacl:
$AdminTask setDynamicClusterMaxInstances {-interactive}
- Use Jython string:
AdminTask.setDynamicClusterMaxInstances ('[-interactive]')
setDynamicClusterVerticalInstances
Set 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 usage
- Use Jacl:
$AdminTask setDynamicClusterVerticalInstances dcName {-numVerticalInstances 2}
- Use Jython string:
AdminTask.setDynamicClusterVerticalInstances('dcName', '[-numVerticalInstances 2]')
Interactive mode example usage
- Use Jacl:
$AdminTask setDynamicClusterVerticalInstances {-interactive}
- Use Jython string:
AdminTask.setDynamicClusterVerticalInstances ('[-interactive]')
testDynamicClusterMembershipPolicy
Test 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 usage
- Use Jacl:
$AdminTask testDynamicClusterMembershipPolicy {-membershipPolicy node_nodegroup='ngName'}
- Use Jython string:
AdminTask.testDynamicClusterMembershipPolicy('[-membershipPolicy node_nodegroup=\'ngName\']')
Interactive mode example usage
- Use Jacl:
$AdminTask testDynamicClusterMembershipPolicy {-interactive}
- Use Jython string:
AdminTask.testDynamicClusterMembershipPolicy ('[-interactive]')
createNonWASDynamicCluster
Create 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: 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.
- -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 WAS Community Edition dynamic clusters: wasce20, cell/node/wasce_server
Return value.
The command returns the javax.management.ObjectName value of the dynamic cluster that we created.
Batch mode example usage
- Use 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}"}
- Use 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 we are running on WAS v7.0 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 example usage
- Use Jacl:
$AdminTask createNonWASDynamicCluster {-interactive}
- Use 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 usage
- Use Jacl:
set serverid [$AdminConfig getid /Cell:mycell/DynamicCluster:mydynamiccluster/Server:mydynamiccluster/]
- Use 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.
Commands for the AdminTask object Create dynamic clusters Configure vertical stacking Commands for the AdminConfig object Intelligent Management: dynamic cluster custom properties