IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Forward all stored operations

The sequence diagram for forwarding all stored operations is shown below. The last two messages from the ForwardingServerOperation show the communication that occurs when the host returns a failed or timeout response.

UML sequence diagram. See the flow of events that follows.

Flow of events
  1. The forwarder application calls the ForwardingServerOperation to forward all the records in the STORE table.
  2. The ForwardingServerOperation retrieves the first stored record from the STORE table through the StoreService. The first record is the record with the smallest ID number.
  3. The ForwardingServerOperation unformats the stored record, which is a hash table, and maps the values to the context data elements. The operation and the CommonCommunicationsService are passed to the forwarder.
  4. The forwarder uses the Common Communications service to send the host request.
  5. Upon receipt of a successful host response, the forwarder unformats the host response and updates the context before returning the host response to the ForwardingServerOperation.
  6. When the ForwardingServerOperation receives a successful host response, it deletes the record from the STORE table and commits the stored operation. See subflow 6.1 below.
  7. The result of the retrieved, forwarded, and committed stored operation is updated in the Electronic Journal table. See subflow 7.1 below.
  8. The ForwardingServerOperation retrieves the next record, and steps 3-7 are repeated until the last record in the StoreService has been processed.

Subflows

6.1 A failed or timeout host response message rolls back the stored operation in the STORE table.

7.1 The result of the retrieved, forwarded, and rolled-back store operation is updated in the Electronic Journal table.



Feedback