jbi and petals presentation at soa4all architecture meeting

21
Leading Open Source SOA SOA4ALL WP1 meeting 13-14 May PEtALS Enterprise Service Bus Christophe Hamerling PEtALS Product Manager eBM WebSourcing

Upload: christophe-hamerling

Post on 10-Jun-2015

2.462 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: JBI and PEtALS Presentation at SOA4ALL architecture meeting

Leading Open Source SOA

SOA4ALL WP1 meeting 13-14 May

PEtALSEnterprise Service Bus

Christophe HamerlingPEtALS Product Manager

eBM WebSourcing

Page 2: JBI and PEtALS Presentation at SOA4ALL architecture meeting

AGENDA

2SOA4ALL WP1 meeting 13-14 May

• Java Business Integration

• PEtALS, The European Open Source ESB

Page 3: JBI and PEtALS Presentation at SOA4ALL architecture meeting

AGENDA

3SOA4ALL WP1 meeting 13-14 May

• Java Business Integration

• PEtALS, The European Open Source ESB

Page 4: JBI and PEtALS Presentation at SOA4ALL architecture meeting

4SOA4ALL WP1 meeting 13-14 May

JBI : A standard for ESB

• JBI: Java™ Business Integration (JSR 208)– The Java™ standard for SOA implementation– Builds on top of Web Services state of the art

• Defines architecture for integration solution– Based on

• pluggable component• XML messaging

Page 5: JBI and PEtALS Presentation at SOA4ALL architecture meeting

5SOA4ALL WP1 meeting 13-14 May

JBI Environment View

JBI Container

XSLT WS-BPEL EJBContainer

SOAPHTTP

JMSMOM

AS1/AS2EDI

JBI

Components

XS

L

XS

L

XS

LP

rocess

EJB

Process

Process

EJB

EJBExternal Services Artifacts

Page 6: JBI and PEtALS Presentation at SOA4ALL architecture meeting

6SOA4ALL WP1 meeting 13-14 May

JBI Components

• A component :– is installed on the container and interacts with other

components– consumes and/or provides services– match the JBI API– is fully portable = can be installed on any JBI container

• Two types of JBI Components– Service Engine (SE): Provide integration logic,

transformation, content based routing...– Binding Component (BC): provide connectivity to/from

external resources

Page 7: JBI and PEtALS Presentation at SOA4ALL architecture meeting

7SOA4ALL WP1 meeting 13-14 May

JBI modules

• Normalized Message– Pattern (InOnly, Robust InOnly, InOut, InOptOut)– Context (protocol, properties)– XML payload– Attachments

• Delivery Channel– JBI Client access to NMR

• Normalized Message Router– Send/Receive messages to/from components– Responsible for routing messages

• Endpoint– Provide access to the service

• Service Unit / Assembly

Page 8: JBI and PEtALS Presentation at SOA4ALL architecture meeting

SOA4ALL WP1 meeting 13-14 May

AGENDA

8

• Java Business Integration• PEtALS, The European Open

Source ESB

Page 9: JBI and PEtALS Presentation at SOA4ALL architecture meeting

9SOA4ALL WP1 meeting 13-14 May

PEtALS ESB identity card

• Open Source Enterprise Service Bus• Created in June 2005• Hosted by OW2 Consortium• Lead by eBM WebSourcing (FR)• Releases :

– 1.0 reached in September 2006– Version 2.1.1 is SUN certified with JBI TCK– Current version is 2.1.2– 3.0 planned for September 2008

• http://petals.ow2.org

Page 10: JBI and PEtALS Presentation at SOA4ALL architecture meeting

10SOA4ALL WP1 meeting 13-14 May

PEtALS Features

• Distributed JBI Container• Standard based connectivity

– Web Services / REST Services– Mail : POP, IMAP, SMTP– JMS– EJB– FTP– TCP/IP

