Top Banner
Oracle SOA Workshop (11.1.14.0) Lab Overview Lab Guide
4
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: second file

Oracle SOA Workshop(11.1.14.0)Lab Overview

Lab Guide

Page 2: second file
Page 3: second file

OverviewIn this SOA workshop, you will be building the bus layer and business rule / human task inSOA that are used for this PR application.

The PR application can be submitted from online web application and/or offline application.The online web application will submit the PR application via web service to OSB. Theoffline PR application will save the content as text file which will be transferred to a fixedlocation on server. OSB will read from that fixed location periodically to process theapplication.

The bus layer will handle all the calling of web services from Oracle SOA and web servicedeployed on the server, which include the message orchestration for PR application.

The flow of PR application at service bus will be as follow:

1. As mentioned above, the PR application can be submitted from the followinga. A web application will send a request to this bus layer through web service.b. Offline PR application is saved as text file onto server and OSB will pick up

the file periodically for processing.2. Once OSB receives the request, it will get the credit rating of the applicant. The credit

rating service is actually a web services residing somewhere else.3. After which, it will invoke the business rule defined in SOA to check if there is a need

to route for approval.4. If approval is required, OSB will trigger the human task via a BPEL process. The

task will be sent to users with manager role.

OSB

Web serviceFile protocol

SOA Suite (Biz Rules, Human Task, etc)

Page 4: second file

Below is the logical architecture of the PR Application’s service bus layer.

The use of a bus layer has a lot of benefits:1. Applications and services connect once to the bus. This results in unlimited

scalability since it eliminates the problem of every service trying to connect to everyother service.

2. Services are truly loosely coupled. Application developers need not worry aboutintegration logic, since it is completely separate and delegated to the OSB. Soservices can be completely heterogeneous and loosely coupled. Integrationdesigners configure integration rules in the OSB which are invoked at run-time todetermine what data and security transformations to use, which route or sequence ofservices to invoke. IT environments are rarely static and change with the needs ofthe business. With an OSB, integration logic can be reconfigured on the fly withoutaffecting the applications.

3. The OSB also provides a repository of services and their policies. In this way,services can be discovered and reused, with the OSB dynamically enforcing theservice’s interoperability and security policies.

4. All services connected to the bus can be centrally managed. For example, SLAthresholds for availability, performance and other measures can be set. Alerts can begenerated for any SLA variances or other issues needing attention.

OSB

Proxy Services

Credit Rating PS

PR Application PS

Read Batch File PS

Business Services

CR for SalariedApplication BS

CR for Self-EmployedApplication BS

Route Rule BS

PR Approval Task BS

Resources

CR for SalariedApplication WSDL

CR for Self-EmployedApplication WSDL

XQuery & MFL

Route Rule WSDL

PR Approval TaskWSDL

Oracle SO

A