addSIBusMember command
Use the addSIBusMember command to add a member to a service integration bus by using the wsadmin tool. A bus member can be an application server or a WebSphere® MQ server.
Para executar o comando, utilize o objeto AdminTask do cliente de script wsadmin.
![[IBM i]](../images/iseries.gif)
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.
- 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')
AdminConfig.save()
Purpose
The addSIBusMember command adds a new member to a service integration bus. When an application server is added as a member of a bus, a messaging engine with default settings is created automatically.
When a WebSphere MQ server is added as a member of a bus, a server proxy is created that can override the parent connection properties (host, port, channel, and SSL security configuration alias) that are defined in the WebSphere MQ server. By this means, a different set of connection properties can be assigned to each bus membership.
Target object
None.
A bus member object is created. If the bus member is a server, a messaging engine is also created.
Required parameters
- -bus bus_name
- The name by which the service integration bus is known. You can use the listSIBuses command to list the names of existing buses.
Conditional parameters
- -node node_name
- -server server_name
- To add an application server as a bus member, specify both the
name of the node on which the server runs, and the name of the server.
If you specify these parameters, do not specify the -wmqServer parameter.
- -wmqServer
- To add a WebSphere MQ server as a bus member, specify
the name of the WebSphere MQ server. This is the name that
was specified in the -name parameter when the WebSphere MQ server was created.
If you specify this parameter, do not specify the -node or -server parameters.
Optional parameters
- -description text
- An optional description for the bus member, for administrative purposes.
- -virtualQueueManagerName
- The override value for the name of the WebSphere MQ
server virtual queue manager. Ao enviar mensagens para o IBM MQ, o gerenciador de filas de gateway do IBM MQ vê o barramento como um gerenciador de filas remotas. O nome do gerenciador de filas virtual é o nome que é transmitido para o IBM MQ como o nome desse gerenciador de filas remotas. O valor padrão é o nome do barramento. Se esse valor não for um nome válido para um gerenciador de filas do IBM MQ ou se já existir outro gerenciador de filas do IBM MQ com o mesmo nome, substitua o valor padrão por outro valor que seja válido e o nome exclusivo para um gerenciador de filas do IBM MQ. Para ser válido, o nome deve atender aos seguintes critérios:
- Deve conter entre 1 e 48 caracteres.
- Deve estar em conformidade com as regras de nomenclatura de fila do IBM MQ (consulte o tópico Regras para objetos de nomenclatura do IBM MQ no centro de informações do IBM MQ).
- -host
- The override value for the WebSphere MQ server bus member host attribute. This value is the host name or IP address of the host to which a connection is established to communicate with a queue manager or queue-sharing group. Use this parameter if the -wmqServer parameter is specified.
- -port
- The override value for the WebSphere MQ server bus member port attribute. The port number is monitored by a queue manager listener or queue-sharing group listener, which is listening for connections. The default value is 1414. Use this parameter if the -wmqServer parameter is specified.
- -channel
- The override value for the WebSphere MQ server bus member channel attribute. This is the name of the server connection channel that is used to establish a connection to the IBM MQ queue manager or IBM MQ for z/OS® queue sharing group. The default value is SYSTEM.DEF.SVRCONN. Use this parameter if the -wmqServer parameter is specified.
- -securityAuthAlias
- The override value for the WebSphere MQ server bus member securityAuthAlias attribute. This is the authentication alias that is supplied when connecting to the WebSphere MQ server. This parameter has no default. Use this parameter if the -wmqServer parameter is specified.
- -transportChain
- The override value for the WebSphere MQ server bus member transportChain attribute. This is the name of the transport chain to use when communicating with IBM MQ. The default value is OutboundBasicWMQClient. Use this parameter if the -wmqServer parameter is specified.
- -trustUserIds TRUE | FALSE
- The override value for the WebSphere MQ
server bus member trustUserIds attribute. This
determines whether user IDs that are received in messages from IBM MQ are propagated into messages.
The application user ID is always set from the jsAppUserIdRFH2 value.
If this is not present (either because the key/value pair is not present
in the <sib> folder of the RFH2 header, or
because the message does not have a RFH2 header), this field is not
set. This parameter has two possible values:
- TRUE
- User IDs are propagated into messages.
- FALSE
- User IDs are not propagated into messages.
The default value is TRUE. Use this parameter if the -wmqServer parameter is specified.
- -fileStore
- Create a file store to use as a message store for the messaging engine. Um armazém de arquivos é um tipo de armazenamento de mensagem que usa diretamente os arquivos em um sistema de arquivos por meio do sistema operacional. The alternative is to use a data store. For more information, see the related links.
- -logSize logsize
- The size of the log file in MB. Use this parameter if the -fileStore parameter is specified.
- -logDirectory logdirectoryname
- The name of the log file directory if you do not want to use the default log directory. Use this parameter if the -fileStore parameter is specified.
- -minPermanentStoreSize minpermanentstoresize
- The minimum size of the permanent store file in MB. Use this parameter if the -fileStore parameter is specified.
- -minTemporaryStoreSize mintemporarystoresize
- The minimum size of the temporary store file in MB. Use this parameter if the -fileStore parameter is specified.
- -maxPermanentStoreSize maxpermanentstoresize
- The maximum size of the permanent store file in MB. Use this parameter if the -fileStore parameter is specified.
- -maxTemporaryStoreSize maxtemporarystoresize
- The maximum size of the temporary store file in MB. Use this parameter if the -fileStore parameter is specified.
- -unlimitedPermanentStoreSize TRUE | FALSE
- A parameter that specifies whether the permanent store size is
unlimited. This parameter has two possible values:
- TRUE
- The permanent store size is unlimited.
- FALSE
- The permanent store size is limited. If you use this option, supply a -maxPermanentStoreSize parameter.
Use this parameter if the -fileStore parameter is specified.
- -unlimitedTemporaryStoreSize TRUE | FALSE
- A parameter that specifies whether the temporary store size is
unlimited. This parameter has two possible values:
- TRUE
- The temporary store size is unlimited.
- FALSE
- The temporary store size is limited. If you use this option, supply a -maxTemporaryStoreSize parameter.
Use this parameter if the -fileStore parameter is specified.
- -permanentStoreDirectory permanentstoredirectoryname
- The name of the permanent store directory if you do not want to use the default permanent store directory. Use this parameter if the -fileStore parameter is specified.
- -temporaryStoreDirectory temporarystoredirectoryname
- The name of the temporary store directory if you do not want to use the default temporary store directory. Use this parameter if the -fileStore parameter is specified.
- -dataStore
- Create a data store to use as a message store for the messaging
engine.
Um armazém de dados consiste no conjunto de tabelas que um mecanismo do sistema de mensagens utiliza para armazenar dados persistentes em um banco de dados. Consulte Tabelas de Armazenamento de Dados para obter uma lista de tabelas que abrangem um armazém de dados. Todas as tabelas em um armazém de dados são mantidas no mesmo esquema do banco de dados. É possível criar múltiplos armazéns de dados no mesmo banco de dados, contanto que use um nome de esquema diferente para cada armazém de dados.
The alternative is to use file store (the default). For more information, see the related links. - -createDefaultDatasource TRUE | FALSE
- A parameter that specifies whether to create a default data source
when the messaging engine is created. This parameter has two possible
values:
- TRUE
- Create a default data source.
- FALSE
- Do not create a default data source.
Use this parameter if the -dataStore parameter is specified. Do not use this parameter if the -cluster parameter is specified.
- -datasourceJndiName jndiname
- The JNDI name of the data source that the messaging engine uses to access the relational database management system (RDBMS) for the data store. Use this parameter if the -dataStore parameter is specified.
- -authAlias authalias
- The name of the authentication alias that the messaging engine uses to connect to the database in its data store. Use this parameter if the -dataStore parameter is specified.
- -createTables datasource
- Create the database tables for the specified data source automatically. If this option is not specified, the database administrator must create the tables. Use this parameter if the -dataStore parameter is specified.
- -restrictLongDBLock TRUE | FALSE
- A parameter that specifies whether the active messaging engine
must retain long running locks on the SIBOWNER table in the database.
When this option is selected, the messaging engine establishes a lock
over the database only for short durations. In the event of the active
messaging engine not responding to the database, the standby messaging
engine will be able to take ownership of the database because the
active messaging engine only holds short duration locks. This parameter
has two possible values:
- TRUE
- Restrict long running locks on the database.
- FALSE
- Do not restrict long running locks on the database.
Use this parameter if the -dataStore parameter is specified.
Important: Although the property is selected, the property will not be effective until the database tables are upgraded using the sibDBUpgrade command for WebSphere Application Server Versão 9.0 and later. - -schemaName schemaname
- The name of the database schema that contains the tables for the data store, if you do not want to use the default schema name. For details about the default schema, see Criando Usuários e Esquemas no Banco de Dados. Use this parameter if the -dataStore parameter is specified.
- -initialHeapSize size
- The initial Java™ virtual machine (JVM) heap size, in megabytes, of the server or of each server in a cluster. There is no default value. If this parameter is not specified, no change is made. If this parameter is specified, the supplied value must be greater than or equal to zero and less than or equal to 2048. If the parameter is supplied without a value, an error message is generated.
- -maxHeapSize size
- The maximum JVM heap size, in megabytes, of the server or of each server in a cluster. There is no default value. If this parameter is not specified, no change is made. If this parameter is specified, the supplied value must be greater than or equal to zero and less than or equal to 2048. If the parameter is supplied without a value, an error message is generated.
Examples
Add a server1 on node1 as a member of bus1 with a default file store.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 ]')
Add server1 as a member of bus1, and use a file store to save messages.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 -fileStore ]')
Add server1 as a member of bus1, and use a file store to save messages, with options.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 -fileStore
-logSize 100 -logDirectory C:\\filestore1 ]')
Add server1 as a member of bus1, and use a data store to save messages.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 -dataStore ]')
Add server1 as a member of bus1, and use a data store to save messages, with options.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 -dataStore
-createDefaultDatasource true -datasourceJndiName myjndi]')
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Change the initial JVM heap size to 256 and
the maximum JVM heap size to 512.
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1
-initialHeapSize 256 -maxHeapSize 512]')
Tópico de Referência