Messaging API

The Transaction Server Messaging API provides a mechanism by which the Transaction Server can send requests to, and receive requests from, remote services. These remote services can request specific actions against deposited transactions, such as repair, review, balancing, or fraud checking.

The remote services can be stand-alone Java™ applications or Java Platform, Enterprise Edition applications that run on an application server. The Messaging API uses the Java Message Service (JMS) as a platform and application neutral interface between the Transaction Server and the remote services.

The Transaction Server does not have any special knowledge of the remote service. As a result, the requests contain only a unit-of-work identifier and it is the responsibility of the remote service to fetch the transactions that it is to process. Services can use the Transaction Server API, which supports the retrieval of transactions from a unit of work. Or, for unique requests, the remote services can use database views. Database views can be used by applications that want to fetch transactions by using complex queries. Developing these database views is up to the remote service. The Transaction Server API must be used to fetch images because they are only available through the API.

IBM® provides Java client code that a remote service can use to transform service requests and responses between XML messages and Java objects. This code is in Java classes in the appbr.jar file.

The Messaging API messages are validated against the appbridge.xsd XML schema file. Only messages that conform to this schema are processed. Ensure that the Messaging API messages that are created by an external application conform to the schema.