Creating a service integration bus using the wsadmin tool

Use the wsadmin tool to create a new service integration bus in the cell.

To run the command, use the AdminTask object of the wsadmin scripting client.

This command is only valid when used with WebSphere® Application Server Version 6 and later application servers. Do not use it with earlier versions.

Command-line help is provided for service integration bus commands:

For additional details of the command properties, see the related reference topic.

Purpose

This command creates a new service integration bus in the cell.

Command name
createSIBus
Target
None.
Result
A bus object.

To save the changes made by the command, type $AdminConfig save.

Required parameters

-bus busname
The name by which you want the service integration bus to be known. Choose a unique name.

Conditional parameters

None.

Optional parameters

-description text
An optional description for the bus, for administrative purposes.
-secure TRUE | FALSE
Set this option to TRUE to inherit the global security setting of the cell. Set this option to FALSE if you always want to disable bus security.
Set this option to TRUE to enforce the authorization policy for the bus, which also requires administrative security to be enabled. Set this option to FALSE if you always want to disable bus security. If administrative security is disabled the bus is insecure.
interEngineAuthAlias name
The name of the authentication alias used to authorize communication between messaging engines on the bus.

For a secured bus with multiple bus members, consider setting an inter-engine authentication alias for the bus. When bus security is enabled, the bus uses the inter-engine authentication alias to authenticate incoming connections from other messaging engines. An unauthorized messaging engine cannot connect to the bus.

-mediationsAuthAlias name
The name of the authentication alias used to authorize mediations to access the bus.
-protocol protocol
The transport chain used for communication between messaging engines in this bus.

The transport chain must correspond to one of the transport chains defined in the Messaging engine inbound transports settings for the server. All servers automatically have a number of transport chains defined to them, and it is also possible to create new transport chains.

The default transport chain is InboundBasicMessaging.

-discardOnDelete TRUE | FALSE
Set this option to TRUE if messages on a deleted message point can be discarded. Set this option to FALSE if messages on a deleted message point should be retained at a system exception destination.
highMessageThreshold number
The maximum total number of messages that any messaging engine on the bus can place on its message points.

This value is used to set the default high message threshold for a messaging engine when the messaging engine is created on the bus.

configurationReloadEnabled TRUE | FALSE
Set this option to TRUE to dynamically reload configuration files for this bus.

When this option is TRUE, certain changes to the bus configuration are applied without requiring the messaging engines to be restarted. These changes are applied when destinations or mediations are added to, or removed from, the bus. This option also controls whether automatic updates occur on all the messaging engines on the bus.

Example

wsadmin>$AdminTask createSIBus {-bus anewbus -description "A new bus called anewbus"}
anewbus(cells/9994GKCCell/buses/anewbus|sib-bus.xml#SIBus_1097531651175)
wsadmin>



Related concepts
Access control for multiple buses
Related tasks
Adding a foreign bus
Related reference
Buses administrative commands
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=rjj_cli_bus_create
File name: rjj_cli_bus_create.html