Versions Compared

Key

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

...

An Eagle workflow may be as simple as getting a file from a vendor location (be it somewhere in the cloud or on an FTP site) and then loading it into the application, or it may be more complex, linking multiple services together, managing exceptions, parallelism, invoking a remote call and providing notification. Using Eagle’s XML technology, you can build custom data driven workflows to meet their exact requirements.

...

  • Traditional Scheduler  Using Eagle’s scheduler capabilities it is possible to build a workflow that triggers jobs in either a sequence, based on basic concurrency logic, or the state of a preceding event. This architecture typically uses a polling mechanism. In some cases the context of the workflow is not maintained, that is, load securities , poll for changes based on update date and execute an engine on securities that have changed and then publish.
  • Data Driven – In a data driven workflow, the context is typically maintained and managed through a series of control messages to maintain and interrogate status of the service. Using the preceding example, load securities, and then pass changed securities to the engine for processing. There is no need for a polling process, the consumer is fed the exact payload to process.

...

Orchestration describes the automated arrangement, coordination, and management of services.”

You Using EJM, you have the following choices in how a custom workflow is orchestrated using EJMorchestrated:

  • Eagle orchestration, using Eagle’s native scheduling and data integration capabilities, we will refer to this as Eagle orchestration.
  • External orchestration, using Enterprise job schedulers, such as Control-M, AUTOSYS, Tidal and others or via BPM frameworks and application (such as Pega or IBM’s Lombardi product).

Both orchestration patterns leverage the same rich set of integration and workflow APIs to initiate Eagle services. Those APIs we We will refer to generically these APIS as Control Messages. The difference lies where the management, or orchestration, of these services resides. With that said there is certainly a possibility that a hybrid approach can be constructed.

...

If you are using the XSCHEDULE toolkit today, the external orchestration provides a number of benefits such as alternative transport models, decoupled integration (i.e. For example, cloud to cloud) and enhanced management capabilities with regard to the control and reporting of jobs.  

...