SOA using OpenESB, BPEL, JBI, GlassFish and NetBeans

Sang Shin Java Technology Architect Sun Microsystems, Inc. javapassion.com

1

Agenda
Composite Application BPEL JBI JBI and GlassFish OpenESB Java EE Service Engine Intelligent Event Processor

Composite Applications

Traditional Application Development

Point technologies, products, and APIs
> For example: EJB, Spring, Hibernate, JSF, Servlets, Struts,

etc.

Lots of glue written by developers

> Requires a great deal of expertise & time > Inflexible

Composite Applications
A way to compose applications from reusable parts Composite applications employ SOA principles
> Features exposed as Web services > Standards-based interaction between services > Are themselves compose'able

WSDL Tutorial (Optional Presentation)

Why WSDL?
Enables automation of communication details between communicating partners
Machines can read WSDL Machines can invoke a service defined in WSDL

Discoverable through registry Arbitration

3rd party can verify if communication conforms to WSDL
7

WSDL Document Example

Simple service providing stock quotes A single operation called GetLastTradePrice Deployed using SOAP 1.1 over HTTP Request takes a ticker symbol of type string Response returns price as a float
8

WSDL Elements

Types Message Operation Port Type Binding Port Service

9

WSDL Elements

Types

Data type definitions Used to describe exchanged messages Uses W3C XML Schema as canonical type system

10

WSDL Example: Types

<definitions name="StockQuote" targetNamespace="http://example.com/stockquote.wsdl" xmlns:tns="http://example.com/stockquote.wsdl" xmlns:xsd1="http://example.com/stockquote.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/> <types> <schema targetNamespace="http://example.com/stockquote.xsd" xmlns="http://www.w3.org/2000/10/XMLSchema"> <element name="TradePriceRequest"> <complexType> <all> <element name=tickerSymbol" type="string"/> </all> </complexType> </element> <element name="TradePrice"> <complexType> <all> <element name="price" type="float"/> </all> </complexType> </element> </schema> </types>

11

WSDL Elements

Messages

Abstract, typed definitions of data being exchanged Abstract description of an action Refers to an input and/or output messages Collection of operations Abstract definition of a service
12

Operations

Port type

Example: Messages, Operation, Port type

<message name="GetLastTradePriceInput"> <part name="body" element="xsd1:TradePriceRequest"/> </message> <message name="GetLastTradePriceOutput"> <part name="body" element="xsd1:TradePrice"/> </message> <portType name="StockQuotePortType"> <operation name="GetLastTradePrice"> <input message="tns:GetLastTradePriceInput"/> <output message="tns:GetLastTradePriceOutput"/> </operation> <!-- More operations --> </portType>
13

WSDL Elements

Binding

Concrete protocol and data format (encoding) for a particular Port type

Protocol examples: SOAP 1.1 over HTTP or SOAP 1.1 over SMTP Encoding examples: SOAP encoding, RDF encoding

Port

Defines a single communication endpoint Endpoint address for binding URL for HTTP, email address for SMTP Aggregate set of related ports
14

Service

Example: Binding, Port, Service

<binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="GetLastTradePrice"> <soap:operation soapAction="http://example.com/GetLastTradePrice"/> <input> <soap:body use="literal" /> </input> <output> <soap:body use="literal" /> </output> </operation> </binding> <service name="StockQuoteService"> <documentation>My first service</documentation> <port name="StockQuotePort" binding="tns:StockQuoteSoapBinding"> <soap:address location="http://example.com/stockquote"/> </port> </service>

15

BPEL

Need for Business Process

Developing the web services and exposing the functionality (via WSDL) is not sufficient Example Scenario
> Concert ticket purchase Web service has 3 operations,

which need to be performed in the following order > Getting a price quote > Purchase a ticket > Confirmation and cancellation

We also need a way to orchestrate these functionality in the right order

17

BPEL Works With WSDL

Web services are described in WSDL We need a way to orchestrate these operations with multiple web services in the right order to perform a Business process
> Sequencing, conditional behavior etc.

BPEL provides standard-based orchestration of these operations

18

BPEL: Relationship to Partners

WSDL

Partner Servic

Partner Servic Partner Service Orchestrating Process (BPEL)

Partner Servic
19

Business Process Needs To...

Co-ordinate asynchronous Manipulate/transform communication between data between partner services interactions Correlate message Support for long running exchanges between business transactions parties and activities Implement parallel Handle exception processing of activities handling Implement compensation logic (Undo operations)
20

BPEL Document Structure

<process>
<! Definition and roles of process participants --> <partnerLinks> ... </partnerLinks> <!- Data/state used within the process --> <variables> ... </variables> <!- Properties that enable conversations --> <correlationSets> ... </correlationSets> <!- Exception handling --> <faultHandlers> ... </faultHandlers> <!- Error recovery undoing actions --> <compensationHandlers> ... </compensationHandlers> <!- Concurrent events with process itself --> <eventHandlers> ... </eventHandlers> <!- Business process flow --> (activities)* </process> 21

