Magnus Larsson Callista Enterprise AB

Transcription

1 SOA Govern nance Consumers Process Management Composite s Core s Systems Systems Portals Web Apps COTS Legacy Inhouse Magnus Larsson Callista Enterprise AB Ma nagemen nt & Monitoring CEP - B AM

2 Vendor support of Open Source SOA Vendors provide services for training, consulting and support on selected Open Source SOA products MuleSource Over 1000 mission-critical production installations worldwide! co /custo e s/casestud p p WSO2 Progress FUSE

3 Building a SOA Reference Model Consumers Systems Portals Web Apps Systems COTS Legacy Inhouse

4 Building a SOA Reference Model Consumers Systems Connectivity - SOAP, Rest, Messaging, Database, FTP Portals Web Apps Transformation - XML, CSV, Fixed Position Routing - Header and/or Content based Enterprise Integration Patterns - Splitting, Aggregation, Resequencing Core s Systems COTS Legacy Inhouse

5 Building a SOA Reference Model Consumers Systems Portals Composite s Course Web Grained Apps Internal Messaging High performance access to other services Composite s Core s Systems COTS Legacy Inhouse

6 ESB - Enterprise Bus The hart of SOA Consumers Systems Portals Web Apps Composite s Core s Systems COTS Legacy Inhouse

7 Enterprise Bus Example Example: Purchase Order Process From SOA Modeling Language specification (UML Profile) / d/08 0 df

8 Enterprise Bus Example Consumers Web App System REST? SOAP/HTTP JMS (CSV)? Systems Purchasing EU Purchasing NA Purchasing ASIA

9 Architecture ESB Usage Example Inside ESB Only use internal messaging, VM -protocol Only use Canonical Message Formats, CMF ESB VM Purchasing EU SOAP/HTTP Web App RESTful CMF Message Purchasing CMF Message Purchasing EU REST VM Purchasing NA JMS VM Purchasing NA

10 Introducing Mule ESB Mule ESB Transport Transport Sending Application Channel Message Rec ceiver Connector Tra nsformers Inbound Ro outer Component Outbo ound Router ers Transform Connector Messag ge Dispatche Channel Receiving rapplication Configuration based on Spring Framework Transports: Additional available on Routers: Transformation (using Smooks):

11 Enterprise Bus Example Mule ESB REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS <service name="purchasing_client"> <inbound> <inbound-endpoint address=" synchronous="true > <acegi:http-security-filter realm="mule-realm"/> </inbound-endpoint> </inbound>...

12 Enterprise Bus Example Mule ESB REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS <outbound> <filtering-router> <outbound-endpoint address="vm://purchasing" transformer-refs="ppo.resttocmf" responsetransformer-refs="ppo.cmftorest" synchronous="true /> <restlet:uri-template-filter pattern="/processpurchaseorder" verbs="post" /> </filtering-router> router> <filtering-router> <outbound-endpoint address="vm://getpurchaseorder"/> <restlet:uri-template-filter pattern="/purchaseorder/{poid}" verbs="get"/> </filtering-router> </outbound> </service>

13 Enterprise Bus Example Mule ESB REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS <service name="purchasing"> <inbound> <inbound-endpoint address="vm://purchasing" synchronous="true"/> </inbound> <outbound> <filtering-router> <outbound-endpoint address="vm://s1 vm://s1_purchasing_eu EU" synchronous="true"/> <message-property-filter pattern="role=role_user_eu"/> </filtering-router> <filtering-router> <outbound-endpoint address="vm://s2_purchasing_na" synchronous="true"/> <message-property-filter pattern="role=role_user_na"/> </filtering-router> </outbound> </service>

14 Enterprise Bus Example Mule ESB REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS <service name="purchasing_eu"> <inbound> <inbound-endpoint d i address= vm://s1_purchasing_eu" P h i S i synchronous="true"/> "/ </inbound> <outbound> <pass-through-router> <cxf:outbound-endpoint address= wsdllocation="classpath:/schemas/business/purchase/purchase-1.0.wsdl" wsdlport="purchasingport" operation="processpurchaseorder" clientclass="se se.callista.soalab.purchase.wsdl.v1.purchasing soalab Purchasing synchronous="true" /> </pass-through-router> </outbound> </service>

