BPEL-Workflows. Service-Enablement von Applikationen. Sun Produkten. und. auf Basis von.

Transkript

1 BPEL-Workflows und Service-Enablement von Applikationen auf Basis von Sun Produkten Heiko Lemke Sun Microsystems Grid Workflow Workshop Oldenburg, 3. März

2 Business Integration mittels SOA und BPM/Workflow

3 Was sollte verbessert werden? vorher: Isolierte Datensilos diverse technische Schnittstellen Kundendienst Steuerung Auftragsverarbeitung Konten Verwaltung Prüfe Kundenstatus Prüfe Kundenstatus Berechne Frachtkosten Prüfe Produkt Verfügbarkeit Prüfe Produkt Verfügbarkeit Bestellstatus Prüfe Kundenguthaben Prüfe Kundenguthaben Monolithische Anwendungen Bestellstatus Daten Speicher Eigene AS400 Oracle Marketing Vertriebssteuerung CRM Anwendung System System SAP Finance System Warenwirtschaft Anderer System Geschäftsbereich Externer HandelsPartner

4 Service-Definitionen auf Funktionsbasis hinterher: grafische Orchestrierung Kundendienst Steuerung Auftragsverarbeitung Konten Verwaltung Änderungsauftrag Ausnahmeauftrag Anderer Fall Gemeinsame Services Composite Applications bieten mehr Funktionalität Prüfe Prüfe Guthaben Kundenstatus Prüfe Prüfe Erstelle Bestand Bestellstatus Rechnung Daten Speicher Eigene AS400 Siebel Marketing Vertriebssteuerung CRM Anwendung System System Oracle Finance System Warenwirtschaft Anderer System Geschäftsbereich Externer HandelsPartner

5 Composite Application Beispiel Benötigte Geschäftslogik wird durch Services und BPM/Workflow aus bestehenden Anwendungen extrahiert und bereitgestellt Bestehende Anwendungen Modernes Web Interface ogik l s t f schä Eigene Anwendung Ge Gesc häfts l ogik SAP System

6 Was braucht man für eine SOA? Presentation User Interface Generate Quote Process Validate Order Check Credit Consolidate Order for Shipment Process Check Inventory Order Fulfillment Process Schedule Shipment Create Invoice Business Processes Assembly & Orchestration Business Services Business Language Technical Services IT Landscape

7 SOA erfordert Adapter, Transformationen, Orchestration, Kommunikation und mehr... Messaging and Request / Reply Orchestration Transformation Wrappers / Adapters

8 Composite Applications und BPM Wichtige Geschäftsprozesse sind oft fragmentiert A2A B2B BPM Stammdaten Mgmt Workflow B2B A2A Master Data Portal BL Bus. Logic ETL BAM BAM BL B2B Portal B2B B2B Workflow Authentisierung / Identity Management Application Server / Betrieb Portal A2A ETL

9 Sun Java CAPS die SOA Suite Java Composite Application Platform Suite

10 Java CAPS Overview Platform: SOA Perspective - Layers

11 Java CAPS Overview Suite: SOA Perspective - Product Components

12 Java CAPS Overview Suite: Product Components egate Integrator egate Heart and soul The Enterprise Service Bus (ESB) J2EE 1.4-certified runtime via embedded application server Hosts eways (resource adapters) to integrate with external systems Provides shareable repository for all development artifacts Management and monitoring built-in

13 Java CAPS Overview Suite: Product Components eway Adapters eway Adapters J2EE Connector Architecture 1.5 (JCA)based adapters Connects egate to external systems A few examples: File and Batch Database (Oracle) ERP (Siebel, SAP) Communications (HTTP, TCP/IP) Messaging (MQ Series) Mainframe (CICS, IMS)

14 Java CAPS Overview Suite: Product Components einsight BPM einsight BPM Provides human workflow Business Modeler using Business Process Modeling Notation (BPMN) Drag and drop reusable services onto the modeling canvas BPEL, Java & XSLT code generated automatically Integrates web interface (evision) into the process flow

15 Java CAPS Overview Sample einsight BPMN models

16 Workflow incl. User Activities Manual steps via evision or API Manual (human) intervention > User activities User / Roles via LDAP > Assign, re-assign, escalate WorkList Manager > Check-out, resolve evision user pages > User interaction pages Business Process with Workflow

17 Beispiel-Szenario CAPS SOA Integration mittels Application-Service-Wrapping

