Simple configuration without workload sharing or high availability
A simple configuration consists of a single messaging engine running on only one server. This configuration does not provide workload sharing or high availability.
If the server on which the messaging engine is running fails, the messaging engine cannot be failed over to an alternative server. A simple way to create this configuration is to add a server to a bus. The messaging engine is created automatically and the default service integration policy, "Default SIBus Policy", provides suitable behavior. Alternatively, we can add a cluster to a bus, then configure a Static policy for the messaging engine so that the messaging engine runs on only one server.
The following diagram shows a simple configuration created by adding a server to a bus. There is a single messaging engine, ME, with a data store, running on one server. If the server fails, the messaging engine becomes unavailable until the server is restarted.
Figure 1. Simple configuration with a single server
Figure 2. Simple configuration after the server fails
In this configuration, we do not need to enable access to the data store from other servers because the messaging engine cannot run on any other server.