15 Enterprise Bus Example Mule ESB REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS <jms:activemq-connector name="jmsconnector" brokerurl="tcp://localhost:61616 /> <service name="purchasing_na">... <outbound> <pass-through-router> <outbound-endpoint address="jms://soalab.purchasing_na.request" transformer-refs=..." synchronous="true"/> <reply-to address="jms://soalab jms://soalab.purchasing_na.response Response" /> </pass-through-router> </outbound> <async-reply timeout="10000"> <inbound-endpoint address="jms://soalab.purchasing_na.response" transformer-refs=..."/> <single-async-reply-router/> </async-reply> </service>

16 Enterprise Bus Example Mule ESB Unit testing services in Mule ESB Test Proxy s Separate config-file JUnit Tests Mule base class initiates Mule ESB per test run Unit Tests REST ESB RESTful VM Purchasing VM VM Purchasing EU Purchasing NA SOAP/HTTP JMS Test Proxy EU Test Proxy NA

17 Mule ESB Connectivity - FTP vm: ftp: CMF Message Transform FromCMF FTP Transport Receiving Application Declare a FTP Connector <ftp:connector name="ftpconnector" pollingfrequency="1000" binary="true" passive="true" outputpattern="${originalname}_${date}.txt" /> Send file to a FTP Server <outbound-endpoint address="ftp://usr:pwd@server/dir />

18 Mule ESB Connectivity - JDBC vm: jdbc: CMF Message Transform FromCMF JDBC Transport Receiving Application Declare a JDBC Connector <jdbc:connector name="jdbcconnector" pollingfrequency="500" datasource-ref="jdbcdatasource"> <jdbc:query key="insertimportdata" value="insert INTO IMPORT_TB (ID, VALUE) VALUES (${map-payload:id}, ${map-payload:value})"/> </jdbc:connector> Insert records into staging table <jdbc:outbound-endpoint querykey="insertimportdata transformer-refs= ToMap"/> refs

19 Mule ESB Transaction and Error Handling Configure transactional endpoints <jms jdbc vm:transaction action="always_begin"/> Global XA transactions <xa-transaction action="always_join"/> Error handling including commit/rollback control <default-service-exception-strategy> <vm:outbound-endpoint path="s0_systemerrorhandler"/> <commit-transaction exception-pattern="se.callista.soalab.exception"/> </default-service-exception-strategy>

20 Building a SOA Reference Model Consumers Systems Portals Web Apps Process Management Composite s Core s Systems BPM Process Management 1. Orchestration COTS Legacy Inhouse 2. Workflow

21 BPM (JBoss jbpm)

22 BPM (JBoss jbpm)

23 Building a SOA Reference Model Consumers Systems Portals Web Apps SOA Governance SOA Govern nance Process Management Composite s Core s Systems COTS Legacy Inhouse

24 What is SOA Governance tools? From To enable SOA governance, software industry responded with two different categories of tools, registries and repositories. A registry is a tool that keeps a list of services with their locations. On the other hand a repository functions as a tool that keeps information on how the services are used, how they interact, who is using the services and why they are used. These tools are considered as key enablers of SOA Governance. Usually these two technologies come together as an "Integrated" Registry-Repository, Reposito thus avoiding data duplication.

25 SOA Governance (Mule Galaxy)

