Versions Compared

Key

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

Table-Driven Workflow Instancing

TheWorkflow Table can be used to instantiate multiple workflows interfacing similar sources and targets. Although almost every configuration aspect can be parameterized, the start/end-point identifiers (e.g. IP addresses, directories, login, passwords, etc.) are normally the most important.

...

Using the Workflow Table tab to add workflow instances

Workflow Execution Scheduling

MediationZone provides support for manual, real-time and scheduled execution of any kind of workflow group holding processing functions (i.e. collection, processing, distribution, or any combination thereof):

...

Graphical view of execution occurrence

Workflow Execution

The Execution Manager provides a graphical interface to manage the execution of workflow groups and the monitoring of their status and schedule. It also provides views of running workflows and detailed views of the contents of the workflow groups including throughput and other statistics.

...

Example of workflow group scheduling info in Execution Manager

Workflow Execution Suspension

A Suspend Execution configuration enables you to apply a restriction that prevents specific workflows and/or workflow groups from running in a specific period of time.

...

Execution of workflows has been disabled for period of time

Shared In-Memory Table Lookup during Workflow Execution

During execution of business logic, many workflows are dependent on retrieving data from a persisted storage, such as a database, by looking up data in own in-memory table. Each workflow instance will load/release its own lookup table during a workflow startup/shutdown. Therefore in the case of execution of many workflow instances, multiple loads/releases of the table will occur with unnecessarily high memory consumption.

...

Shared in-memory table lookup

Error Handling

Many types of error handling can be implemented using the workflow properties. Automated re-transmissions can be executed according to the preferred behavior, e.g. make a specified number of retries before aborting the re-transmission attempts as configured in the example below.

...