ConceptAndConfiguration
The Event Manager flow of events:
A Sender sends events via the Event Service, which distributes the event to all subscribes, which have subscribed to the type of events. The Event Manager business layer which handles the communication to the Event Service will also ensure that the event is stored in the event table in the database.
Service, Senders and Subscribers may run in different machines. This means Senders and subscribes must have the same configuration of where the Event Service is running, and the Event Service have a similar configuration of how to run.
The configuration of all three components happens in the file DHI.Solutions.EventManager.Config in the MIKE OPERATIONS installation folder, see figure below.
Default content of the Event Manager configuration file:
By default an Event Service is started in each machine with MIKE OPERATIONS. It will communicate on port 8732 for setting up senders and subscribers and use a dynamic range of ports between 10000 and 11000 for the sending of events.
In a single machine setup this default configuration will ensure that JobRunner can send events and that MIKE OPERATIONS Desktop and MIKE Workbench receive these events from the Event Service.
In a multi-machine setup one machine should be designated Event Service and all config-files in all the participating machines should have the RemoteServiceAddress configured to point to a ip or machine name of the machine running the Event Service, e.g
Opening ports¶
In some windows systems the ports may be blocked and the permissions to use them has to be added via a command line.
On the server: -ensure port 8732 is open for Incoming communication, by making an Incoming rule in the Windows firewall.
On the client: - Ensure the dynamic port range is open for Incoming communication, by making an Incoming rule in the Windows firewall. - Run command (maybe as administrator):
The “