Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 3 - Methods of Execution Event-Driven Execution Model
Intelligent Business Integration Reference Guide
43
A watch may have multiple map instances executing simultaneously. The Event
Server uses its resource manager to insure that map inputs and outputs remain in
a consistent state.
Event Server Methodology
Whenever the Event Server detects a new event trigger, the watches associated
with that trigger are either:
♦ Initiated, thereby causing the map to execute
♦ Placed in an initiation pending state, awaiting the completion of all specified
triggers
♦ Maintained in an initiation pending state until operating system resources (such
as threads) are available
The Event Server initiates an individual map thread for each successful
combination of specified triggers. Multiple instances of the same map component
can be invoked and executed simultaneously if the Event Server is configured to
take advantage of concurrent multi-threading of map execution for performance.
Alternatively, if strictly sequential execution architecture is required (FIFO);
configuring the Event Server accordingly can accommodate this. This concurrent
versus sequential capability can be configured at the individual map component
level. So maps contained in a system could be concurrent, while others could be
set to execute sequentially.
Business Advantages
Some of the main business advantages to using the Event Server are:
♦ Automatic system execution
♦ Multi-threaded environment for multiple transactions. Linear scaling across
multiple CPUs
♦ Process prioritization