Differenze tra le versioni di "EEM - External Event Management"
(→Monitoring system configurations) (Etichetta: visualeditor) |
(→Monitoring system configurations) |
||
Riga 111: | Riga 111: | ||
|- | |- | ||
| <u>Request Identification Tag</u> || || | | <u>Request Identification Tag</u> || || | ||
− | |||
− | |||
− | |||
|} | |} |
Versione delle 11:15, 18 ago 2015
EEM - External Event Management is one of the complementary modules of itmSUITE®. The module is aimed to enable interactions between itmSUITE® and third party applications (interfaces). The supported direction of the data flow is from the external application to itmSUITE® (input). It is possible to define and implement outbound data flow and interfaces by using the action engine component of the itmSUITE®.
Indice
Introduction
The module can receive information (inbound messages) with two modes which may be activated at the same time:
Active channel
In this mode data acquisition is made by means of mails. EEM verifies at regular intervals the existence of mail messages in a configured mailbox and processes them when found.
Passive channel
In this mode, EEM makes available web services in order to acquire data.
EEM processing steps
EEM works on inbound messages received by means of the active or passive channel through a three steps process:
- EEM processes and validates the incoming message
- EEM passes processed messages to message bus which, in turn, dispatches them to the recipients (the modules configured to subscribe to the message)
- itmSUITE® recipient module performs the configured tasks for the received message by means of the action engine
The above mentioned three steps process is illustrated in the figure below.
EEM configuration
The following paragraphs gives an overview of EEM configuration.
Active channel configuration
Using EEM menu Active Notification Channels it is possible to define an active channel which is mapped on an existing mailbox.
The image below shown the parameters needed to configure an active channel.
The following parameters shall be provided:
Field | Meaning | Comments |
---|---|---|
Id | ||
Name | ||
Status | ||
Logging | ||
Host | ||
Port | ||
Authentication Required | ||
Username | ||
Password | ||
Passive channel configuration
There is no specific configuration for passive channels.
Monitoring system configurations
A monitoring system configuration tells EEM what to do in the very first step (processing and validating an inbound message).
For each monitoring system configuration there are two configuration screens, one for general settings and one for specific parameters. The General configuration is shown in the screen below.
The following parameters shall be provided:
Field | Meaning | Comments |
---|---|---|
Id | ||
Name | ||
Type | ||
Status | ||
Active Channels Available | ||
Email Identification Strategy | ||
Email Identification Value | ||
Passive Channels Available | ||
Request Identification Tag |
The image below shown the Parameter tab used by the system to collect information present on a message.
The following parameters shall be provided:
Field | Meaning | Comments |
---|---|---|
Id | ||
Name | ||
Status | ||
Logging | ||
Host | ||
Port | ||
Authentication Required | ||
Username | ||
Password | ||
One message is validated if the Identification Strategy is respected and all the parameters are presents into the body of message