Hands-On with Oracle SOA

Hands-On with Oracle SOA

November 14th, 2012

10:30-11:15

Room vt445

Cristian Durca Ahmed Aboulnaga Technical Architect Technical Director

Raastec, Inc. Raastech, Inc.

of 98 © Raastech, Inc. 2012 | All rights reserved.

1. Understanding Oracle Integration Products

2. Our “Integration” Use Case

3. Implementing the Solution

4. Summary

Agenda


UNDERSTANDING ORACLE INTEGRATION PRODUCTS


Oracle Fusion Middleware



Oracle Fusion Apps

Oracle E-Business Suite

Oracle JD Edwards

Oracle PeopleSoft

Oracle Siebel

Oracle Retail

More…



Oracle Database

Oracle MySQL



Oracle Enterprise Linux

Oracle Solaris

Oracle VM

Oracle Exadata/Exalogic

Oracle SPARC

Oracle Storage Products


Oracle SOA Suite

Oracle Service Bus (OSB)

Oracle Data Integrator (ODI)

Oracle Web Services Manager (OWSM)

Oracle Application Integration Architecture (AIA)

Oracle Business Activity Monitoring (BAM)

Oracle GoldenGate

Oracle Enterprise Repository (OER)

Oracle Enterprise Gateway (OEG)

Oracle Service Registry (OSR)

Oracle B2B Integration

Oracle Integration Products


Transforms complex architectures into agile integration

networks by connecting, mediating, and managing

interactions between services and applications

Delivers low-cost, standards-based integration for mission

critical SOA environments where extreme performance

and scalability are requirements


A comprehensive and easy-to-use solution for policy

management and security of service infrastructure

Provides visibility and control of the policies through a

centralized administration interface offered by Oracle

Enterprise Manager


A comprehensive, hot-pluggable software suite to build,

deploy and manage Service-Oriented Architectures

(SOA)

Unified application development tooling and end-to-end

lifecycle management


Gives business executives the ability to monitor their

business services and processes in the enterprise

Correlate KPIs down to the actual business process

themselves

Allows the ability to change business processes quickly or

to take corrective action if the business environment

changes


OUR “INTEGRATION” USE CASE


High Level Flow of Use Case

Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


Consider using OSB as your entry (and/or exit) points

OSB is lightweight, and easily supports throttling and caching

OSB proxy services are usually exposed as web services

Why OSB?

Web Application

OSB Proxy Service

Mobile Application

OSB Proxy Service

OSB Proxy Service

OSB Proxy Service


<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<wsse:Security soap:mustUnderstand="1">

<wsse:UsernameToken>

<wsse:Username>myusername</wsse:Username>

<wsse:Password>mypassword</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

</soap:Header>

Install the Oracle Service Bus OWSM Extension to provide

support for WS-Security

Attach the policy “oracle/wss_username_token_service_policy”

Client must supply username and password in the SOAP

header

Why OWSM?

OSB Proxy Service

OWSM Policy


Incoming payload includes:

Item Number

Quantity

Dollar Amount

Type Flag (‘M’ for mobile, ‘W’ for web)

Use BPEL for complicated flows and/or orchestration

(e.g., calculate tax)

Use Mediator to route to the correct table based on the flag

in the payload

Why SOA Suite?

SOA Suite Composite

BPEL

(calculate tax)

Mediator

(route)


BAM is essentially a reporting tool

Designed to capture in-flight transactions and report on

them in real-time

Does not impact performance of integration flow

In our use case, publish total dollar amounts of web

orders to BAM for management reporting

Why BAM?

SOA Suite Composite

BAM Reports


Bringing it all together…

Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy

The Oracle Integration Layer


IMPLEMENTING THE SOLUTION


Create the Order.xsd schema file

An XML schema describes the structure of an XML message

Create XML Schema

<?xml version="1.0" encoding="ISO-8859-1" ?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="Order">

<xs:complexType>

<xs:sequence>

<xs:element name="OrderType" type="xs:string"/>

<xs:element name="ItemNumber" type="xs:string"/>

<xs:element name="Quantity" type="xs:positiveInteger"/>

<xs:element name="Price" type="xs:decimal"/>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:schema>


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


These tables represent the backend for our order system

Create the backend database tables

CREATE TABLE web_orders (

item_number VARCHAR2(10),

quantity NUMBER,

dollar_amount NUMBER(7,2)

);

CREATE TABLE mobile_orders (

item_number VARCHAR2(10),

quantity NUMBER,

dollar_amount NUMBER(7,2)

);


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


BAM Data Objects are essentially tables

Used to store data that is published to BAM

Create the BAM Data Objects


Create the BAM Data Objects


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


BAM Data Object

SOA Suite Composite

BPEL

(calculate tax)

Mediator

(route)

WebOrders Table

MobileOrders Table Price x 1.05

OrderType = ‘W’

OrderType = ‘M’


A SOA composite application can consist of multiple

components, such as:

BPEL component

Mediator component

Database Adapters

BAM Adapter

Open up JDeveloper 11g

Create a new SOA project

Create SOA composite


Create a SOA project


