2. Installation and Configuration Guide
3. Tutorial 1: First spin - Getting to know Oracle Service Bus by exposing a simple service
4. Tutorial 2: New adapters
5. Tutorial 3: Data enrichment
This article is aimed at developers and architects who are familiar with Oracle Enterprise Service Bus (OESB) and are (fairly) new to Oracle Service Bus (OSB). The tutorials in this article highlight differences between these two products. The tutorials are based on a workshop in the WAAI community; a collaboration of Dutch consultancies (Whitehorses, Approach, AMIS, and IT-Eye). The goal of the WAAI collaboration is to share, bundle, and expand knowledge on the recent Fusion Middleware 11g release.
When it comes to choices within Oracle's SOA product portfolio, life seemed to be somewhat easier a few years ago. When you needed service bus functionality, you choose Oracle's Enterprise Service Bus. Two things caused a shift that resulted in a richer and better set of ESB-like products: the acquisition of BEA, including its AquaLogic Service Bus (ALSB) product; and the evolution to Service Component Architecture (SCA) in SOA Suite 11g, which includes the Mediator component. These changes also made the choice for the "right bus" somewhat more difficult.
With the release of the last generation of Fusion Middleware 11g the smoke has somewhat cleared. ALSB has been rebranded as Oracle Service Bus (OSB) and is enriched with some of the functionality from Oracle ESB — JCA as transport protocol, an improved adapter offering including the AQ and Database adapter, and transformation capabilities based on XSLT — thus providing the best of both worlds. In Oracle's go-forward strategy, OSB is the strategic ESB product. The routing and transformation capabilities previously offered by Oracle ESB have been migrated to the Mediator component of SOA Suite 11g. Mediator is one of the many SCA components that can be assembled into service composites.
Depending on your needs and environment, there are two options for migration from Oracle ESB to this new Oracle infrastructure:
* You only need bus-like functionality. Choose OSB since it is the better product compared to OESB and it is strategic to Oracle. You will need to migrate OESB flows to OSB projects.
* You need a complete SOA-stack including service orchestration capabilities and possibly business rules, support for human activities, and so on. The best choice in this case is moving to SCA. Existing OESB flows providing routing and transformation capabilities migrate to Mediator components within a SCA composite — which can be done automatically by opening ESB projects in JDeveloper 11g — while OESB flows that connect your environment to the outside world should be migrated to OSB.
The tutorials in this article are based on building OSB projects from scratch, not on migration from other or previous products to OSB. Let's move on to the tutorials. First we need to install and configure Oracle Service Bus.