Adapting your own Solution to Use the Transaction Document Register
The transaction document processing framework supplied with LANSA Composer may not exactly suit every circumstance or organisation. You are, of course, free to use LANSA Composer's transport, transformation and orchestration features to design and implement your own transaction document processing solution.
If you do, you may still opt to use the transaction document register and the LANSA Composer Document Manager application to record and manage your inbound and outbound transaction document flows.
In order to adapt an existing solution to use the transaction document register, there are just two Activities that you need to add to your transaction document processing solution:
1. The TXDOC_REGISTER activity registers an in-coming or out-going transaction document in the transaction document register. Normally this should be done as soon as the document becomes available to the process and before significant processing is done for it.
2. After registering the document, and as the processing sequence proceeds to process the transaction document, you can record its progress and update the status in the transaction document register using the TXDOC_STATUS activity.
If you use these activities appropriately, you will be able to use the LANSA Composer Document Manager to enquire upon and manage your inbound and outbound transaction document flows (although some features may not apply). For more information, refer to:
4.2 LANSA Composer Document Manager