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

Creating a foreign bus through the command line

Use this command to create a new foreign bus in the cell.

Before you begin

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 creates a new foreign bus for a specified service integration bus. A foreign bus represents a bus in another cell (or within the same cell) or a WebSphere MQ network, with which a service integration bus can exchange messages.

Command name
createSIBForeignBus
Target
None.
Result
A foreign bus 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 foreign bus. You can use the listSIBuses command to list the names of existing buses.
-name busname
The name by which you want the foreign bus to be known.
Notes:
  • When you create a foreign bus that represents another service integration bus, the name of the foreign bus must match the name of the other service integration bus.
  • When you intend to link two buses directly, you must assign them unique names.
  • You must not change the name of a foreign bus name after it has been configured.
-routingType Direct | Indirect
Create a foreign bus with the physical link (also known as the routing type) specified:
Direct
A service integration bus link from a messaging engine in the local bus to a messaging engine in the foreign bus.
Indirect
An indirect link, that is, a link that is made through one or more intermediate foreign buses.

Conditional Parameters

None.

Optional Parameters

-description text
An optional description for the bus, for administrative purposes.
-type MQ | SIBus
Create a foreign bus with the type specified:
MQ
Create a foreign bus to link the service integration bus to a WebSphere MQ network.
SIBus
Create a foreign bus to link the service integration bus to another service integration bus.
-sendAllowed True | False
(Default: True) Whether or not producers can send messages to the foreign bus.
False
Producers cannot send messages to the foreign bus.
True
Producers can send messages to the foreign bus.
-inboundUserid userID
The inbound user ID is used to authorize individual messages arriving from the foreign bus to destinations in the service integration bus. If this is not a secure bus, this property has no affect on messages. You may wish to specify an inbound user ID:
  • if the foreign bus is in a different security domain from this bus and user IDs from the foreign bus are not recognized in this bus
  • to locally-control access of inbound messages to this bus.
If this is a secure bus and the foreign bus is not secure, and no inbound user ID is set, any inbound messages from the foreign bus are only authorized to destinations that allow unauthenticated users access.
-outboundUserid userID
The outbound user ID replaces the user ID that identifies the source of a message in all messages being sent to the foreign bus. This user ID is also used by the foreign bus to authorize the message to its destination if both buses are secure buses and the foreign bus has not overridden the user ID with its own inbound user ID.
-nextHopBus bus_name
(If -routingType is Indirect) The name of the next service integration bus in the sequence of connected buses. An intermediate bus can be a WebSphere MQ system rather than a service integration bus.

Example

wsadmin>$AdminTask createSIBForeignBus {-bus SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus -name SCA.SYSTEM.IBM-AA8DA602255Cell02.Bus -routingType Direct -type SIBus}
SCA.SYSTEM.IBM-AA8DA602255Cell02.Bus(cells/IBM-AA8DA602255Cell01/buses/SCA.SYSTEM.IBM-AA8DA602255Cell01.Bus|sib-bus.xml#SIBForeignBus_1132530748562)
wsadmin>
Related reference
Foreign 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_fbus_create.html

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