After Oracle SOA Suite 12.1.3 for developers is installed we can now create our first Service Bus project. Select New Application.
From the Service Bus Tier we can select the Service Bus Application with Service Bus Project.
It seems the OSB 12c project naming was aligned with other JDeveloper projects, and so dropping the old OSB Configuration terminology and use Service Bus Application instead.
The 1st step in the Service Bus Application wizard is to determine our application name, working folder and an application package prefix
Since the Servicew Bus Application needs a Service Project we can now determine our project nme and the working folder for our project:
Our first (empty) project is a fact.
When we look at the result we see that the main part is the SBProject. The layout looks familiary close to the SCA composites we know from the SOA Suite.
However the OSB Proxy Services terminology is still used instead of Exposed Services and Pipelines/Split Joins instead of the SCA Components term
When we look at the Components panel to the right we see that 12c uses pipelines and split-joins to model the service bus project logic.
Besides that a lot of transports and adapters are available to connect to a large scale of backends and technologies.
OId obvious integration friends like HTTP, FTP, File, JMS are there, but also options like REST, UMS, Oracle Coherence and Oracle BAM.
Probably for backwards compatibility Oracle decided to support both the old OSB 11g Business Services transports and better integrate the SOA Suite JCA transports in the designer.
Which again allows us to use 2 default options for the File, JMS and FTP transport.
Looking at the way Oracle decided to arrange the components as they did between Technology and Advanced, it looks like the “default” or “best-practice” transport is located under Technology.
- The Technology panel File and FTP transport pop-up the JCA Adapter wizard, and the HTTP and JMS transport pop-up the Business Service wizard.
- The Advanced panel File and FTP transport pop-up the Business Service wizard, and the JMS transport pop-up the JCA Adapter wizard
Another killer feature is the default integrated Maven support for your projects.
After viewing a demo of a competitors new integration product release recently, which simply stated “there is still no Maven support”, this seems clearly an advantage for Oracle and will help developers and IT organizations to embrace CI more efficiently.