Messaging API

The Messaging API provides a mechanism by which the Transaction Server sends requests to and receives requests from remote services. The services perform specific actions (such as repair, review, balancing, and fraud checking) against deposited transactions. The services themselves may be J2EE applications running on an application server, stand-alone applications, or legacy processes.

The Messaging API uses the Java™ messaging service as a platform and application neutral interface between the Transaction Server and the deployed services.

The Transaction Server is not required to have any knowledge of the remote service. As a result, requests contain only a unit of work identifier. It is the responsibility of the service to fetch the transactions that it is to process. Services perform this operation using the Transaction Server API; or, for unique requests, the database views can be used.

The Transaction Server API supports the retrieval of transactions from a unit of work. Applications that fetch transactions using complex queries should use database views, although images are available only through the Transaction Server API.

IBM® provides Java client code that the service can use to transform service requests and responses between XML messages and Java objects.

Note: Messages can be used only to insert, delete, change, or move transactions and adjustments within an existing deposited batch. Common Services uses one of its supported protocols to deposit batches through the Gateway.