EJM External Orchestration Patterns

There are several types of external orchestration patterns, as described below.

External Orchestration - Tool Retains Control of the Workflow

In this scenario, the client externally schedules all tasks via EJM, sending control messages for each task. The client manages the order of commands and enforces the task dependencies within the workflow. Tasks can include specific data loads, specific data extracts, and named STAR or PACE events.

External Orchestration - Tool Relinquishes Control of the Workflow

This applies with the group scheduling of multiple data loads using multiple files. In this scenario, the BPM triggers the initiation of a set of data loads for a corresponding set of input files, and then relinquishes control of the execution order and task dependencies to load these files onto the Eagle data warehouse. EJM uses an infrastructure preprocessor stream to properly order the data load tasks.

The table below shows the maximum number of files you can load as a group for each supported interface using one control message.

EJM Orchestrates the Workflow

In this scenario, EJM serves as the orchestration engine and the EJM infrastructure streams and Message Center services are customized to perform the tasks of the client production cycle, including the management of task dependencies and connections with upstream and downstream jobs and processes.