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, a WebSphere® MQ server, or a server cluster.
To run the command, use the AdminTask object of the wsadmin scripting client.
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 cluster is added as a member of a bus, if messaging engine policy assistance is not enabled, a messaging engine with default settings is created automatically. To create an additional messaging engine for a bus member, use the createSIBEngine command.
When a cluster is added to a bus, if messaging engine policy assistance is enabled and the high availability messaging engine policy type is specified, a messaging engine with settings that support the high availability policy is created automatically.
When a cluster is added to a bus, if messaging engine policy assistance is enabled and the scalability, or scalability with high availability, messaging engine policy type is specified, one messaging engine with settings that support the selected policy is created automatically. You must then use the createSIBEngine command to create additional messaging engines (one for each application server in the cluster). For each new messaging engine, the settings that support the selected policy are created automatically.
If you use the addSIBusMember command with messaging engine policy assistance enabled and the custom messaging engine policy type specified, you can set the behavior for the first messaging engine, then use the createSIBEngine command to create additional messaging engines.
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 or a server cluster, a messaging engine is also created.
If you specify these parameters, do not specify the -cluster or -wmqServer parameters.
If you specify this parameter, do not specify the -node, -server, or -wmqServer parameters.
If you specify this parameter, do not specify the -cluster, -node, or -server parameters.
The default value is TRUE. Use this parameter if the -wmqServer parameter is specified.
This parameter has no default. Use this parameter if the -cluster parameter is specified and the -enableAssistance parameter is set to TRUE.
The default value is FALSE. Use this parameter if the -cluster parameter is specified, the -enableAssistance parameter is set to TRUE, and the -policyName parameter is set to CUSTOM.
The default value is FALSE. Use this parameter if the -cluster parameter is specified, the -enableAssistance parameter is set to TRUE, and the -policyName parameter is set to CUSTOM.
The default value is FALSE. Use this parameter if the -cluster parameter is specified, the -enableAssistance parameter is set to TRUE, and the -policyName parameter is set to CUSTOM.
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]')
Add cluster1 to bus1 without using messaging engine policy assistance and use a file store as the message store for the messaging engine.
AdminTask.addSIBusMember('[-bus bus1 -cluster cluster1 -filestore true -logDirectory C:\filestore1 -permanentStoreDirectory C:\filestore2 -temporaryStoreDirectory C:\filestore3]')
Add cluster1 to bus1 and use messaging engine policy assistance and the high availability messaging engine policy. Use a file store as the message store for the messaging engine.
AdminTask.addSIBusMember('[-bus bus1 -cluster cluster1 -enableAssistance true -policyName HA -fileStore -permanentStoreDirectory C:\myfilestore1 -temporaryStoreDirectory C:\myfilestore1 -logDirectory C:\myfilestore ]')
Add cluster1 to bus1 and use messaging engine policy assistance and the custom messaging engine policy. Use a file store as the message store for the messaging engine. Set the messaging engine to fail over, not to fail back, and to run only on server1 and server2.
AdminTask.addSIBusMember('[-bus bus1 -cluster cluster1 -enableAssistance true -policyName CUSTOM -fileStore -permanentStoreDirectory C:\myfilestore1 -temporaryStoreDirectory C:\myfilestore1 -logDirectory C:\temp\myfilestore -failover true -failback false -preferredServersOnly true -preferredServerList [[node1 server1] [node2 server2]]]')
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]')