Transactions with a value of “ENGINE” (sent using route_vrec() or route_vrecx()), or with a user-defined engine name (sent with a route_recx()), are processed using this procedure:
The same process occurs as when the transaction ID is set to a single production object (“Transactions using a production object ID”), except that now the transaction is tested against each of the production objects specified in the user-defined engine, or against all productions objects (using “ENGINE”).
If the transaction passes all of the relevant tests for one or more of the production objects, SFM writes it to the transaction log file, and returns a value of 1 to the acquisition AIM.
If the transaction does not pass any of the relevant tests for any production objects, the SFM writes the transaction to its unrouteable log file, and returns a value of -6 to the acquisition AIM.
All production objects must have a production record
in the SFM configuration file. See the e-Biz Impact Configuration
Guide for details.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