BPEL Activities
Basic Activities <invoke> <receive> <reply> <assign> <throw> <wait> <empty> <exit> Structured Activities <if> <while> <repeatUntil> <foreach> <pick> <flow> <sequence> <scope>
22

BPEL: Basic Activities

<invoke>
> To invoke a one-way or request/response operation on a

portType offered by a partner

<receive>
> To do a blocking wait for a matching message to arrive > Can be the instantiator of the business process

<reply>
> To send a message in reply to a message that was received

through a <receive> > The combination of a <receive> and a <reply> forms a request-response operation on the WSDL portType for the process

23

BPEL: Structured Activities

<sequence>
> Perform activities in sequential order

<flow>
> Perform activities in parallel

<if>
> Conditional choice of activities

<scope>
> Enclose multiple activities in a single scope
24

Example Business Process

Receive <PO> <sequence>

Invoke <InventoryService>

Invoke <CreditService>

<flow>

Reply <Invoice>

</sequence>

25

Sample Activities in BPEL

<sequence> <receive partnerLink=customer portType=lns:purchaseOrderPT" operation=sendPurchaseOrder variable=PO createInstance="yes" /> <flow> <invoke partnerLink=inventoryChecker portType=lns:inventoryPT operation="checkINV" inputVariable="inventoryRequest" outputVariable="inventoryResponse" /> <invoke partnerLink="creditChecker" portType=lns:creditPT" operation="checkCRED" inputVariable="creditRequest" outputVariable="creditResponse" /> </flow> ... <reply partnerLink=customer portType=lns:purchaseOrderPT operation=sendPurchaseOrder variable=invoice"/> </sequence>

26

BPEL: Relationship to Partners

WSDL

Inventory Checker Service

Credit checker Service

Customer Service Orchestrating Process (BPEL)

Another Partner Service

27

Why Do You Care on BPEL?

In SOA-enabled environment, you are more likely to build an application by orchestration various services via BPEL You will probably use BPEL design tool to create a BPEL document The BPEL document is then executed by BPEL engine
> Highly likely in JBI enabled platform

28

Building Travel Reservation Composite Application (Demo Scenario Next Slide)

http://www.netbeans.org/kb/60/ep-understand-trs.html

Demo:

29

Demo Scenario: Travel Reservation Business Process

It receives travel reservation request from its client
> The request contains travel reservation request XML

document based on OTA (Open Travel Association)

It then performs travel reservation business process talking to three partner web services
> Airline reservation partner web service > Hotel reservation partner web service > Vehicle reservation partner web service

The three partner web services are implemented as EJB based web services
30

Demo Scenario
See Travel Reservation business process as a BPEL document See WSDL documents of partner web services and of the BPEL process web service Build and deploy the application over GlassFish and JBI server Test the application with test requests Perform source-code debugging on BPEL

31

Services and SOA

What Are Services?

Black-box components with well-defined interfaces
> Performs some arbitrary function > Can be implemented in myriad ways

Accessed using XML message exchanges

> Using well-known message exchange patterns (MEPs)

Metadata in the form of WSDL describes...

> Abstract interfaces > Concrete endpoints

33

What Can Services Do?

Perform business logic Transform data Route messages Query databases Apply business policy Handle business exceptions Prepare information for use by a user interface Orchestrate conversations between multiple services
34

How Are Services Implemented?

Enterprise JavaBeans (EJB ) technology BPEL XSLT SQL Business rules Mainframe transaction EDI transform Humans (yes, really!)
35

Example: Purchase Service

Bid Request Bid Request

Lowest Bid

Bid
Purchase Service

Buyer Accept/ Reject

Supplier Accept/ Reject

Ship Notice

Ship Notice

36

Purchase Service Functions

Buyer Endpoint Supplier Endpoint

Buyer Conversation

Supplier Conversation

Transaction Fees Supplier Routing Supplier Selection Buyer Credit Product Conversion

37

Purchase Service Functions

WS Buyer DL /S o Endpoi a p nt
Buyer BP EL Conversatio n

WS Supplie DL r /Soa Endpoi p

nt Supplier BP EL Conversati on

EJ Transaction Fees B XQ Supplie ue r ry

Selecti on

ting Supplier Routing T able

Ru Buyerle Credit
Product XS LT Conversion

Ro u

38

Service Oriented Architecture (SOA)

An architectural principle for structuring systems into coarse-grained services Technology-neutral best practice Emphasizes the loose coupling of services New services are created from existing ones in a synergistic fashion Strong service definitions are critical Services can be re-composed when business requirements change
39

