The Messaging Monitoring System (MMS) is a component that implements a notification system for sending messages associated with specific events. The events and messages are configured in the database as well as the templates that define the content of each message.
Each message is delivered in accordance with a dedicated connector object, implemented by default or customized.
Depending on the scenario considered, the issuing entity may also be interpreted as the source of a file and the entity receiving can be interpreted as the target of the same file. In this case the message is interpreted as a file to generate and deliver.
Who is who ?
- The windows service MessageMS is responsible for periodic monitoring of configured events. For each elegible event a package is built with basic information of the application and inserted into the message queue configured;
- The windows service MessagePS is responsible for processing data requests inserted into message queue: message is generated based on the template and sent. The transmission of messages is made from the objects using connectors. By default connector objects are available for communication via SMTP server, web-form POST(s) and invocation of web services;
- The component MessagingManager offers the options of 1) sending an explicit message or 2) the processing of an event;
- The successful delivery of messages is registered in the database. The same goes for messages whose deadline or number of attempts is exceeded;
- For messages sent in error is sent an e-mail alert notification is sent for the system administrator;
The configuration of events and messages is done at database level, Windows Registry or configuration file.
How does it works ?
The sending of one or more messages associated (s) to an event is achieved through:
- An explicit request to send message(s) by the entity that invokes. The order can be processed in a synchronously or asynchronously manner;
- Automatic processing of events configured through dedicated monitoring services:
1. The activation conditions of the event are checked;
2. Messages are generated according to the associated message type(s) and template;
3. Each message is delivered through a connector object.
What kind of messages can be configured ?
- Message with format HTML / TEXT generated from the template and specific language for sending via mail (e.g. reservation request);
- Message with format HTML / TEXT generated from the template and specific language for sending via regular mail (e.g. periodic reports of reserves);
- Message with format HTML / TEXT / XML / etc and sent as e-mail or as a file to transfer to a directory and / or remote server via FTP (e.g. XML electronic invoice);
- Invoke web-services parameterized with specific information including or not the message (HTML / TEXT / XML / etc), sender and recipients;
- Invocation of web-forms parameterized with specific information including or not the message (HTML / TEXT / XML / etc), sender and recipients;
What characterizes how the message is delivered/sent ?
i. What and of what type of connector object is responsible for delivering the message (Communication Channel) ?
Default types of connectors are available for:
- Delivery of mail messages;
- File delivery;
- Delivery of messages via invocation of web services;
- Delivery of messages via web-form POST
ii. How should be processsed the delivery(Dispatch/Delivery properties) ?
- The number of attempts to send the message;
- Date limit for deliver;
- Delivery priority;
- Immediate delivery ?
When installed in any project at Production level, the behaviour of the MMS system can be monitored online through specific tools developed for this purpose. It´s possible to monitorize all messages sent successfully, pending to be sent or delivered in error. The following information is made available:
- Event and associated message;
- Origin / Sender and Destination / addressee;
- Delivery priority;
- Number of attempts made;
- Content of the message;
- Information collected and used to generate the message (message source);
- Dates of application for sending and receiving;
- Error associated to last send attempt (in the case of pending messages)
The information contained in this article is made available for reading with authorization of Expedita Ltd