FTM methodology is oriented around using finite state machines (FSM) to control the
lifecycle of FTM objects. Therefore, each object identified in Identify FTM
Objects will have a lifecycle defined by an FSM model. The sample application builds on top of a
generic FSM model that is supplemented with a concrete IBM® App Connect
Enterprise implementation for
actions called by the generic FSM model.
Basically, the generic model contains FSMs for the following functionality:
- Inbound physical transmission
- Outbound physical transmission
- Outbound transactions
- Inbound acknowledgment transactions
Each of the generic FSMs supports a common activity that all FTM applications need
to do. Some applications may need to modify or extend the functionality of one or more of these generic FSMs,
but many applications are able to use them as-is.
The following tables show for each FTM object, the FSM that is used to manage its
lifecycle.
Table 1. Inbound physical transmission FSMs
| Physical transmission |
FSM |
| Payment Origination |
Generic : Inbound Physical Transmission |
| Payment Origination Batch |
Generic : Inbound Physical Transmission |
| Repair Response |
Generic : Inbound Physical Transmission |
| Liquidity Response |
Generic : Inbound Physical Transmission |
| Gateway Acknowledgment |
Generic : Inbound Physical Transmission |
Table 2. Inbound transaction FSMs
| Transaction |
FSM |
| Payment Origination |
Inbound Payment Transaction |
| Repair Response |
Generic : Inbound Acknowledgment Transactions |
| Liquidity Response |
Generic : Inbound Acknowledgment Transactions |
| Gateway Acknowledgment |
Generic : Inbound Acknowledgment Transactions |
Table 3. Inbound batch FSMs
| Batch |
FSM |
| Payment Origination |
Inbound Payment Batch |
Table 4. Outbound transmission FSMs
| Transmission |
FSM |
| Repair Request |
Generic : Outbound Physical Transmission |
| Liquidity Request |
Generic : Outbound Physical Transmission |
| Payment Initiation |
Generic : Outbound Physical Transmission |
| Client Acknowledgment |
Generic : Outbound Physical Transmission |
Table 5. Outbound transaction FSMs
| Transaction |
FSM |
| Repair Request |
Generic : Outbound Transaction |
| Liquidity Request |
Generic : Outbound Transaction |
| Payment Initiation |
Generic : Outbound Transaction |
| Client Acknowledgment |
Generic : Outbound Transaction |
Since the generic FSMs are handling almost all of the objects used by the sample application, FSMs need to
be defined for only the following objects:
- Payment Origination Transaction
- Payment Origination Batch
Working from the detailed sequence diagrams, candidate states can be identified for each of these
objects.