This simple configuration consists of a single messaging engine running on only one server.
This configuration has a single messaging engine with no provision for either 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. The easiest 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, you 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 that is created by adding a server to a bus. There is a single messaging engine, ME, with data store DS, running on one server. If the server fails, the messaging engine becomes unavailable until the server is restarted.
The data store for the messaging engine needs to be accessible by only this single server, because no other server can run the messaging engine.