Transaction Server API

When the Transaction Server is installed, the artifacts that are needed to develop a Transaction Server client application or user exit are installed in an SDK. The SDK contains the necessary Java™ libraries to create a Transaction Server client, task, or event handler.

The Transaction Server API provides methods for client applications to communicate with the Transaction Server. It supports Java applications when they are run under a Windows, Linux®, or AIX® operating system. The SDK subdirectory contains the necessary files to create a Java client.

The Transaction Server provides the focal point for the entire processing environment. Any access to data that is held within the environment is directed through the API and resolved by the Transaction Server. One exception to this rule is when the image data for an item is requested. You can fetch the data locally rather than have the Transaction Server return it.

The Transaction Server can also be customized by creating new tasks or handling events by using the custom code.

Sample programs are included and can be modified as needed. These samples are provided in the transaction-server/samples subdirectory.

The files that you need are provided in the FTM artifacts pod and must be downloaded from the pod. For more information about getting files from the artifacts container for your offering, see Getting the files from the artifacts container for your FTM offering.