Setting up the Notification Service

Background

Starting with release 3.4.0 of OpenEMPI we switched to Apache ActiveMQ Artemis as the standard messaging service implementation. Apache ActiveMQ Artemis is an asynchronous messaging system, an example of Message Oriented Middleware. Using an asynchronous messaging system allows you to integrate OpenEMPI with other systems using a loosely coupled architecture. Messaging systems decouple the senders of messages from the consumers of those messages. The decoupling applies to the timing of the sending and receiving of the messages since the receiver or receivers do not need to be accessible or available when the messages are sent out. The decoupling also applies to the technologies used by the senders and the receivers since it is possible to receive the messages from the messaging system using a wide variety of technologies that don't match the technologies used in the implementation of OpenEMPI. Lastly, the decoupling also applies to the routing of the messages since the sender does not have any awareness of who the receiver is and through configuration you can setup either single or multiple receivers for the messages sent out by OpenEMPI.

Starting with release 3.5.1, OpenEMPI also supports RabbitMQ as the message broker instead of Apache ActiveMQ Artemis. You can find detailed configuration information for the supported messaging brokers in the corresponding documentation page below.