Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In the Message Streams workspace, you can create and manage message streams and specify message stream options. 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. You can manage data triggered and scheduled streams and copy and customize Eagle-provided default streams. To schedule message streams, access the Schedule workspace and create and schedule Message Stream Process events.

You can also submit message streams to run ad hoc, test the stream syntax prior to execution, and view stream messages. In the Monitor workspace, you can view the status of all message streams, reprocess messages that failed, and review and resolve any message stream exceptions. Message streams are also used in Eagle Job Management (EJM) processes that allow you to manage communication and data exchange workflows between Eagle and third party systems.

You can manage message streams as follows:


About Data Triggered Message Streams

...

When you create message streams that will be scheduled, you can incorporate these streams into Message Stream events, add them to jobs, and schedule Message Stream events to run on demand or on a schedule.

...

Note

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 Message Streams 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.

Note

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.