Service Implementation over JBI

What Is JBI?
JBI provides a standard application integration framework JBI to Application integration is what Java EE is to Enterprise application

41

Why JBI?
Point-to-point integration model is not scalable and hard to maintain The traditional EAI model has its problems > Proprietary integration server > Vendor lock-in > High barrier for entry for small, independent, innovative ISV's providing best-of-breed solutions There is a need for an open standard framework for application integration
42

What Is JBI?
Standard meta-container for integrating service containers
> Service containers can host

any services (service units) > Business logic service > System services > Service can be located locally or remotely

Plug-in architecture
> Service Engines (SE) Local

service or consumer > Binding Components Remote service or consumer

43

Service Provider Self-Description

Orchestration (BPEL)
WSDL

Transformation (XSLT)
WSDL

Service containers register the services they provide

J2EE Platform
WSDL

Normalized Message Router

JBI Core Services

WSDL

WSDL

WSDL

WS-I Basic SOAP

AS2

JMS

J2EE Platform
44

System Management

Java Business Integration (JSR 208)

WS D So L/ ap

XQuery
WS D So L/ ap

Install

BP EL EJ B XQ ue ry Ru le

BP EL
Ro u Ta ting ble

Rules

Process

JavaEE

Deploy

NMR AS2 Soap JBI Route MOM

XS LT

Composite Service

45

OpenESB

What is Project OpenESB?

Project OpenESB implements an Enterprise Service Bus (ESB) runtime using Java Business Integration (JBI) as the foundation > This allows easy integration of web services to create loosely coupled enterprise class composite applications. It also provides various tools for the development, deployment, and management of composite applications

47

OpenESB Architecture

48

Design-Time IDE
App Server
Java EE EJBs Servlets

Runtime

Management Web Server

Composite Application Project

BPEL SE Java EE SE HTTP BC

XSLT SE

FTP Many More BC SEs

JBI Bus
FTP BC FTP Many More BC BCs

Composite Application Manager

BPEL Editor
Open Standard Based Service Bus

3rd Party Service Platforms

BPEL Monitor

XSLT Editor

WS-Reliable Messaging WS-Security WS-FastInfoSet,

3rd Party Service Platforms

XSLT Monitor

App Server

IEP Editor

Java EE EJBs Servlets

HTTP BC Java EE SE BPEL SE

FTP BC

FTP Many More BC BCs

IEP Monitor Many More Many More Editors Monitors

Many More Many More Editors Editors

JBI Bus
XSLT SE FTP Many More BC SEs

49

JBI and GlassFish

JBI Support in GlassFish

A JBI runtime has been integrated with GlassFish V2 GlassFish admin console now supports JBI Java EE Service Engine act as the bridge between Java EE applications and JBI A Java EE application archive (ear/war/jar) can be packaged in a JBI composite application JBI runtime has been enhanced to adhere to the appserver clustering architecture
> Each instance in the app server cluster will also have a JBI

runtime in it

51

JBI in Admin Console

52

Usage Scenario

Usage Scenario: Loan Processing

Loan Requestor Service:
> LoanRequestProcess > WS-I BP > BPEL Orchestration > LoanProcessor > JavaEE > TransformReport > XSLT > LoanReportStore > Business Partner thru FTP > LoanReportMailer > Legacy thru JMS
54

JBI-based Infrastructure BPEL JavaEE XSLT

NMR WS-I BP JMS File

55

JBI-based Infrastructure

BPEL Loan Request Process

JavaEE Loan Processor EJB NMR

XSLT Transform Report

File WS-I BP JMS LoanRS WS ReportMail ReportStore

56

BPEL Loan Request Process

JavaEE Loan Processor EJB NMR

XSLT Transform Report

JMS File WS-I BP LoanRS WS ReportMail ReportStore

57

Architecture Refactoring

BPEL Loan Request Service

XSLT Transform Report

JavaEE Loan Processor EJB

NMR JMS File WS-I BP LoanRS WS ReportMail ReportStore

58

BPEL Loan Request Service

XSLT Transform Report

RulesEngine

JavaEE

Loan ReportStore Processor

NMR JMS JMS WS-I BP LoanRS Q LoanRS WS ReportMail File

59

Service Engines (SE) & Binding Components (BC)

JBI Components
Service Engines Binding Comps Other
> > > > > > >

BPEL SE XSLT SE JavaEE SE IEP SE ETL SE SQL SE Workflow SE

> > > > > > > > > > >

MQSeries BC HL7 BC SAP BC SMTP BC HTTP BC JMS BC File BC CICS BC DCOM BC CORBA BC ...

> > > >

Clustering CASA JBI Mock WSIT Tech CAM Aspect SE Encoding SE Rules SE Scripting SE
61

In Progress
> > > > >

