About EJM Activities

In the EJM Monitoring Tool, several types of activities can be monitored, including processes, subprocesses, and tasks. The execution and status of EJM processes can be monitored at the summary level and at the message level. EJM processes created in IWS can be saved as IWS solutions and executed via the EJM framework which promotes connectivity between Eagle application modules, Business Process Management (BPM) tools, and third party schedulers. You can also monitor the status of EJM processes created in Eagle's classic modules such as Eagle's Message Center Editor.

EJM Processes

An EJM process is one or more subprocesses (steps) connected together. EJM processes manage communication and data exchange between Eagle modules and third party systems. When multiple subprocesses are involved, EJM orchestrates internal workflows within the Eagle product suite. Created in IWS, EJM processes can be set up as schedule-based or triggered by the arrival of files.

EJM processes can also handle complex workflow conditions, such as concurrency where some subprocesses occur concurrently while other subprocesses occur only when specific subprocesses are completed. EJM processes can also handle subprocesses in which one file is used by multiple tasks.

The following high level diagram describes the relationship between EJM processes, subprocesses, and tasks.

EJM Subprocesses

Created in IWS, EJM subprocesses (steps) group together EJM tasks that accomplish a specific purpose, for example, extract or load entity data.

EJM Tasks

Created in IWS, EJM tasks contain a sequence of message streams organized in a predetermined order.
Each EJM task contains message streams that include:

• Control messages that specify how data is to be processed.
• Data messages with the actual data file/payload.
• Acknowledgements and status reports that together ensure proper communication and data exchange.

Message streams are Eagle's rules-based packaged instructions for extracting, transforming, and loading data from multiple file formats into and out of Eagle databases. Message streams include the delivery location for the incoming data, XML mapping rule files, and relevant data validation. Inbound message streams deliver data to Eagle databases whereas outbound streams extract data out of Eagle databases and deliver it to specified locations.