IBM Business Process Manager, V8.0.1, All platforms > Reference > Commands and scripts > Commands (wsadmin scripting)

configRecoveryForCluster command

Use the configRecoveryForCluster command to specify a cluster, that you have configured to support Service Component Architecture, to manage failed events.

Purpose

This command provides a command line method to configure a cluster to manage failed events. You can use this command in a script when configuring multiple clusters.

>>-$AdminTask-- --configRecoveryForCluster - {------------------>

>-- —clusterName-- --clusterName-------------------------------->

>--+--------------------------------------+-- }----------------><
   '- —remoteMELocation--| remoteMESpec |-'       

remoteMESpec

|--+- --WebSphere:cluster=--clusterName-------------------+-----|
   '- --WebSphere:node=--nodeName--,--server=--serverName-'   

Parameters

-clusterName=clusterName

A required parameter that specifies the cluster you are configuring.

-remoteMELocation locationSpecification

Specifies the location of a remote messaging engine. locationSpecification can be either of

• WebSphere:cluster=clusterName

• WebSphere:node=nodeName,server=serverName

Examples

The following example uses configRecoveryForCluster to configure cluster AppCluster to manage failed events on a local messaging engine.

$AdminTask configRecoveryForCluster {-clusterName AppCluster}
$AdminConfig save

The following example uses configRecoveryForCluster to configure cluster AppCluster to manage failed events using the remote messaging engine MECluster.

$AdminTask configRecoveryForCluster {-clusterName AppCluster 
	-remoteMELocation WebSphere:cluster=MECluster}
$AdminConfig save

Parent topic: Commands (wsadmin scripting)

Related information:

Obtaining online help using wsadmin scripting
Administrative command invocation syntax using wsadmin scripting
Use the wsadmin scripting tool
Jython script library