open-esb.dev.java.net/Components.html

62

OpenESB Package Ships Many SE's/BC's

63

NetBeans Support of OpenESB

Types of SOA NetBeans Projects

When creating a composite application, you typically use the following types of SOA NetBeans projects:
> > > > > > > > >

BPEL Module project XSLT Module project SQL Module project Composite Application project IEP Module project Worklist Module project ETL (Extract, Transform, and Load) EDM (Enterprise Data Mashup) And more
65

Types of SOA NetBeans Projects

66

BPEL Module Project

BPEL Module project is a group of source files which includes
> XML Schema (*.xsd) files > WSDL files > BPEL files

Within a BPEL Module project, you can author a business process compliant with the WS-BPEL 2.0 language specification. Will be added to a Composite application as a JBI module
67

Composite Application Project

Composite Application project is a project whose primary purpose is to assemble a deployment unit for the Java Business Integration (JBI) server
> BPEL Module projects must be added to a Composite

Application project in order to be deployed to the BPEL runtime.

The Composite Application Project can also be used to create and execute test cases that can then be run, in JUnit fashion, against the deployed BPEL processes.
68

Composite Application Project

With a Composite Application project, you can:
> Assemble an application that uses multiple project types > > > >

(BPEL, XSLT, IEP, SQL, etc.) Configure external/edge access protocols (SOAP, JMS, SMTP, and others) Build JBI deployment packages Deploy the application image to the target JBI server Monitor the status of JBI server components and applications

69

Lots of Step by Step Tutorials

http://www.netbeans.org/kb/60/ep-index.html

70

Building Hello World Composite Application

www.javapassion.com/handsonlabs/wscompositeapps/

Demo:

71

Java EE SE

JavaEE SE
Ideal place to execute complex business logic Bridge between JavaEE container and JBI container Provides support for
> Transactions > Resource Pooling > Security

Code re-use Invoke your EJBs/web applications from OpenESB components (BPEL SE) Ability to expose your EJB/Web applications to multiple transports (using BCs) just add bindings to your WSDL
73

Scenario 1: Remote throughHTTP BC

BPEL NMR HTTP BC Marshall DOM to <xml> SOAP/HTTP Network layer
JBI Container
HTTP

BPEL SE
WSD L WSD L BPEL process

HTTP BC

WSDL

HL7

HL7 BC

WSDL

N M R

BPEL process

WSD L WSD L

EE SE
ejb.jar

HTTP

SAP BC

WSDL

RMI application.ear

EE Container
app-a.ear ejb-b.jar

ejb-c.jar

app-c.ear

HTTP RMI

Network layer SOAP/HTTP JAXWS Unmarshal <xml> Create DOM JAXB WS.helloWorld(name) 74

Scenario 2: Local through NMR

BPEL NMR HTTP BC Marshall DOM to <xml> SOAP/HTTP Network layer SOAP/HTTP JAXWS Unmarshal <xml> Create DOM JAXB WS.helloWorld(name)
JBI Container
HTTP BC
WSDL WSD L WSD L

BPEL SE
BPEL process

HTTP

HL7

HL7 BC

WSDL

N M R

BPEL process

WSD L WSD L

EE SE
ejb.jar RMI application.ear

SAP BC

WSDL

Advantages:
> Performance > Transaction propagation > Security context propagation

Likewise: EJB to BPEL

75

Java EE Service Engine: Functions as Bridge between App Server and JBI Runtime Env.

Java EE S.E. As a Bridge

78

Building Loan Processing Composite Application

www.javapassion.com/handsonlabs/wscompositeapps/#Exercise_2 www.javapassion.com/handsonlabs/wscompositeapps/#Exercise_3

Demo:

83

Intelligent Event Processor

Real-life Use Cases of IEP

How many times did Fred login as root for the last 24 hours? How many times is purchase order business process triggered for the last hour? And what is the average execution time? Is a credit card charged for gasoline twice within last one hour? Raise an alert when a stock price jump more than 10% relative to its 1 minute moving average price. Is the number of JMS messages in the broker increasing over time? What changed?

85

Real Time Event Collection and Notification

External Service Consumer /Provider

JBI Containter

Binding Component

Other Service Engines

Normalized Message Router

IEP Service Engine

86

Building IEP Application that Captures Incoming Stock Data Stream

Demo:

87

Summary

Summary
SOA enables flexible and agile enterprise application architecture Services can be created and used using Java EE BPEL is a service orchestration language for creating composite applications Services can be re-implemented using other technologies as long as service interfaces are preserved without changing consumers Java Business Integration (JBI) is the enabling infrastructure
89

SOA using OpenESB, BPEL, JBI, GlassFish and NetBeans

Sang Shin Java Technology Architect Sun Microsystems, Inc. javapassion.com
90