The recent BEA acquisition augments Oracle SOA Suite with BEA's AquaLogic Service Bus (henceforth referred to as the Oracle Service Bus). OSB offers a lightweight Enterprise Service Bus to connect, mediate and manage interactions between heterogeneous services and legacy applications. The go-forward strategy is to offer a unified service bus architecture that combines the respective strengths of the (existing) Oracle Enterprise Service Bus and the (newer) OSB, in addition to providing an automated upgrade path for existing customers.
In this tutorial, we demonstrate some of the core OSB features.
Tutorial overview
The core OSB features showcased are:
- Connectivity, via the ability to access and integrate applications using a standards based approach (SOAP).
- Messaging and Routing: Once connectivity is established, incoming data and messages are routed to their appropriate destination. Routing decisions are usually based on headers, content or other external rules.
Use Case
Incoming loan applications at a financial services company are routed through OSB to determine the appropriate business service to process the application, depending on the applicant’s credit limit.
OSB makes a service callout to JD Edwards Enterprise One to obtain the applicant's credit limit. If the credit limit is <= $100k, the application is routed to the “regular-loan” business service for processing; all other applications are routed to the “jumbo-loan” business service.
The tutorial uses a file system to represent the two business services.
Implementation
The main steps in the process are:
- Generate and publish the WSDL for the JD Edwards web service.
- Implement CBR in the Oracle Service Bus and define the relevant business services: regular-loan and jumbo-loan.
- Implement an OSB service callout to the JD Edwards web service; route the response containing the credit limit using CBR to the appropriate business service.
