Creating a service integration bus link using the wsadmin tool

Use this command to create a new service integration bus link in the cell.

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

[iSeries] The wsadmin scripting client is run from Qshell. For more information, see the topic "Configure Qshell to run WebSphere® Application Server scripts".

This command is only valid when used with WebSphere Application Server Version 6.1 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 link for a specified service integration bus. A service integration bus link defines a link between a messaging engine in one service integration bus and a messaging engine in a foreign service integration bus.

Command name
createSIBLink
Target
None.
Result
A service integration bus link object.

To save the changes made by the command, invoke the "save" command on the AdminConfig object.

Required parameters

-bus busname
The name of the service integration bus for which you want to create the service integration bus link. You can use the listSIBuses command to list the names of existing buses.
-messagingEngine name
The name of the messaging engine for which you want to create the service integration bus link. The service integration bus link connects a messaging engine to another messaging engine in a different service integration bus, thereby providing a bridge between two service integration buses.
-name MQlinkname
The name by which you want the service integration bus link to be known.
-foreignBusName busname
The name of the foreign bus that defines the remote service integration bus for the service integration bus link. You can use the listSIBForeignBuses command to list the names of existing foreign buses.
-bootstrapEndpoints endpoints
The comma-separated list of endpoints used to connect to a bootstrap server.

This property is set in the same way as the Provider endpoint property in the JMS connection factory settings. For more information, see the steps relating to setting bootstrap endpoints in Configuring a connection to a non-default bootstrap server. This task primarily describes how to configure a JMS connection factory, but also applies to setting several bootstrap endpoint values if the remote messaging engine is in a cluster.

The port for the bootstrap endpoint is the port defined on the SIB endpoint address that is configured on the target application server on the foreign bus.

-remoteMessagingEngineName name
The messaging engine on the foreign bus to which this link connects.

Conditional parameters

None.

Optional parameters

-description text
An optional description for the bus, for administrative purposes.
-protocolName protocolname
The type of transport chain used for communication with the foreign bus.

The transport chain name must be the name of the transport chain as defined on the server on which the target messaging engine is hosted.

-authAlias aliasname
The name of the authentication alias, used to authenticate access to the foreign bus.

You must have predefined a J2C authentication alias.

-initialState Started | Stopped
Whether the link is started automatically when the messaging engine is started.
Default Started
Range
Stopped
When the associated messaging engine is started, the gateway link is in a stopped state and cannot process any new requests for connections.
Started
When the associated messaging engine is started, the gateway link is in a started state and can process any new requests for connections.

Example

wsadmin>$AdminTask createSIBLink {-bus SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -messagingEngine IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus
 -name mySIBLink2 -foreignBusName SCA.SYSTEM.IBM-AA8DA602255Cell02.Bus
 -bootstrapEndpoints localhost:7276:BootstrapBasicMessaging
 -remoteMessagingEngineName IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell02.Bus}
mySIBLink2(cells/IBM-AA8DA602255Cell01/nodes/IBM-AA8DA602255Node01/servers/server1|sib-engines.xml#SIBGatewayLink_1132612346967)
wsadmin>



Related reference
Service integration bus link administrative commands
Reference topic    

Terms of Use | Feedback

Last updated: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=rjj_siblink_create
File name: rjj_siblink_create.html