Oracle Service Bus (previously known as Weblogic ALSB) is a light weight messaging component of SOA Suite. In addition to providing basic routing and transformation services, OSB also provides advanced capabilities for service abstraction.
As of version 11.1.1.3, OSB can only run on Weblogic platform. Since it runs in a separate JVM, there is an overhead in communicating with rest of SOA Suite components.
Though OSB is similar to Mediator component at the conceptual level, there are specific scenarios when OSB will be very useful.
OSB has a built-in feature to modify service end point at run time. This would be very useful when virtualizing external services, probably hosted by various partners.
OSB can also be used to throttle services, thus limiting the number of invocations. This can be valuable in meeting client service level agreements as well as preventing services from being swamped.
In other cases, Mediator will offer more benefits since it is available in the same JVM as rest of SCA components.
OSB service invocation overview
OSB service invocation happens through two different layers: proxy service and business service. Proxy service is an entry point for all service invocations. Ideally proxy service should present a canonical interfaces to clients.
Proxy service then routes inbound message through a series of steps (aka pipes). Each step can perform distinct operations such as transformation, enrichment and logging etc., Eventually this message is routed to Business Service which is just a reference to target service. Similarly, output message from business services follows reverse flow through outbound pipeline, proxy service and finally to the client.
Input and output pipe lines are also responsible for transforming data from and to canonical format.
In subsequent lessons, we will explore various features of OSB.
HOW TO DESIGN A PROXY THAT DOES ONLY ERROR HANDLING AND GIVES THE RESPONSE BACK TO MAIN PROXY…
Hello,
I have a many proxy services.Incase of any faults that occur the control goes to errorhandler,here i will call a proxy using service callout where all the error handling is done.
Can anybody suggest me how to design a proxy to handle faults of around 5 types and give the same response back to my original proxy service so that customer can get the errorcode from the original proxy.
I am trying to design it using pipeline pair node….Inside request pipeline i cant put if then and check for any fault code as u must be knowing faults cant be defined inside request pipeline…………..
Thanks and regards,
Aryashree…
In case you are still struggling, you may want to refer to the latest post – http://www.orafmwschool.com/fault-management-oracle-service-bus/.