ODL delivery AIMs must define the following functions:
servayt() – provides a response to the SFM when it checks to see if the AIM is active, and identifies the transaction last processed using the lastID file.
For example:
int servayt(int [in, flavor] flavor, string [out] *pSerial, int [in] sfmFlavor)
servproc() – used by the SFM to send a transaction to the delivery AIM.
For example:
int servproc(int [in, flavor] flavor, string [in, out] *pSerial, string
[in] src, blob [in] dataBuf, string [in] tranid, string [out]
*errTxt, string [in] fkey, int [in] opts, char [in] priority, int
[in] sfmFlavor)
In addition, an ODL delivery AIM must provide the return values listed in Table 2-1.
You may want to have a delivery AIM cancel or skip a transaction if it finds an error that transaction production could not catch, such as assigning a duplicate part number. The transaction cannot be processed due to the error, but the delivery AIM that caught the error can continue to receive and process other transactions.
When a delivery AIM cancels or skips a transaction, the SFM marks the transaction for that destination as CANCELLED or SKIPPED. You can repair the suspended transaction using the Global Console. See Monitoring e-Biz Impact for detailed information about monitoring and log file maintenance.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |