Scribd
Upload
130 views

OSB - Async Service Pattern With OSB

This article summarizes an approach for implementing asynchronous service patterns with Oracle Service Bus (OSB). The key steps are: 1. Create an asynchronous BPEL process 2. Configure a response queue for storing asynchronous responses 3. Import WSDL and XSD definitions for the asynchronous service into OSB 4. Create a request proxy, business service and route for initiating asynchronous calls 5. Create a response business service targeting the response queue 6. Create a response proxy for receiving callback responses 7. Configure the request route to specify the callback endpoint in the message header.

Uploaded by

SOA Training
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
130 views

OSB - Async Service Pattern With OSB

This article summarizes an approach for implementing asynchronous service patterns with Oracle Service Bus (OSB). The key steps are: 1. Create an asynchronous BPEL process 2. Configure a response queue for storing asynchronous responses 3. Import WSDL and XSD definitions for the asynchronous service into OSB 4. Create a request proxy, business service and route for initiating asynchronous calls 5. Create a response business service targeting the response queue 6. Create a response proxy for receiving callback responses 7. Configure the request route to specify the callback endpoint in the message header.

Uploaded by

SOA Training
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Async service pattern with OSB

This article is from the excellent Blog by oraclefusion1011.

See complete article here - http://oraclefusion1011.blogspot.com/2011/04/aync-servicepattern-with-osb.html . It is reproduced here for easy reference only. OSB having no inherit support for Async communication makes it difficult to design communiaction with Async services, here i am trying to explain the async pattern that can be followed and works fine : 1. Create a Async Bpel 2. Response Queue : Create one response Queue to save all the async messages 2. OSB Resources - WSDL for the Async service : Import the WSDL - XSD for the Async service : Import the XSD - requestProxy start endpoint of the osb flow - requestBussServ service based on the endpoint of the service running on SOA - responseproxy Any soap service which will receive the callback of the asynchronous service call. - responseBussServ any soap service with jms endpoint, which will put the received callback in the queue. 3. Create RequestBS This will be based on the WSDL. 4. Create ResponseBS , this will invoke the JMS Queue to put message to that. Service Type : Any XML Service Protocol : jms Endpoint URI : jms://localhost:8001/MyJMSConnFact/AsyncRespQ Message Type : text 5. Create Proxy based on this BS : Any XML Service 6. Create Proxy based on the RequestBS On the message flow edit the route action from Proxy to BS for header - Add action -> Assign <soap-env:Header xmlns:ns1="http://schemas.xmlsoap.org/ws/2003/03/addressing"> <ns1:MessageID>ws:uniqueAddress</ns1:MessageID> <ns1:ReplyTo> <ns1:Address>http://localhost:8011/AsyncOSB/Proxy_Services/ResponseQProxy</ns1:

Address> </ns1:ReplyTo> </soap-env:Header> Assign this to header to specify the callbasck proxy ie ResponseQProxy 7. Now we have complete configuration Flow : RequestProxy[Set header for callback in message flow] -> RequestBS -> Call Bpel ResponseJMS <- ResponseBS <- ResponseProxy

You might also like