Eclipse Con2009 Practical Process Orchestration

Practical Process Orchestration using Eclipse SOA | © 2009 by SOPERA ; made available under the EPL v1.0

Practical Process Orchestration using Eclipse SOA

Dr. Dietmar Wolz

2 Practical Process Orchestration using Eclipse SOA | © 2009 by SOPERA ; made available under the EPL v1.0

Agenda

Introduction

Process Orchestration in Swordfish

Sample scenario

Eclipse BPEL Editor

Demo


Agenda

Introduction


Sample scenario

Eclipse BPEL Editor

Demo


What is Swordfish?

Swordfish is the codename of the Eclipse SOA Runtime Framework Project (under the Runtime top level project)

Mission: Create a flexible and modular SOA runtime framework that can be complemented by other components – both open source and commercial – to create a full-fledged Enterprise Service Bus.

Swordfish builds upon existing proven open source SOA technology and extends it with enterprise features such as service registry integration, remote configuration and monitoring capabilities.


Swordfish builds upon proven open source ESB technology, extending it with enterprise features

.


How to implement Services in Swordfish?

Swordfish is a framework – there's no single way to implement services with Swordfish

The options currently available include: BPEL (requires the Apache ODE BPEL Engine to be installed as a plugin)

Java using JAX-WS (requires Apache CXF to be installed as a plugin)

Java using low-level JBI APIs

Swordfish is based on Equinox, so everything you deploy into Swordfish must be packaged into an OSGi bundle.


Agenda

Introduction


Sample scenario

Eclipse BPEL Editor

Demo


Composite Services in Swordfish


Why to use BPEL?

Industry standard language for expressing business processes

Business services can be designed to be process-agnostic

The BPEL process manages and coordinates the state

Designed to fit naturally into the Web services stack

Uses and extends WSDL 1.1

Expressed entirely in XML

Provides and consumes Web services in an abstract way, using WSDL to define service interfaces


BPEL features

Parallel processing

Delayed execution - persisting process state

Concurrent/selective event processing

Asynchronous execution

Message correlation

Data manipulation - XPath based

Data validation

Scoped error handling / compensation handlers

Dynamic Endpoint Resolution

Extendable - for example XSLT transformations


Swordfish features (will be extended)

Events / Monitoring The Swordfish Event API builds upon the OSGi EventAdmin Service

Configuration (local/remotely) The Configuration API builds upon the OSGi ConfigurationAdmin service

A ConfigurationAgent receives configurations from a ConfigurationSource (possibly a remote one) and provides them to other components through the OSGi Configuration Admin service

A component that implements ConfigurationConsumer receives updated configurations as they become available

Dynamic Endpoint Resolution / Service Discovery The Service Resolver API builds upon the general interceptor API

The ServiceResolverInterceptor is reponsible for translating the (logical) service interface name carried inside a message exchange into a physical endpoint


Dynamic Service Discovery


Process-Tooling

Eclipse BPELEditor

Apache ODEJBI Service Unit

ServiceRegistry/

File SystemService Discovery/

WSDL Import

Deployment


Swordfish-Tooling


BPEL Editor for Ganymede/Gallileo- check the Swordfish Wiki

http://wiki.eclipse.org/Swordfish_Documentation:_Installing_BPEL_Editor_in_Ganymede


BPEL – WSDL - PartnerLinks

BPEL-Process

abstractWSDLinbound

abstractWSDLoutbound

PartnerLinkinbound

PartnerLinkoutbound

import

ProcessConsumer

ServiceProviderinvokescalls


Process Execution

ProcessConsumer

ServiceProvider

invokes

calls

BPEL-Process

replies

ProcessExecution


Standard JBI deployment

Inboundhttp-binding

JBI Service Unit

NMRinternal

endpoints


Outboundhttp-binding

JBI Service Unit

externalendpoints

Swordfish/SMIX 4


Alternative deployment

Inboundhttp-binding

JBI Service Unit

NMRinternal

endpoints


SwordfishServiceResolverInterceptor

externalendpoints

Swordfish/SMIX 4


Agenda

Introduction


Sample scenario

Eclipse BPEL Editor

Demo


Flight Reservation Service Process

Reservation ServiceBPEL-Process

WSDLReservation

WSDLStorage

PartnerLinkReservation

PartnerLinkStorage

import

ReservationServiceConsumer

ReservationStorageServiceProvider

invokescalls


Flight Reservation Service WSDLs

invokes


Physical Endpoints are not specified in the Process Description

Physical Endpoints are either defined in the http-binding SU or are provided dynamically by the

Swordfish Service Resolver Interceptor


Agenda

Introduction


Sample scenario

Eclipse BPEL Editor

Demo


The Reservation Process in the BPEL Editor


The BPEL source view


The missing view

missing: a (really) human readable process DSL

Intalio developed such a DSL called SimPEL

a SimPEL compiler translates SimPEL code into BPEL

Disadvantage: textual representation is not standardized


Import a WSDL


Receive the Process Parameters


The providerRequest Variable


The providerResponse Variable


The consumerRequest Variable


The consumerResponse Variable


The Inbound PartnerLink


The Outbound PartnerLink


Assigning Data


Invoke an External Web Service


Deployment to Apache ODE


Customizing ODE log output


Debugging / Tracing service calls

Tracing outgoing service calls using httptracer


Agenda

Introduction


Sample scenario

Eclipse BPEL Editor

Demo

Eclipse Con2009 Practical Process Orchestration

Technology

Transcript of Eclipse Con2009 Practical Process Orchestration