Coding the client application

When coding the client application, adhere to the call sequence shown in the sequence diagram shown in the following figure.
Figure 1. Sequence diagram
gpy_izge_TranSrvrSeq.jpg

Each series of processing requests must be preceded by an initialization request. At the end of processing by the client application, the final call must be either a terminate request, which commits any database changes, or a cancel request, which rolls back any database changes. Every API call sequence must end with either terminate or cancel. To determine the possible processing requests and any requirements they may have, see API Configuration File.

Actions requiring user intervention should not be performed between the initialize request and the terminate or cancel request. Get any user input required prior to initializing the request or do one initialize-request-terminate sequence before requesting input and a second initialize-request-terminate sequence afterward. If user input is requested between the initialize and terminate requests, the database connection may time out.