UglyPaymentRequestFailsParse.103

An ugly payment cannot be fully parsed by IBM® App Connect Enterprise. The parsing failure means that it cannot be mapped to ISF. After submitting this message, the physical transmission for this payment should appear on the all alerts window as well as on the physical transmission search itself (shown in the following figure).

Note: Since the transmission was not mapped to ISF, a matching transaction was not created and a search returns no transaction objects.

Figure 1. Physical Transmission for Ugly Payment

In the sample application, the only option for an ugly payment is for the operator to cancel it with a command. To cancel the ugly payment, click the transmission in the all alerts (or physical transmission search) window to show the details window. On the details window, click the resolve resolve icon (subject to user authorization permissions). The only available resolution action is cancel. Cancellation places an operator command message on the FXH.SAMP1.COMMAND message queue. The following figure shows the resulting command physical transmission object.

Figure 2. Operator Command Transmission: Cancel

The following figure shows the transaction for the operator command.

Figure 3. Operator Command Transaction: Cancel

Click the command transaction to show the details. The related objects listed in the following figure, shows that this transaction targets the original ugly transmission.

Figure 4. Command transaction: Targeted object relationship

Click the link for the targeted transmission to show the state transitions. The following figure shows that the transmission has now completed and is in a final, failed state.

Figure 5. Command transaction: Final state history