WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Modifying a service integration bus link through the command line

Use this command to change properties of a service integration bus link.

Before you begin

This command provides only a subset of the properties available. If you want to modify other properties, you need to use the administrative console or wsadmin and JACL

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".

Required cleanup: Change to paragraph and flag for WAS6.1-onward (disable for WESB) This command is only valid when run against WebSphere Application Server Version 6.1 application servers. Do not run it against earlier versions.
Command-line help is provided with each of the service integration technologies commands:
  • For a list of all the available service integration technologies commands, plus a brief description of each command, type the following command:
    wsadmin> $AdminTask help SIBAdminCommands
  • For detailed help on a given command, enter the following command:
    wsadmin> $AdminTask help command_name

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

Purpose

This command modifies the properties of a service integration bus link.

Command name
modifySIBLink
Target
None.
Result
A service integration bus link object (modified).

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 modify 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 modify the service integration bus link. The service integration bus link connects a messaging engine as a queue manager to service integration bus, thereby providing a bridge between a service integration bus and a service integration bus network.
-name linkname
The name by which you want the service integration bus link is known.
-foreignBusName busname
The name of the foreign bus that defines the service integration bus network for the service integration bus link. You can use the listSIBForeignBuses command to list the names of existing foreign buses.

Conditional Parameters

None.

Optional Parameters

-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.

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.
-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 showSIBLink {-bus SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -messagingEngine IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -sibLink mySIBLink2}
SIB Link details:
Name = mySIBLink2, Uuid = 774D6C07A8D78AB4, Target Uuid = 303CB5DE74B25FBCE48A6CD2,
 Description = null, Remote Messaging Engine Name = IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell02.Bus,
 Protocol Name = null, Bootstrap Endpoints = localhost:7260:BootstrapBasicMessaging, Authentication Alias = null,
 Initial State = STARTED
wsadmin>$AdminTask modifySIBLink {-bus SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus
 -messagingEngine IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus
 -name mySIBLink2 -bootstrapEndpoints anotherhost:7890:BootstrapBasicMessaging}
mySIBLink2(cells/IBM-AA8DA602255Cell01/nodes/IBM-AA8DA602255Node01/servers/server1|sib-engines.xml#SIBGatewayLink_1132613287970)
wsadmin>$AdminTask showSIBLink {-bus SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -messagingEngine IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -sibLink mySIBLink2}
SIB Link details:
Name = mySIBLink2, Uuid = 774D6C07A8D78AB4, Target Uuid = 303CB5DE74B25FBCE48A6CD2, Description = null, Remote Messaging Engine Name = IBM-AA8DA602255Node01.server1-SCA.SYSTEM.IBM-AA8DA602255Cell02.Bu
s, Protocol Name = null, Bootstrap Endpoints = anotherhost:7890:BootstrapBasicMessaging, Authentication Alias = null, Initial State = STARTED
wsadmin>
Related reference
Service integration bus settings

Reference topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\ref\rjj_siblink_modify.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)