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.
To run the command, use the AdminTask object of the wsadmin scripting client.
The wsadmin scripting client is run from Qshell. For more information, see Configuring Qshell to run WebSphere Application Server scripts using wsadmin scripting .
print AdminTask.help('SIBAdminCommands')
print AdminTask.help('command_name')
AdminConfig.save()
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.
None.
A bus member object is created. If the bus member is a server, a messaging engine is also created.
If you specify these parameters, do not specify the -wmqServer parameter.
If you specify this parameter, do not specify the -node or -server parameters.
The default value is TRUE. Use this parameter if the -wmqServer parameter is specified.
Use this parameter if the -fileStore parameter is specified.
Use this parameter if the -fileStore parameter is specified.
A data store consists of the set of tables that a messaging engine uses to store persistent data in a database. See Data store tables for a list of the tables that comprise a data store. All the tables in a data store are held in the same database schema. You can create multiple data stores in the same database, provided that you use a different schema name for each data store.
The alternative is to use file store (the default). For more information, see the related links.Use this parameter if the -dataStore parameter is specified. Do not use this parameter if the -cluster parameter is specified.
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]')
Change the initial JVM heap size to 256 and the maximum JVM heap size to 512.
AdminTask.addSIBusMember('[-bus bus1 -node node1 -server server1 -initialHeapSize 256 -maxHeapSize 512]')