SOA Best Practices (from monolithic to service-oriented)

Size: px

Start display at page:

Download "SOA Best Practices (from monolithic to service-oriented)"

Wendy Holmes
8 years ago
Views:

<Insert Picture Here> SOA Best Practices (from monolithic to service-oriented) Clemens Utschig - Utschig Consulting Product Manager, Oracle SOA Suite & Integration clemens.utschig@oracle.

1 <Insert Picture Here> SOA Best Practices (from monolithic to service-oriented) Clemens Utschig - Utschig Consulting Product Manager, Oracle SOA Suite & Integration clemens.utschig@oracle.com The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remain at the sole discretion of Oracle. 1

Agenda Web services, BPEL and 100% standard integration approaches extend the reach of the application server platform to enable mainstream developers to build service-oriented, processcentric

2 Agenda Web services, BPEL and 100% standard integration approaches extend the reach of the application server platform to enable mainstream developers to build service-oriented, processcentric applications in a highly productive, declarative fashion. <Insert Picture Here> SOA Use Cases Key SOA Standards 7 Steps to SOA Success Q&A Customer Needs Increasingly Demanding Requirements End-to-End Processes Shorter Change Cycles Better Insight and Auditing IT Increasingly Complex Infrastructure Heterogeneous Systems Silos M&A 2

3 The Application Model is Evolving Packaged Applications 2 Fulfillment Center 3 1 Customer Service Business Partners One-Block Solution SOA Solution More Interoperable More Modular Business Processes Richer Clients SOA (batch / performance) Use-Case (I): Retek Sales Module Oracle Financial Ledger Integration INTEGRATION FLOW Retek Receive Error Hospital (Human Workflow) Transform Invoke Oracle Financials BPEL Low complexity, very high volume 3

4 JSF SOA (Process-driven) Use-Case (II) DSL Provisioning Order submit CREATE ACTIVATION FLOW 6000 Devices Validate Customer (DataHub) Customer Profile Order Validation (EJB 3.0) Exception Rate SLA Management BAM Setup 1 Setup 2? BPEL Very high complexity, medium volume? Promotion Management (Business Rules) Exception Management Portal Order Hospital (Human Workflow) SOA (Human-centric) Use-Case (III) the pain with human interaction.. Human centric users expect request/response 4

5 Key SOA Standards Fusion Effect Richer Experience More Adaptable More Interoperable Portal ERP/ Legacy Apps PKI Dashboards Web Application WS Process Flow Logic Security Reliability Logging Failover Dynamic Routing Custom Apps & Services API Web services MONITORING USER INTERFACE PROCESS ORCHESTRATION SERVICE BUS BUSINESS SERVICES BAM / Dashboards WSRP, JSR-168 BPEL WS-Security XML/XML Schema JMX Struts/JSF BPMN / XPDL WS-Policy, SAML WSDL/WSIF Spring Webbeans SCA Web Services Mgmt SOAP JCA SDO Key Standards: WSDL, WSIF and Non- SOAP Bindings WSDL HTTP.NET, Axis Service INTERFACE BINDING BINDING RMI JDBC Service Database Stored Procedures BINDING JCA ERP 5

6 Key Standards: WS-Addressing and Asynchrony WS-Addressing Correlation Callback Location 10:05 Receive Order 10:10 Processing. 10:25 <risk>4</risk> Performance Reliability Business Time Key Standards: WS-Security WS-Security, SAML Signature Encryption Role and Access Control <Patient> Disease A </Patient> 6

7 Key Standards: BPEL and Process Orchestration Markup language for composing a set of discrete services into an end-to-end process flow SalesDB start 10+ years of R&D from MSFT and IBM Rich Flow Semantics Duplicate Number! Optimized Bindings XPATH+XSLT+XQuery Billing WS-Security A Process is a Service Router end interface WSDL porttype Binding: SOAP Key Standards: SCA for reusable building blocks service JMS JCS S S properties C 1 R S wire C 2 R R Service Component Architecture: language-neutral component model assembly model Specifications backed by a growing number of leading industry vendors SCA terminology: composite component reference Composite: deployment unit Service: entry-point into composite Component: provides logic Reference: refers to external services Wire: connects services, components and references no special semantic. 7

