Code top level flows
The FTM core contains the following high level flows:
- PhysicalTransmissionFlow
- PhysicalTransmissionFlow is responsible for processing all inbound transmissions. The flow logs it to the database and passes it to the inbound mapper for mapping to ISF.
- EventProcessingFlow
- EventProcessingFlow is responsible for processing the events raised by FTM to
drive the FSM engine of FTM as defined by the FSM model. This involves processing
events by determining the state transitions related to the current event and for each transition:
- Evaluating the event guard condition.
- Retrieving the FTM objects to be transitions.
- Calling the specified action, if any.
These flows are designed to be generic and must be included as a subflow in an application-specific flow.
The application-specific flows are usually referred to as 'wrapper' flows. The wrappers for the high level
flows are:
- Physical Transmission Wrapper Flow
- This flow needs to map message inputs to the generic PhysicalTransmissionFlow. These inputs may be MQInputNodes or any other IBM® App Connect Enterprise input nodes. The physical transmission wrapper flow also must identify the inbound channel, as it is required by the generic PhysicalTransmissionFlow.
- Event Processing Wrapper Flow
- This flow handles retrieval of event messages from the FTM event queue and passes them to the generic EventProcessingFlow.
In the simplest case, a deployment will have only a single physical transmission (PT) wrapper flow and a single event processing (EVT) wrapper flow. For applications that are more complex, it is possible to have multiple PT and EVT wrapper flows dedicated to handling the processing of different interfaces to FTM.
Both of the wrapper flows may need to contain subflows to include the mappers and actions that are implemented as part of the solution.