| Warning |
|---|
While EagleML and EJM are version independent, your Eagle product suite must be at least version 12.1.5. |
...
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. 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.
...
EagleML provides a generic set of XML-based interfaces. They are described as XSD and implemented on the Message Center framework as Message Streamsmessage streams. The term Message Stream 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 delivered to the designated streams using a 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 Eagle's Automation Center.
...