18 Common Object Based Integration EJB JCA Adaptor EJB WS WSDL WS WSDL JCA Adaptor Common Object De-couples Point-to-Point Integrations Much more robust, a change in app 1 does not impact app 2 Manages complexity, you don t need to know app1 and app2 Scalable, consider App1 integrates to App s 2,3,4.. Reusable services Addresses the spaghetti in the hub issue First Step towards SOA style integration

19 JCA Adaptor Integration the SOA way This is service enablement 50-70% of SOA implementation is about service enablement. Publish onto the ESB CRM user Subscribe from the ESB Service Interface Service Interface Siebel EAI/UAN Adaptor SAP BAPI/ALE Adaptor ERP user

20 einsight JCA Adaptor Integration the SOA way BPEL Service Orchestration SOAP / HTTP, egate JMS, SMTP, FTP, SFTP, egate Service Interface egate eway Java CAPS modules CRM user Business Service Interface Service Interface EJB / XSLT Transformation (Integration) Siebel EAI/UAN Adaptor Technical Service Interface WSDL/XML SAP BAPI/ALE Adaptor JCA / J2EE Open Standards ERP user

21 eway s Service Enable Applications Implementation An eway is an open JCA Adaptor/connector with an open service interface out-of-thebox Service Bus (distributed logical hosts and messaging services) or HUB Technical Services eway s CRM Planning Revenue & Benefits Housing Other Systems An eway provides a technical service interface out of the box

22 egate Collaboration Editor s Implementation Enable the provision of simplified service interfaces, hiding the application interface complexity inside easy to reuse services Service Bus (distributed logical hosts and messaging services) Business Services CRM Planning Revenue & Benefits Housing Other Systems Collaboration Editors transform technical services into business services

23 Complex Transformations Implementation Business focused application service interfaces are easier to use / change than application focused service interfaces Service Bus (distributed logical hosts and messaging services) Simplified Business Service Interface Collaboration App eway Business Service Interface (Common Object) Proprietary Application Interface egate Collaboration Editors allow You to hide application complexity inside the services you build

24 SOA Top-Down

25 Business Process Design 1) Business Analyst designs the Process Model 2) And defines the Service Interfaces NOT THE IMPLEMENTATION otd otd Order Order Business Service (content not defined at this stage) Com Com

26 Business Process Design 1) Business Analyst designs the Process Model 2) And defines the Service Interfaces NOT THE IMPLEMENTATION Business Service (content not defined at this stage)

27 Business Process Design 1) Business Analyst designs the Process Model 2) And defines the Service Interfaces NOT THE IMPLEMENTATION Common Object to Common Object Mapping, a single drag and drop Simple Attribute mapping via drag and Drop 3) Business Analyst Maps output from one service interface to input of another

28 Business Services (e.g.updateerp) Implementing an ASI as a Business Services otd bsupdateerp otd Order Order Business Service (Activity) Com Com otd Order Com Two physical ERP systems seen as technical services otd Order Com Custom OMS

29 SOA Based Implementation Plan - Summary Get Order Quote Submit / Change Order Manage Exception Orders Presentation "User Interface" Presentation Service Interface: Operations and Common Object Models (OrderCOM) defined in WSDL Consolidate Order Generate Quote Process Page Flow Process Validate Order Automated Business Process for Shipment Process Order Fulfillment Process Business Processes "Assembly & Orchestration" Business Service Interface: Operations and Common Object Models (OrderCOM) defined in WSDL Check Credit Check Inventory Schedule Shipment Create Invoice Business Services "Business Language" Application Service Interface: Operations and Common Object Models (OrderCOM) defined in WSDL Com Interface Process Custom OMS Validate Technical Services "IT Landscape"

30 Open Source Tools and CAPS Next

31 OpenESB Open Source JBI ESB Basis for Java CAPS 6

32 OpenESB Features Application Server Glassfish Excellent tooling NetBeans Enterprise Pack Fully JBI compliant Based on the JBI Reference Implementation Latest standards (BPEL 2.0, WebServices) Open Source Community initiated by Sun

33 OpenESB Features Tooling BPEL Editor

34 Further Information Sun SOA > Sun Java CAPS > Open ESB on Java.net > JBI Specification and Reference Implementation >

35 Warum Sun für eine SOA/Workflow Lösung? Einheitliche Umgebung Komplette Umgebung Sichere Zugangs- und Identitätsverwaltung Unterstützung von Standards: Interoperabilität und Portabilität sind gewährleistet Für viele Plattformen verfügbar

36 Vielen Dank