Use the createSIBEngine command to create a messaging engine for a server or cluster bus member by using the wsadmin tool. When you add a server or a cluster as a member of a service integration bus, at least one messaging engine is created automatically. Use the createSIBEngine command to create an additional messaging engine for a cluster bus member.
Each server bus member has exactly one messaging engine, but cluster bus members can support additional engines. If you create an additional messaging engine for a cluster, and you use a data store for the message store, you must explicitly configure both the data store and the JDBC data source that the messaging engine uses to interact with the data store. You must create the data source at cluster scope, not node scope. For more information about creating messaging engines, see Configuring a data source for a messaging engine running in a 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 createSIBEngine command creates a new messaging engine for a server or cluster bus member. Use this command to create an additional messaging engine for a cluster bus member.
If the cluster has messaging engine policy assistance enabled and the scalability or scalability with high availability policy specified, the messaging engine settings are created automatically to conform with the specified policy.
After you use this command, if the cluster has messaging engine policy assistance enabled and the custom policy specified, you can create a core group policy for a messaging engine by using the createMissingSIBEnginePolicy command.
None.
When the messaging engine is created, the high message threshold of the bus is used to set the default value for this property. When a message point is created on this messaging engine, the value of this property is used to set the default high message threshold for the message point.
The default value is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy specified. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
The default value is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy set. To do this, you use the addSIBusMember or modifySIBusMemberPolicy commands.
The default value is FALSE. Use this parameter if the cluster has messaging engine policy assistance enabled and the custom policy set. To do this, use the addSIBusMember or modifySIBusMemberPolicy commands.
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.
Use this parameter if the -dataStore parameter is specified.
Depending on the choice of the message store and its attributes, you specify different combinations of the parameters. To avoid errors when you specify the message store for the messaging engine, see Avoiding errors when creating a messaging engine with a file store or a data store by using the wsadmin tool.
Create a messaging engine for cluster1 on bus1 that uses a default file store.
AdminTask.createSIBEngine ('[-bus bus1 -cluster cluster1]')
Create a messaging engine for cluster1 on bus1 that uses a file store with defaults.
AdminTask.createSIBEngine ('[-bus bus1 -cluster cluster1 -fileStore]')
Create a messaging engine for cluster1 on bus1 that uses a file store with options.
AdminTask.createSIBEngine ('[-bus bus1 -cluster cluster1 -fileStore -logSize 3636363 -logDirectory C:\mylogdirectory]')
Create a messaging engine for cluster1 on bus1 that uses a data store with defaults.
AdminTask.createSIBEngine ('[-bus bus1 -cluster cluster1 -dataStore]')
Create a messaging engine for cluster1 on bus1 that uses a data store with options.
AdminTask.createSIBEngine ('[-bus bus1 -cluster cluster1 -dataStore -createDefaultDatasource true -datasourceJndiName myjndi]')
Add a new messaging engine to cluster1 that is a member of bus1 and that uses a file store as the message store for the messaging engine.
AdminTask.createSIBEngine('[-bus bus1 -cluster cluster1 -fileStore true -logSize 100 -minPermanentStoreSize 200 -maxPermanentStoreSize 500 -unlimitedPermanentStoreSize false -permanentStoreDirectory C:\myfilestore -minTemporaryStoreSize 200 -maxTemporaryStoreSize 500 -unlimitedTemporaryStoreSize false -temporaryStoreDirectory C:\myfilestore -logDirectory C:\myfilestore ]')
Add a new messaging engine to cluster1 that is a member of bus1, where cluster1 has messaging engine policy assistance enabled and the custom messaging engine policy specified. 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.createSIBEngine('[-bus bus1 -cluster cluster1 -fileStore true -logSize 100 -minPermanentStoreSize 200 -maxPermanentStoreSize 500 -unlimitedPermanentStoreSize false -permanentStoreDirectory C:\myfilestore -minTemporaryStoreSize 200 -maxTemporaryStoreSize 500 -unlimitedTemporaryStoreSize false -temporaryStoreDirectory C:\myfilestore -logDirectory C:\myfilestore -failover true -failback false -preferredServersOnly true -preferredServerList [[node1 server1] [node2 server2]]]')