When you create a service integration bus and add a server or a cluster member to that bus, a messaging engine with default settings 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. Cluster bus members can support additional engines. If you create an additional messaging engine for a cluster, 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.
The wsadmin scripting client is run from
Qshell. For more information, see the topic "Configure Qshell to
run WebSphere® Application
Server scripts".
This command is only valid when used with WebSphere Application Server Version 6 and later application servers. Do not use it with earlier versions.
Command-line help is provided for service integration bus commands:
wsadmin> $AdminTask help SIBAdminCommands
wsadmin> $AdminTask help command_name
$AdminConfig save
This command creates a new messaging engine for a cluster bus member.
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.
A file store is a type of message store that directly uses files in a file system through the operating system.
You can specify the type of message store of the messaging engine to be a file store. The type of message store can also be a data store, for more information see related links.A data store consists of the set of tables that a messaging engine uses to store persistent data in a database. Refer to 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 only by using a different schema for each data store.
You can specify the type of message store of the messaging engine to be a data store, although the default is file store. For more information see related links. For the z/OS® operating system, you must
not create tables, so set this parameter to FALSE.
Depending on the choice of the message store and its attributes, you need to specify different combinations of the parameters. To avoid errors when specifying the message store when creating the messaging engine, see Avoiding errors when creating a messaging engine with a file store or a data store using the wsadmin tool.
Create a messaging engine on the bus
$AdminTask createSIBEngine -bus busNameCreate a messaging engine on the bus, using a file store to save messages, with default settings
$AdminTask createSIBEngine -bus busName -fileStoreCreate a messaging engine on the bus, using a file store to save messages, with options
$AdminTask createSIBEngine -bus busName -fileStore {{logDirectory "c:\fred" logSize 3636363}}Create a messaging engine on the bus, using a data store to save messages, with default settings
$AdminTask createSIBEngine -bus busName -dataStoreCreate a messaging engine on the bus, using a data store to save messages, with options
$AdminTask createSIBEngine -bus busName -dataStore {{createDefaultDatasource true datasourceJndiName myjndi}}Create a messaging engine on the bus, using a data store to save messages, with syntax
$AdminTask createSIBEngine -bus busName -createDefaultDatasource true -datasourceJndiName myjndi