The members of a service integration bus are the application servers and clusters within which messaging engines for that bus can run. When you add a new bus member, you configure its message store, which is either a file store or a data store.
If you add a server as a member of a bus, WebSphere® Application Server creates a messaging engine for the server. By default, the messaging engine is configured to use a file store. If you choose a data store, you have the choice of using the default JDBC data source and Derby JDBC Provider for its data store. If you do not want to use the default data source configuration, you can choose to use a different data source or you can configure the data store to use a different JDBC provider.
If you subsequently delete a bus member and then recreate it, you should make sure that you understand the life cycle of the file store or a data store. Refer to Data store life cycle and Removing a messaging engine from a bus for details.
If security is enabled, and the bus has mixed-version bus members, the bus members establish trust by using an inter-engine authentication alias. If you add a server as a bus member at WebSphere Application Server Version 6, and it is the first bus member at this level, you must select or create an authentication alias during this task. This action sets the inter-engine authentication alias.
You can optionally tune the initial and maximum Java virtual machine (JVM) heap sizes. Tuning the heap sizes helps to ensure that application servers hosting one or more messaging engines are provided with an appropriate amount of memory for the message throughput you require.
In this information ...Related tasks
Related reference
Related information
| IBM Redbooks, demos, education, and more(Index) |