Message content

Remote services can send the Transaction Server requests to insert, delete, change, or move transactions, segment states, batch states, and adjustments within an existing deposited batch (ICL). The AppBridgeConstants interface provides the supported message types along with the various return codes and return descriptions. This class is contained in the txsvrcli.jar file. The NameValuePairBean class is used to provide additional information as name and value pairs for the request. This class is in the appbr.jar file.

For each of these requests, Transaction Server returns an AppBridgeServiceResponse that has a return code. If the return code is not AppBridgeConstants.ABRC_SUCCESS, the return code is a unique code indicating the reason. The return message has a string describing the error, including the exception data if applicable. For information about the other return code values, refer to the Javadoc information.

Some of these requests take a transaction identifier as the unit of work. This is a single, long value that is the primary key of the payment table in the FTM database.

When the type is not specified in the JMS header, the message is not parsed by the Messaging API. If the AppBridgeMessage class is not used to create the message that is placed on the queue, add the type to the JMS header by using the setJMSType method in the javax.jms.Message interface. Use the msgType parameter that is specified in the ibmPaymentsDirectorMessage header as input for the setJMSType method. Only text messages are supported.