Outbound process flow:
Eg. Post real time transactions for sales order to third party.
- Sales order is created.
- Business event will be triggered to enter the SO header ID in staging table. (this staging table acts as Oracle advanced queue) this action event trigger can be custom code to feed header ID in staging table or oracle advanced queue.
- Enqueue process is message passing from producer application to OAQ.
- The staging table (also can be oracle advanced queue) is associate to AQ adapter. Staging table has the header ID.
- Dequeue process passes message from OAQ to consumer application i.e. SOA.
- AQ adapter continuously listen to the associates stg table or OAQ. As soon as the header id is enqueued in stg table, AQ adapter dequeues it and passes to DB adapter.
- There is DB Adapter setup for every interface packages communicating to SOA. On receiving the header ID, this DB adapter calls the interface package.
- Interface package sends the output data in OUT parameter to SOA.
- SOA transforms the output data into some third party readable structure like XML script.
- Third party adapter posts data to the database
Inbound Process flow
For real time inbound processing, the file will be placed by legacy system in a specific location.
- Legacy team will inform the file location to SOA team.
- SOA team will develop the file adapter for location which will continuously listen to file upload.
- Received file is transformed as per the oracle readable standards.
- DB adapter will call the interface package with input as legacy data.
- Interface package performs the operations and post transaction to database.
No comments:
Post a Comment