OSB transactions

Question

I'm trying to create simple web service-based proxy service that publishes incoming data ($body) into two JMS queues. What I want to achieve is a transactional behaviour of such a service. I want to enqueue incoming message either in both queues or in none of them.
Proxy service
- is WSDL based
- contains Pipeline Pair node
  - in request pipeline there is Stage
    - Stage contains two Publish actions
      - each Publish action uses different business service
        - business services are messaging services using XA connection factory
      - both Publish actions contains Routing Options with QoS set to Exactly Once
I simulate error using security policy settings on JMS queues. When I forbid access to the first queue only, everything is OK. I receive correct error message (soap fault with Access denied to resource ...) from web service proxy service and the message is not enqueued in the first JMS queue nor in the second one. However, when I forbid access to the second queue only, I still reveice correct error message, but the message is enqueued in the first JMS queue.
I want proxy service to rollback publish actions in case of any error raised during request. Does anybody know how to do it? Any help would be appreciated.
I have to say that the documentation could discuss this problem a little bit more. I didn't find any complex information about transactions in OSB. Only a few bits here and there. So I tried many variations of my proxy and business services. I even tried to split my proxy service into more proxy services according to advice found at http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html
"To have an HTTP proxy service publish to a JMS queue but have the publish action rollback if there is a exception later on in the request processing, split the proxy service into a front-end HTTP proxy service and a back-end JMS proxy service. The publish action specifies a qualityOfService element of exactly-once and uses an XA connection factory."
My environment:
Oracle Service Bus 10gR3
WebLogic 10gR3
2-node cluster
Linux OS
Edited by: hisaak on 11.2.2009 3:42

Answer 1

Juan Luis,
Solution is,
Step1
Create a JMSProxy1(XA/Req-Resp)
RequestQ
ResponseQ
Step2
Create a BS (JMSBS2/ReqOnly) with endpoint URI=ResponseQ (Use correlation ID, and XA connection factory)
1) Create a Proxy (JMS/XA/REQRESP)
2) In the error handler
a) use a publish action configured with BS created in Step2. Use QOS=Best effort so that It doesn't participate in the transaction.
b) After publish using java call out , mark transaction for roll back or use action raise error.
httpProxy---->JMSBS1----(RequestQ)----JMSProxy1(XA/Req-Resp)---In Error handler----Publish to JMSBS2-- raise error(rolls back the transactions)
JMSBS1------<(ResponseQ)---------will receive the message sent by JMSBS2 when there is error in pipeline because we use QOS=BestEffort
JMSBS1------<(ResponseQ)---------will receive the message from the response of JMSProxy1 if no error is raised in pipeline
In both cases we have the response back to the http proxy. By this solution we can rollback the actions but will still get the response no matter.
Only limitation is we should JMS correlation ID for JMSBS1. Read JMS correlation ID from Proxy and use the same Correlation ID in the publish action(JMSBS2) in JMSProxy1.
Let me know if any clarifications are required
Thanks
Manoj