Use this command to create a new service integration bus link in the cell.
The command described in this topic is run using the AdminTask object of the wsadmin scripting client.
These command line scripts are run from Qshell. For more information, see the topic "Configure Qshell to run WebSphere Application Server scripts".
wsadmin> $AdminTask help SIBAdminCommands
wsadmin> $AdminTask help command_name
For additional details of the command properties, see the related reference topic.
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.
To save the changes made by the command, invoke the "save" command on the AdminConfig object.
This property is set in the same way as the Provider endpoint property in the JMS connection factory settings.
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.
None.
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.
You must have predefined a J2C authentication alias.
Default | Started |
Range |
|
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>