| Warning |
|---|
While EagleML and EJM are version independent, your Eagle product suite must be at least version 12.1.5. |
...
EagleML covers a large variety of models including models for data interfaces (which are divided into transactions and object interfaces) as well as interfaces for messaging and flow control. This section describes the general structure of EagleML-2-0, including the an explanation of the data and control interfaces and , object types and inheritance, and the relations between them.
EagleML-2-0 is was developed to be used for any interfacing interface with Eagle. It can be used with messaging architectures architecture and delivery protocols like JMS, MQS, ESB-based architectures, SOAP/REST Web Services; as well as FTP, SFTP, HTTP FILE-based transfers.
...
The control section of EagleML-2-0 is meant to enable SOA-based flow control interfacing and allow for external orchestration. It can be especially useful for Enterprises that are looking for a modern style application integration where BPM acts as a central workflow control of the entire system.
There are 3 three distinct types of objects which constitute EagleML:
...
Messages are used for providing data exchange between systems. They act as envelopes that carry either data transactions or control instructions or as exception alerts or events and notifications. Structurally, messages have headers that contain messaging specific elements (such as Message Message Id or Message Address) and bodies. The body of the message can be either data transaction or control instructions.
There are a large variety of messages in EagleML-2-0, which can be grouped into two main types - : data messages and control messages.
...
Control messages are intended for application integrations and have elements for tasks and workflow execution, and exception and notification patterns such as Task Correlation IdID, Task Parameters, Task Status, Severity Code, Reason Codes, Error description and Resolutions. Control messages are XML-based files that contain descriptions of tasks to be performed on the data being transferred and how the data is to be consumed and published. Control messages are also known as CMs or Run Task Requests (RTRs). The coordination of control messages forms the basis of the Eagle Job Management (EJM) framework.
There is a high level of relationship between message headers. The headers for data and control messages have common elements that encapsulated in most base type MessageHeader. They also have specific elements based on the purpose of the message to reflect integration patterns such as Message ID, Correlation ID, and Message Address.
...