Adapters are used for easily referencing technologies

such as databases, file systems, FTP servers, JMS, and

so forth

The Database Adapter hides the underlying

implementation of the connectivity of the database, so

that the SOA developer can focus on building

integrations

Simply drag the Database Adapter to the external

references pane

Create Database Adapters for each table


Drag Database Adapter to pane


Use Database Adapter configuration wizard

Provide a name for the reference


Choose a database to connect to


Select table and columns

Select the table name and columns from the database


Select type of operation on this table


Database Adapters created in JDeveloper


Create a Mediator component

Mediator’s strengths are in transformation and routing

Route to the Database Adapters that we just created…

…based on a filter on the ‘OrderType’ flag

Create SOA Mediator component



Create a name for the Mediator component



Use the XSD we created earlier as our message input


Create a WSDL for the Mediator component


Create a routing rule


Select the Database Adapter

Select the Database Adapter we had created earlier


Create a filter expression


Create a transformation


Map the XML to the Database Adapter object


How the composite looks like so far


BPEL is used for orchestration or complicated logic

Simply drag the “BPEL Process” to the composite pane

Create SOA BPEL component


Create SOA BPEL component


Link the BPEL to the Mediator


Create an ‘Assign’ activity


Multiply the price


Map rest of BPEL elements to Mediator object


Create an ‘Assign’ activity for the response


Similar to the Database Adapter, drag the BAM Adapter

Will query the BAM server and list all available data objects

Create BAM Adapter


Create BAM Adapter


Map BPEL object to BAM object


How the final SOA composite looks like


Deploy SOA composite

Right-click on the composite name to deploy to SOA server

URL becomes:

http://soadev:8001/soa-infra/services/default/ProcessOrder/calculatetax_client_ep?WSDL


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


OWSM Policy

OSB Project

Proxy

Service

Business

Service

http://soadev:8001/soa-infra/... http://soadev:7001/ProcessOrderProxy/...

SOA Composite


The OSB server is on a separate managed server

Import the WSDL of the SOA composite

Create a Business Service (the link to the SOA composite)

Create a Proxy Service (the exposed interface)

Secure the Proxy Service with an OWSM Policy

Create OSB project


Create OSB project


Import the SOA composite WSDL


Create OSB Business Service


Create OSB Proxy Service


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


Click on Proxy Service


Attach OWSM Policy to OSB Proxy Service


To identify exposed URL


The exposed WSDL for the OSB Proxy Service:

http://soadev:7001/ProcessOrderProxy/ProcessOrderPS?wsdl

This is the WSDL that the web/client applications will invoke

Final OSB exposed WSDL


Web Application

OSB Proxy Service

Mobile Application

SOA Suite Composite

Database Table 1

& Table 2

BAM Reports

OWSM Policy


Use soapUI to test the WSDL

Test with soapUI


Observe authentication failure

Seems to be some security error

Valid error… no username/password provided in payload!


Test with security token in SOAP header

With authentication info in header, we get our ‘Done’ response


Observe instance in EM Console


Clicking on the instance ID shows a successful flow

Data only inserted to the ‘WebOrders’ table as expected

View instance flow


View Mediator instance details


Querying the database table confirms this

Confirm data in database


Data also published to BAM!

Can now create a report to query this Data Object

Confirm data in BAM Data Object


SUMMARY


1. Create an XML Schema

2. Create the database tables

3. Create the BAM Data Object

Summary


4. Create the SOA composite with JDeveloper

a. Open up JDeveloper 11g

b. Create a SOA project

c. Create 2 Database Adapter services

d. Create a Mediator component i. Create a web service interface using the XSD file

ii. Create 2 routing rules to the 2 database services

iii. Use a filter expression on the 'OrderType' element

e. Create a BPEL component i. Link the BPEL component with the Mediator component

ii. Map the input of the BPEL to the input of the Mediator

iii. But multiple the price by 1.05

iv. Create a BAM Adapter to the BAM Data Object

v. Map the input of the BPEL to the BAM Adapter

Summary


5. Deploy the SOA composite

a. Get the WSDL of the SOA composite

6. Create an OSB project

a. Create a Business Service using this SOA WSDL

b. Create a Proxy Service as the OSB interface

c. Secure the Proxy Service with an OWSM Policy

7. Test using soapUI

Summary


Understand where each product should be aligned

There is some overlap between products

There is no one-size fits all architecture

Understand the difference between and usage of OSB,

OWSM, BAM, and SOA Suite

Observe first hand a walkthrough demo:

OSB used as a passthrough, but has other benefits not demo’ed here

OWSM provides a mechanism to attach security policies to a service

BPEL used for orchestration

Mediator used for routing

Take Aways


All these products are provided as part of a single Oracle

SOA Suite license, so take advantage of them!

You can use any combination of OSB, BPEL, or Mediator

depending on your needs

Final Thoughts


Contact Information

Cristian Durca

Technical Architect

[email protected]

Ahmed Aboulnaga

Technical Director

[email protected]

Hands-On with Oracle SOA

Technology

Transcript of Hands-On with Oracle SOA