Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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.
About Data Triggered Message Streams
When you create message streams that will be triggered by events outside of Automation Center, such as arrival of data files from third party vendors, you can only monitor the stream status and resolve any generated exceptions in the Automation Center. These message streams cannot be scheduled.
On this page
tocAbout Scheduled Message Streams
When you create message streams that will be scheduled, you can add them to jobs, and schedule Message Stream events to run on demand or on a schedule.
About Default Message Streams
Eagle provides a set of default message streams that you can copy and modify to suit the needs of your business. Eagle's default message steams display a negative number in the Message Stream ID column (for example, -2108) and have the following naming convention:
eagle_*
| Info |
|---|
Eagle recommends that you do not create custom message streams with eagle_* names and that you do not change or delete Eagle's default message streams. |
About Data Formatting Files
From the Events workspace, you can access and modify data formatting files used by message streams to transform and prepare data for loading into and out of Eagle databases. Reviewing and modifying data formatting files may be useful when troubleshooting message stream issues.
Each message stream specifies data delivery instructions (inbound or outbound in relation to Eagle databases), supports a single data format, and uses a single Ruleset file. A Ruleset file directs data in the message stream to the appropriate Rule file for formatting based on the message type. For example, if the message stream is designed to load security reference data, the Ruleset file may route fixed income securities to one Rule file for processing and equity securities to another Rule file.
For inbound message streams, the Rule file parses the incoming data and performs any additional lookups and validations. The data elements are then mapped to the Eagle tag format to allow loading into Eagle databases. For outbound message streams, the Rule file maps the data extracted from Eagle databases to the external system's specified format and performs any additional processing, if required.
| Info |
|---|
Eagle also supports the Eagle ML 2.0 XSD specification with a set of generic XML-based interfaces described as XSD and implemented on the Message Center framework as message streams. Eagle ML allows you to exchange data with increased accuracy and achieve optimal data exchange efficiency. For more information about EagleML, visit the EagleML wiki pages. |
On this page
| Table of Contents |
|---|