The
FTM sample application raises external events by publishing them to an
IBM® MQ topic. For milestone events, the
FTM sample application defines
publication rules that override the definitions for events
E_InTxnFailed and
E_OutTxnFailed in generic mode. These publication rules are shown in the following
table.
Table 1. Publication rules for E_InTxnFailed and E_OutTxnFailed
| |
PublishHostedServiceTxnFail |
PublishInvokedServiceTxnFail |
Notes |
| For event |
E_InTxnFailed |
E_OutTxnFailed |
|
| Filter |
$ContextEQ{
TXN_TYPE,
'PAYMENT_ORIGINATION'
}
|
$ContextIN{
OUT_TXN_TYPE,
(
'REPAIR_REQUEST',
'LIQUIDITY_REQUEST',
'PAYMENT_INS'
)
}
|
|
| Emitter |
PublishServiceMilestone |
PublishServiceMilestone |
This is the label to the emitter flow. |
| Location |
PubSub://ComIbmFxh/
FTM Sample App/
FTMHostedServiceTxnFail
|
PubSub://ComIbmFxh/
FTM Sample App/
FTMInvokedServiceTxnFail
|
This is the topic to use when the external event is published. |
| External event name |
FTMHostedServiceTxnFail |
FTMInvokedServiceTxnFail |
|
Summary events have a dedicated FSM model. This model handles the events that conform to the Common
Base Event specification that trigger publication of the external events. Because actions in the code define
the topic, a publication rule for them is not necessary.