• Service Engines– XSLT– EIP : Enterprise Integration Pattern– BPEL : Service Orchestration– BPM

Page 11: JBI and PEtALS Presentation at SOA4ALL architecture meeting

11SOA4ALL WP1 meeting 13-14 May

PEtALS Features

• Service infrastructure– Routing (NMR JBI)– Security– Service Level Agreement (Client – Provider QoS)– Monitoring

• Extensible architecture– Based on Fractal Component Model Technology– Software layers/Components

• Delivery Channel• Message router• Message transporter• ...

Page 12: JBI and PEtALS Presentation at SOA4ALL architecture meeting

12SOA4ALL WP1 meeting 13-14 May

PEtALS Distributed Communication

• JBI specification defines a centralized view of the container– Run on one JVM– Connect containers with Binding Components– Distributed aspect is considered as an evolution (JBI

2.0)

JBI Env.

WS

JMS

JBI Env.JMS

JMS

JMS

WS JMS

WS

BusinessServices

BusinessServices

Administration Administration

BusinessServices Business

Services

Page 13: JBI and PEtALS Presentation at SOA4ALL architecture meeting

13SOA4ALL WP1 meeting 13-14 May

PEtALS Distributed Communication

• PEtALS already provides a distributed environment (since v1.0)– Containers are viewed as unified container

• Native communication (no need of Binding Components)

– Centralized administration

CentralizedAdministration

andMonitoring

BusinessServices

BusinessServices

BusinessServices

BusinessServices

JBI Env.

JBI Env.

JBI Env.WS-BPEL XSLT

WS-BPEL

Page 14: JBI and PEtALS Presentation at SOA4ALL architecture meeting

14SOA4ALL WP1 meeting 13-14 May

Component Development Kit

• Ease the development of new JBI components• Contains

– set of abstract component classes– utilities to handle WSDL description, JBI message

contents– mechanism to manage component configuration

(ServiceUnit mgt)

• Components created with this CDK run on other JBI containers (based on JBI API)

Page 15: JBI and PEtALS Presentation at SOA4ALL architecture meeting

15SOA4ALL WP1 meeting 13-14 May

Tools : Configuration

Page 16: JBI and PEtALS Presentation at SOA4ALL architecture meeting

16SOA4ALL WP1 meeting 13-14 May

Tools : Eclipse Developer Plugin

• Wizards– Component– Configuration

• Management– Installation– Deployment

Page 17: JBI and PEtALS Presentation at SOA4ALL architecture meeting

17SOA4ALL WP1 meeting 13-14 May

Tools : WebConsole

• Administrate– Installation– Deployment

• Monitor– Messages– Services– Platform

• Manage errors

Page 18: JBI and PEtALS Presentation at SOA4ALL architecture meeting

18

Installation – Deployment phase

Client Side

Provider Side

BCSOAP

PEtALS

JBI Env

JBI Env

BCSOAP

BCEJB

SEOrchestra

WS Client

WS Provider(SB)

Ejb Container(SA)

Service Assembly

WS

P S

U (S

B)

Ejb

SU

(SA

)

Bp

el S

U (S

C)

WS

C S

U

Page 19: JBI and PEtALS Presentation at SOA4ALL architecture meeting

19

Runtime phase

Client Side

Provider Side

BCSOAP

PEtALS

JBI Env

JBI Env

BCSOAP

BCEJB

SEOrchestra

WS Client

WS Provider(SB)

Ejb Container(SA)

1

2

33

4 4

Page 20: JBI and PEtALS Presentation at SOA4ALL architecture meeting

20

Runtime phase

Client Side

Provider Side

BCSOAP

PEtALS

JBI Env

JBI Env

BCSOAP

BCEJB

SEOrchestra

WS Client

WS Provider(SB)

Ejb Container(SA)

8

7

66

5 5

Page 21: JBI and PEtALS Presentation at SOA4ALL architecture meeting

21

Questions