For transactions that always arrive in the same known order:
Define a field or datalink object for the data area that is the key.
Use the dbInsert filter to copy the data to the appropriate collection file. The production object can then send the transaction off to a null destination or to any delivery AIM that may need just that transaction’s data.
Once an acquisition AIM sends the last necessary piece of data, use the dbSelect filter to copy the other pieces of data from the collection files into that output transaction. Remember to make each call to the dbSelect filter from within an empty rule component object.
Remember, the dbSelect filter does
not perform concatenation. If there is already data present in the
current message area, this filter overwrites it.
Send the output transaction to the delivery AIM that routes to the application endpoint that required these pieces of data in one transaction. Optionally, use recycling to send the output transaction back through transaction production for further processing before passing it on to the delivery AIM.
If desired, use the dbDelete filter to delete the entries from the collection files.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
