Outbound Transaction Optimization

It is recommended that the supplied generic model and actions be used, or that key elements from the generic model be applied into the existing application model, code, or both, where appropriate. When applying any changes to an existing FSM model, you are responsible for fully analyzing all changes; especially in actions.

From FTM V1.1, the following changes were made to the generic model to improve performance:
  • State transitions were reduced by two for each outbound transaction object
    • Fire and Forget Txn ( 4 -> 2 )
    • Request/Response Txn ( 5-> 3 )
    • Transmission ( 2 -> 0 )
  • A_RouteAndSendOutTxn was created to amalgamate four previous actions:
    • A_DoRouteOutTxn
    • A_CreatePTOut
    • A_MapAndPutToQueue
    • A_ProcessOutTxnSent
Fire and Forget Outbound Transaction FSM and Request and Response Outbound Transaction FSM illustrate the optimizations made for the outbound transactions and transmissions in the generic model from FTM V1.1. In the figures, the original FSM refers to the previous unoptimized release and the short FSM refers to the current optimized version.
Figure 1. Fire and forget outbound transaction FSM
FireNForgetOutTxnFsm.jpg
Figure 2. Request and response outbound transaction FSM
ReqNRespOutTxnFsm.jpg