Using a communication object, a data packet is received from the endpoint application.
Headers/footers and other protocol characters are stripped using message frame objects and the data is placed into a blob variable.
If necessary, the control flow attached to the message frame performs data blob manipulation. The AIM may contain multiple message frames with their associated control flows.
The AIM receives the next packet of data from the communication object and processes it through message frames.
The framed data is appended to the blob variable.
The message frame object and control flow continue the append action until the blob data variable accumulates the transaction data, then sends the data to an SFM by calling one of the SFM routing functions (route_vprod(), route_vrec(), and so on). See the e-Biz Impact TRAN-IDE Guide for information on routing functions.
An acknowledgement is sent to the endpoint based on the return value from the SFM using the send() method.
Sources defined in the SFM configuration can receive a ping() DFC. If you do not have a ping() DFC entry point in your acquisition AIM configured to receive these commands, unpredictable results may occur.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