28 SOA Governance (Mule Galaxy) ATOM API Query example p q=select artifact where documenttype = { <feed xmlns=" <entry> <link href="/api/registry/applications/soalab/soalab-purchase-config.xml;atom /> i /A ti / l l b h fi l t <title type="text">soalab-purchase-config.xml</title>... </entry> <entry> <link href="/api/registry/default%20workspace/hello-config-mule2.xml;atom" /> <title type="text">hello-config-mule2.xml</title>... </entry>... </feed>

29 Building a SOA Reference Model SOA Govern nance Consumers Process Management Composite s Core s Systems Systems Portals Management and Monitoring Web Apps Managem ment & Monitorin ng COTS Legacy Inhouse

30 Management and Monitoring (Mule HQ)

33 Building a SOA Reference Model SOA Govern nance Consumers Process Management Composite s Core s Systems Systems Portals Activity Monitoring Web Apps Managem ment & Monitorin ng CEP - BA AM COTS Legacy Inhouse

34 What is BAM & CEP? Activity Monitoring (BAM) and Complex Event Processing (CEP) can be defined as (from "Software technology that enables applications to monitor multiple streams of event data, analyze them in terms of Key Performance Indicators (KPI) that are expressed in event rules, and act upon opportunities and threats in real time, potentially by creating derived events, or forwarding raw events."..

35 Activity Monitoring (Esper) ESB Events Alerts Rules BAM-Engine

36 Activity Monitoring (Esper) ESB Events Alerts Rules BAM-Engine Wire Tap

37 Activity Monitoring (Esper)

38 Activity Monitoring (Esper)

39 Activity Monitoring (Esper) ESB Operational Messages jms: Order BAM Alert Handler jms: Order Processor (long running process) BAM Alerts BAM Events BAM Engine

40 Activity Monitoring (Esper) Order Mule ESB BAM Alert Handler <service name="orderprocessor_testproxy"> <inbound> <jms:inbound-endpoint queue="soalab.orderprocessor /> <wire-tap-router> <jms:outbound-endpoint queue="soalab.bam"/> </wire-tap-router> </inbound> BAM Engine (Esper) select po.id as orderno from pattern [every po=created -> (timer:interval(3 sec) and not Completed(id = po.id))] <service name="bam-alert-component"> <inbound> <jms:inbound-endpoint queue="soalab.bam.alert"/> </inbound> <log-component/> </service>

41 SOA Reference Model, the complete picture SOA Govern nance Consumers Process Management Composite s Core s Systems Systems Portals Web Apps Managem ment & Monitorin ng CEP - BA AM COTS Legacy Inhouse

42 A sample Open Source SOA Sandbox SOA Govern nance Mule Galaxy Consumers Process Management Composite s Core s Systems Restlet Systems Portals JBoss jbpm Mule ESB CXF Web Apps ActiveMQ COTS Legacy Inhouse Managem ment & Monitorin ng Mule HQ CEP - BA AM Esper

43 SOA Product Areas SOA Govern nance Consumers Process Management Composite s ESB Core s Systems Systems Portals Web Apps Managem ment & Monitorin ng CEP - BA AM COTS Legacy Inhouse

44 Open Source SOA ESB MuleSource Mule ESB Apache Mix Sun OpenESB ESB buidling blocks Apache Synapse (WS + XML focus) Apache Camel (EIP library)

45 Open Source SOA ESB Connectivity - Web s Apache CXF Apache Axis Sun Metro (WS-IT) MS.Net WCF interoperability ESB Connectivity - Messaging Apache ActiveMQ Sun OpenMQ JBoss Messaging g Spring.NET Messaging API JMS API for MS.NET ESB Connectivity REST Restlet t Jersey JAX-RS (JSR 311) Adbera Atom Feeds

46 Open Source SOA BPM Apache Ode Sun BPEL Engine JBoss jbpm SOA Governance Tools Repository & Registry MuleSource Galaxy WSO2 Registry

47 Open Source SOA BAM Esper JBoss Drools (since v5.0) Monitoring and Management Hyperic HQ MuleSource Mule HQ Progress Fuse HQ Builtin JMX access, e.g. in ESB products

48 Summary Open Source products for SOA exists not only for core features such as Web s, Messaging and ESB but also for SOA Governance, Monitoring & Management and BAM Typical scenarios for service provisioning and consumption can be implemented very easy Advantages compared to commercial products Lower license cost, obviously Lower complexity, at least for mainstream scenarios Easier to extend Vendor service offerings for support, training and consulting Important to establish a reference model and guiding principles SOA Governance, holistic view

49 Recommended reading

50 Questions?