createMissingSIBEnginePolicy command
Use the createMissingSIBEnginePolicy command to create a core group policy for a messaging engine in a cluster that is a member of a service integration bus.
To run the command, use the AdminTask object of the wsadmin scripting client.
(iSeries) (iSeries) The wsadmin scripting client is run from Qshell. (iSeries) See Configure Qshell to run WebSphere scripts .
This command is valid only when used with WebSphere Application Server v7.0 or later application servers. Do not use it with earlier versions.
Command-line help is provided for service integration bus commands:
- For a list of the available service integration bus commands in Jython and a brief description of each command, enter at the wsadmin prompt:
print AdminTask.help('SIBAdminCommands')
- For overview help on a given command, enter at the wsadmin prompt:
print AdminTask.help('command_name')
After using the command, save the changes to the master configuration using the following command:
AdminConfig.save()
Use this command to create a core group policy for a messaging engine. For example, we must do this after we create a new messaging engine for the cluster using the createSIBEngine command. Use this command only when the cluster has messaging engine policy assistance enabled and the custom policy specified. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
Target object
A messaging engine.
Required parameters
- -name messaging_engine_name
- The name of the messaging engine for which to create a core group policy.
Optional parameters
- -failover TRUE | FALSE
- A parameter that specifies whether the messaging engine in the cluster can fail over to another server in the cluster if the host server for the messaging engine fails. This parameter has two possible values:
- TRUE
- The messaging engine can fail over.
- FALSE
- The messaging engine cannot fail over.
The default is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy specified. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
- -failback TRUE | FALSE
- A parameter that specifies whether the messaging engine in the cluster that has failed over can fail back to a more preferred server in the preferred servers list if that server becomes available again. This parameter has two possible values:
- TRUE
- The messaging engine can fail back. If we use this option, supply a -preferredServerList parameter.
- FALSE
- The messaging engine cannot fail back.
The default is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy set. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
- -preferredServersOnly TRUE | FALSE
- A parameter that specifies whether the messaging engine in the cluster can run only on servers in the preferred servers list, or on any server in the cluster. This parameter has two possible values:
- TRUE
- The messaging engine can run only on servers in the preferred servers list. If we use this option, supply a -preferredServerList parameter.
- FALSE
- The messaging engine can run on any server in the cluster.
The default is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy set. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
- -preferredServerList {{node server}}
- The list of servers, in order of preference, on which the messaging engine in the cluster prefers to run. For each server in the list, specify both the name of the node on which the server runs, and the name of the server. There is no default value for this parameter. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy set. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
Example
Create a core group policy for the messaging engine cluster1.000-bus1. Configure the core group policy so that the messaging engine can fail over, cannot fail back, and can run only on server1 and server2:
AdminTask.createMissingSIBEnginePolicy('[-name cluster1.000-bus1 -failover true -failback false -preferredServersOnly true -preferredServerList [[node1 server1] [node2 server2]]]')