8 Key SOA Standards a (B)language standardized graphical notation for drawing business processes A unified view for Business based modeling and execution Especially useful for H2H and analyst driven processes Best Practices for SOA 2. Connectivity and Messaging 1. Portfolio of Services 3. Process Orchestration, Workflow and Rules SOA Strategy 4. User Interface 7. Performance Scalability 5. Business Activity Monitoring 6. Security and Management 8

9 Step 1 Build a Portfolio of Services Contract/Interface First Coarse Grain Documents Asynchronous Interactions Undo/Cancel Operations Versioning WS-I, Wrapped Document Style WSIF Binding to, JCA Spring Integration / Rest Database IMS, CICS SAP Oracle, PSFT Step 2 Wire Through an ESB Enterprise Service Bus UDDI Registry JCA Adapters Service Virtualization Logical Naming Consider Requirements for: Performance Transactionality Quality of Service Interoperability.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc 9

10 Step 3 Orchestrate into End-to-end Processes BPEL Workflow Rules Enterprise Service Bus fx BPEL XSLT Transformation Human Workflow Service Rules Service Notification Service Error Hospital Service ESB Binding and Wiring Tracing and Debugging Iterative Development Unit Testing.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc Step 4 Expose Through Rich User Interfaces Portal, JSF Applications,.NET, Microsoft Office BPEL Workflow Rules fx JSF or Struts WSRP, JSR-168 AJAX Enterprise Service Bus.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc 10

11 Step 5 Deliver Real-time Dashboards Portal, JSF Applications,.NET, Microsoft Office fx BPEL Workflow Rules Enterprise Service Bus KPI First Sensors to Collect Events without Process Logic Changes Real-time Dashboard Alert/Actions (Fusion Effect).NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc Step 6 Policy-Oriented Security Portal, JSF Applications,.NET, Microsoft Office BPEL Workflow Rules fx WS-Policy, WS-Security Change Policy without Changing Endpoint Agent and Gateway Mode RBAC from outside Enterprise Service Bus.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc 11

12 Step 7 Scale on Demand Portal, JSF Applications,.NET, Microsoft Office fx BPEL Workflow Rules Enterprise Service Bus Asynchronous Interactions WS-Addressing Correlation Handle Large XML Documents Appropriately Stateless Architecture (Grid) JCA and Binding Batch API Do a performance POC.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft, Siebel, etc SOA: Top Down versus Bottom Up? Business Analyst Activity Activity Activity Notation Layer BPMN or UML Integration Developer assign invoke receive assign Executable Layer XML, XQuery, BPEL, Rules Service Developer Business Services Adapters,, Struts, JSF Existing Systems DATABASE PACKAGED APPLICATIONS JAVA MAINFRAME 12

13 Summary Packaged Applications SOA Solution Fulfillment Center Customer Service Business Partners Best Practices/Strategy 1. Portfolio of Services 2. Enterprise Service Bus 3. Process Orchestration 4. User Interface 5. Activity Monitoring 6. Policy Management 7. Performance More Interoperable More Modular Business Processes Richer Clients References and more information SOA Design Patterns, Prentice-Hall Thomas Erl, 2009 SOA in Practice, Oreilly Nicolai M. Josuttis, 2007 Magazin SOA aus dem wahren Leben Winterberg, Maier, Normann, Trops, Utschig 13

Raghu R Kodali Consulting Product Manager, & Evangelist Oracle Fusion Middleware Oracle USA Author Beginning EJB 3 Application Development (Apress)

Integrating BPEL, Workflow & Business Rules Raghu R Kodali Consulting Product Manager, & Evangelist Oracle Fusion Middleware Oracle USA Author Beginning EJB 3 Application Development (Apress) Agenda Why