| Warning |
|---|
While EagleML and EJM are version independent, your Eagle product suite must be at least version 12.1.5. |
...
The main purpose of EagleML is to serve as the Eagle Canonical Data Model. EagleML uses an industry standard based XSD that serves as Eagle’s canonical data model (standardized template) for exchanging different data formats and establishes a clear set of rules for communication for inbound and outbound data exchange.
...
Messages are used for providing data exchange between systems. They act as envelopes that carry either data transactions or control instructions or exception alerts or events and notifications. Structurally, messages have headers that contain messaging specific elements (such as Message Id or Message Address) and bodies. The body of the message can be either data transaction or control instructions.
...
Control messages are intended for application integrations and have elements for tasks and workflow execution, and exception and notification patterns such as Task Correlation Id, 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. However, they also They also have specific elements based on the purpose of the message to reflect integration patterns such as Message IdID, Correlation IdCorrelation ID, and Message Address.
Transactions
Transaction types are wrappers over Data Objectsdata objects. A transaction has a header and body that contain a data object. Headers of transactions Transaction headers describe data object types and actions to be performed over the data object that is contained in transaction’s body.
...
Transactions are always wrapped into Messages. One Message can carry one or many transactions. This is done to support both single record real-time loads as well as batch-based loads.This This enables EagleML-2-0 to serve as both a payload for messaging systems and FILE based transfers.
...
Data objects are the types that describe various interfaces. They actually comprise what we refer to as the Eagle Canonical Data Model. Data objects are all extended from one base type, EagleObject, which has minimum required elements.
...
EagleML provides a generic set of XML-based interfaces. They are described as XSD and implemented on the Message Center framework as Message Streams. The term Message Stream is used to describe components that make up the Message Center interfaces, including the delivery location for the incoming data, XML mapping rule files, and panels. The data is being delivered to the designated streams by using variety of methods including file based uploads to the Incoming folder on the Web server, or by Messaging: MQ Series, JMS, HTTP, or by using the Send Data feature in the Eagle's Automation Center.
...