The transaction routing type determines the production objects to which a transaction is submitted.
route_vprod – submits the transaction to one specific production object, as specified by the transaction’s production IDs defined in the e-Biz Impact Configurator.
route_veng – submits a transaction to a specific group of production objects as specified with the EngGroup parameter.
route_vrec or route_recx – submits the transaction to all production objects. You must specify a transaction ID of “ENGINE” in the function commands.
Transaction production can submit a transaction to one or more production files, and to one or more production objects within each production file. If a transaction is not accepted and processed by any production objects, the transaction is in error. To avoid an error, use a null destination.
Submitting a transaction to a production object does not mean the production object generates an output transaction, because a transaction may fail to qualify for production.
Figure 1-2 is represents the path an input transaction could take. The transaction is submitted to three production files, each of which has multiple production objects.
Figure 1-2: Sample transaction production
The transaction in File A passes qualification in all three production objects. Each production object generates an output transaction, which is sent to a single destination. The transaction in File B passes qualification in only two of the three production objects. Each of the two production objects for which the transaction does qualify generates an output transaction, which is sent to one destination. The transaction in File C passes qualification in both production objects. Each production object generates an output transaction, one of which is sent to one destination and the other sent to three destinations.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
