This is a text description of dysrv_i8.gif.
JMS deployment communication occurs when the DSJMSDriver allows for asynchronous access to services using a Dynamic Services gateway in the form of a JMS daemon. The mode of operations with this driver lets it submit requests asynchronously to an AQ/JMS queue in a remote database. It assumes the existence of this JMS daemon running somewhere that listens asynchronously to the same queue where requests are being submitted. The daemon takes on the role of the Dynamic Services engine and processes the request, generating a response, and submitting that response into another queue that the DSJMSDriver asynchronously listens to. On the service consumer application side, therefore, listeners can be registered to be informed when the response is returned.
The JMS deployment communication follows these steps.
1. The service consumer application asks for a service execution.
2. The DSJMSDriver sends a request to the Oracle Advanced Queuing (AQ) request queue.
3. The DSJMSHandler asynchronously listens to requests from the AQ request queue.
4. The DSJMSHandler communicates with the Dynamic Services engine to execute the request.
5. The DSJMSHandler sends a response to the AQ response queue.
6. The DSJMSHandler asynchronously listens to responses from the AQ response queue.
7. The response is delivered by the DSJMSDriver to the service consumer application.