This content has been marked as final. Show 4 replies
OSB is like the name says a 'Service Bus' and the soa suite is a suite of components which can be used to create a service oriented architecture. In this suite there isn't and service bus available for you.
So both products complement each other.
It's true most actions can be done in both the products/suites, but you should see them both in 1 total solution. After that decide what you design in the osb and what you design in the soa suite components.
if you check wikipedia for the definition of a service bus, you will see what the strengths are (or should be), some line virtualization/transformation/routing/etc.
from my point of view i would say, you create your interface on the service bus, keep the flows in the service bus lightweigh, and route to the 'real' services. These could be modelled in the soa suite components, and in there do the business logic
In general, the SOA Suite (BPEL primarily) should be used for the orchestration. Here you decide which services does what, and in which order you do this. Typically you end up with a composite application.
When it comes to routing and transformation between those composites you should use the OSB.
When transport mediation/data enrichment is required OSB is used. OSB is stateless engine, and use cases that require maintaining state of state should use BPEL.
This is an excellent question and it really comes to the purpose of "Oracle Mediator" and OSB/ALSB to basically perform the same function. This might be also a matter of Oracle licensing and the cost of SOA and OSB.