modifySIBForeignBus command
Use the modifySIBForeignBus command to modify the properties of a foreign bus.
Para executar o comando, utilize o objeto AdminTask do cliente de script wsadmin.
O cliente de script wsadmin é executado do Qshell.
Para obter informações adicionais, consulte Configurando o Qshell para Executar Scripts do WebSphere Usando o Script wsadmin.
A ajuda da linha de comandos é fornecida para comandos do barramento de integração de serviços:
- Para obter uma lista dos comandos de barramento de integração de
serviços disponíveis no Jython e uma breve descrição de cada comando, digite o seguinte
comando no prompt wsadmin:
print AdminTask.help('SIBAdminCommands')
- Para obter ajuda de visão geral sobre um determinado comando, digite o seguinte comando no prompt wsadmin:
print AdminTask.help('command_name')
Após utilizar o comando, salve suas alterações na configuração principal, utilizando o seguinte comando:
AdminConfig.save()
Purpose
This command modifies the properties of a foreign bus. A foreign bus represents a bus in another cell (or within the same cell) or a IBM MQ network, with which a service integration bus can exchange messages.
Target object
A foreign bus.
Required parameters
- -bus busname
- The name of the service integration bus for which you want to modify a foreign bus. You can use the listSIBuses command to list the names of existing buses.
- -name busname
- The name of the foreign bus that you want to modify. You can use the listSIBForeignBuses command to list the names of existing buses.
Conditional parameters
None.
Optional parameters
- -description text
- An optional description for the bus, for administrative purposes.
- -sendAllowed False | False
- (Default: True) Whether 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 might want 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.
- -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 IBM MQ system rather than a service integration bus.
- -topicSpaceMappings local topicSpace_name : remote topicSpace_name
- A topic space mapping allows subscribers on the local topic space to receive messages published in the foreign topic space. For publications to flow from the local topic space into the foreign bus, an equivalent topic space mapping is required by the foreign bus. Topic space names for the local bus are mapped to topic space names defined on the foreign bus. It is common for these two names to match. Note that mapping two topic spaces implies that the topics within them are the same. You can specify multiple pairs of topic spaces.
Example
The following example specifies additional optional properties for an existing foreign bus called foreignbus1:- An inbound user identity called iuserid to authorize messages sent from foreignbus1 to the local bus, when security is enabled on foreignbus1, and the local bus.
- An outbound user identity called ouserid to authorize messages sent from the local bus to foreignbus1, when security is enabled on foreignbus1, and the local bus.
- A topic space mapping between Topic.Space1 on the local bus and Topic.Space2 on foreignbus1. The mapping allows subscribers on Topic.Space1 on the local bus to receive messages published in Topic.Space2 on foreignbus1.
AdminTask.modifySIBForeignBus('[-bus bus1 -name foreignbus1 -inboundUserid iuserid
-outboundUserid ouserid -topicSpaceMappings [[Topic.Space1 Topic.Space2]]]')
'foreignbus1(cells/cell01/buses/bus1|sib-bus.xml#SIBForeignBus_1213023645293)'