getBPMTargetSignificance command

Use the getBPMTargetSignificance command to discover the target significance on all the resources for a given deployment target. The deployment target can be either a server or cluster.

For more information on how targetSignificance values affect processing, see the WebSphere Application Server Information Center.

Required parameters

clusterName name_of_cluster: The name of the cluster on which you are discovering target significance.

nodeName name_of_node: The name of the node on which you are discovering target significance.
If you specify this parameter, then you must also specify the serverName parameter. Do not specify this parameter if you have specified the clusterName parameter.
serverName serverName: The name of the server on which you are discovering target significance.
If you specify this parameter, then you must also specify the nodeName parameter. Do not specify this parameter if you have specified the clusterName parameter.

Optional parameters

printDetails true or false: The default value for this parameter is false. The value entered indicates whether or not to print details for getBPMTargetSignificance command.
If -printDetails = true, the command prints the current setting for targetSignificance used for all the activation specification and connection factories configured on the given cluster or server.

Examples

The following examples show how to use getBPMTargetSignificance

Note: In the examples, the -printDetails property is set to true. If you do not want to print the target significance settings for all the activation specification and connection factories configured on the given cluster or server, set -printDetails to false.

Jython example:
The example uses getBPMTargetSignificance to discover the target significance value for all the application resources deployed on a server (Server1):
```
AdminTask.getBPMTargetSignificance('[-serverName Server1 -nodeName Node2 
-printDetails true]')
```
Jacl example:
The example uses getBPMTargetSignificance to discover the target significance for all the application resources deployed on a cluster (Cluster1):
```
$AdminTask getBPMTargetSignificance { -clusterName Cluster1 -printDetails true}
```