Use the configRecoveryForServer command to specify a server, that you have configured to support Service Component Architecture, to manage failed events.
Purpose
This command provides a command line method to configure a server to manage failed events. You can use this command in a script when configuring multiple servers.
>>-$AdminTask-- --configRecoveryForServer - {-------------------> >-- —serverName-- --serverName-- -- —nodeName-- --nodeName------> >--+--------------------------------------+-- }---------------->< '- —remoteMELocation--| remoteMESpec |-' remoteMESpec |--+- --WebSphere:cluster=--clusterName-------------------+-----| '- --WebSphere:node=--nodeName--,--server=--serverName-'
Parameters
- -serverName serverName
- A required parameter that specifies the server you are configuring.
- -nodeName nodeName
- A required parameter that specifies the node to which the server belongs.
- -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 configRecoveryForServer to
configure server AppServer on node AppNode to manage failed events
on a local messaging engine.
$AdminTask configRecoveryForServer {-serverName AppServer -nodeName AppNode}
$AdminConfig saveThe following example uses configRecoveryForServer to
configure server AppServer on node AppNode to manage failed events
using the remote messaging engine MEServer on node MENode.
$AdminTask configRecoveryForServer {-serverName AppServer -nodeName AppNode
-remoteMELocation WebSphere:node=MENode,server=MEServer}
$AdminConfig save
