The configuration of messaging engines in service integration is very flexible. You can have a single messaging engine that does not provide high availability or workload sharing. With a cluster bus member, you can have a single highly available messaging engine. Alternatively, with a cluster bus member, you can have multiple messaging engines that share workload, or that share workload and also provide high availability.
The configurations that are possible depend on the type of bus member you create. If you create a server bus member, you can create only a simple configuration. If you create a cluster bus member, you can create any of the configurations in the previous list, depending on the number of messaging engines in the cluster and the behavior of those messaging engines. For more details, see the topic about bus member types and their effect on high availability and workload sharing.
For details and examples of the configurations you can create, see the subtopics.
To configure messaging engine behavior, add a cluster to a bus and use a predefined messaging engine policy. The predefined messaging engine policies support frequently-used cluster configurations, such as workload sharing and scalability, high availability, or a combination. You use messaging engine policy assistance, which creates one or more messaging engines and configures them to provide the required behavior. You can also use messaging engine policy assistance to set up a custom configuration. Messaging engine policy assistance guides you through the configuration and many of the settings are created automatically. For more information, see the topic about messaging engine policy assistance.
It is possible to add a cluster to a bus and configure the messaging engine behavior without using messaging engine policy assistance. Use this procedure if you are already familiar with it. Otherwise, use messaging engine policy assistance.
For more information about policies and configuration, see the topic about policies for service integration.
Configuration | Type of bus member | Number of messaging engines | Policy type |
---|---|---|---|
Simple | Server | 1 | Default ("One of N") |
Simple | Cluster | 1 | Static |
High availability | Cluster | 1 | "One of N" or "No operation" |
Workload sharing without high availability | Cluster | more than 1 (typically, one messaging engine for each server) | Static |
High availability and workload sharing | Cluster | more than 1 (typically, one messaging engine for each server) | "One of N" or "No operation" |