Data Sealing on Communications

There is no seal check on the representation of a Communication or Message due to the possible performance impact in case of large content. This would impact user experience, since the seal gets calculated each time an object is retrieved from the database.

To solve this, the digest on the representation gets recalculated during transition from the incoming Communication trough the different states up to transmission to Swift. Tampering with the representation will be detected and reported back to Trax Payments. The seal repair tool will not work when the representation has been tampered with.

TSG receives a JMS message and creates a Communication and calculates the digest.

The job TSG-outbound-integrate will perform the ValidateTSGCommunicationRule on the incoming Communication digest and creates an outgoing Message.

The job TSG-outbound-transmission will perform the scheduleOutgoingGatewayCommunicationRule in wich he validates the outgoing Message digest and creates an outgoing Communication.

The job TSG-process-waiting-FileAct will perform the FileActProcessWaitingCommunicationRule in which he validates the outgoing Communication digest and send the representation to Swift.

In case the digest validation fails an Exception is thrown which results in a Failed status being sent back to Trax Payments.