• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
JBI and PEtALS Presentation at SOA4ALL architecture meeting
 

JBI and PEtALS Presentation at SOA4ALL architecture meeting

on

  • 3,721 views

 

Statistics

Views

Total Views
3,721
Views on SlideShare
3,622
Embed Views
99

Actions

Likes
1
Downloads
54
Comments
0

8 Embeds 99

http://www.ebmwebsourcing.net 28
http://www.ebmwebsourcing.com 27
http://ebmwebsourcing.com 20
http://nicolascaballerosoa.blogspot.ru 14
http://nicolascaballerosoa.blogspot.com 6
http://www.linkedin.com 2
file:// 1
http://nicolascaballerosoa.blogspot.com.es 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    JBI and PEtALS Presentation at SOA4ALL architecture meeting JBI and PEtALS Presentation at SOA4ALL architecture meeting Presentation Transcript

    • PEtALS Enterprise Service Bus Christophe Hamerling PEtALS Product Manager eBM WebSourcing
      • Java Business Integration
      • PEtALS, The European Open Source ESB
      • Java Business Integration
      • PEtALS, The European Open Source ESB
    • 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
    • JBI Environment View JBI Container XSLT WS-BPEL EJB Container SOAP HTTP JMS MOM AS1/AS2 EDI JBI Components External Services Artifacts XSL XSL XSL Process EJB Process Process EJB EJB
    • 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
    • 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
      • Java Business Integration
      • PEtALS, The European Open Source ESB
    • 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
    • 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
    • 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‏
          • ...
    • 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 Business Services Business Services Administration Administration Business Services Business Services
    • 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
      Centralized Administration and Monitoring Business Services Business Services Business Services Business Services JBI Env. JBI Env. JBI Env. WS-BPEL XSLT WS-BPEL
    • 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)‏
    • Tools : Configuration
    • Tools : Eclipse Developer Plugin
      • Wizards
        • Component
        • Configuration
      • Management
        • Installation
        • Deployment
    • Tools : WebConsole
      • Administrate
        • Installation
        • Deployment
      • Monitor
        • Messages
        • Services
        • Platform
      • Manage errors
    • Installation – Deployment phase Client Side Provider Side WS Client WS Provider (SB)‏ Ejb Container (SA)‏ Service Assembly BC SOAP PEtALS JBI Env JBI Env BC SOAP BC EJB SE Orchestra WSP SU (SB)‏ Ejb SU (SA)‏ Bpel SU (SC)‏ WSC SU
    • Runtime phase Client Side Provider Side JBI Env JBI Env SE Orchestra WS Client WS Provider (SB)‏ Ejb Container (SA)‏ BC SOAP PEtALS BC SOAP BC EJB 1 2 3 3 4 4
    • Runtime phase Client Side Provider Side JBI Env JBI Env SE Orchestra WS Client WS Provider (SB)‏ Ejb Container (SA)‏ BC SOAP PEtALS BC SOAP BC EJB 8 7 6 6 5 5
    • Questions