Wednesday, May 22, 13. Java Business Integration

Transcription

1 Java Business Integration

2 Java Business Integration Enterprise Application Integration and B2B often require non-standard technology this causes lock-in! no single provider can give us all we need. JBI provides a standards SOA-based architecture for integration third-party components are plugged in interoperate in a predictable and reliable manner (message exchanges) Interfaces defined through WSDL

3 Meta Container Service engines (SEs) JBI is a meta container A SE provides business logic and transformation services Binding components (BCs) Used to provide external connectivity Web services, JMS, etc. JBI also provides a management structure based on JMX install components manage a component s lifecycle deploy service artifacts to components

4 Meta Container

5 JBI Goals The establishment of a standard integration architecture for developers of service engines and binding components, known collectively as JBI components. The development of an abstract protocol-neutral Message Exchange and Normalized Message (NM) Provision of a standard mechanism for Message Exchanges to flow between JBI components Establishment of a standard for the packaging of JBI components, as well as for deployment of service artifacts to such components Definition of administrative and management hooks such that a diverse set of standard tools targeted at specific problem domains can emerge over time

6 High Level Architecture JBI Messaging Infrastructure allows for decoupling JBI offers APIs for installation, deployment, and management of components

7 Normalized Messages WSDL has two levels: abstract service model vs concrete service model JBI uses the abstract model Components play either the provider or the consumer role Normalized messages are made of two parts: abstract XML message defined through WSDL message metadata (message context data) extra information used during processing by plugins and system components

8 Normalized Message Router Provides One-Way, Reliable One-Way, Request-Response, and Request-Optional Response MEPs The qualities of service supplied by the NMR, in collaboration with the bindings and engines as needed, are: Best effort. Messages may be dropped, or delivered more than once. At least once. Messages may not be dropped, but duplicates may be delivered. Once and only once. Messages are guaranteed to be delivered only once.

9 Normalized Message Exchange 1. BC Receives Request: 1. converts message to normalized form 2. creates a Message Exchange (container for the messages involved in the pattern) 3. sets metadata describing the desired service and operation 2. BC initiates the Message Exchange 3. NMR routes the message to the provider (SE/BC)

10 Normalized Message Exchange 1. Consumer creates a normalized message 1. puts it into a Message Exchange 2. Consumer continues the Message Exchange 3. BC de-normalizes the message into a protocol and transport format and sends the message

11 JBI vs. ESB JBI does NOT specify how to communicate among nodes it only specifies the internal integration (JVM) ESB has to specify inter-node communication facilities Open ESB does NOT provide communication transparency ServiceMix uses JMS

12 An Example Loan Request BPEL Process LoanProcessor JavaEE TransformReport XSLT LoanReport partner FTP LoanReportMailer JMS (legacy ) 3 engine components: BPEL / JavaEE / XSLT 3 binding components: WS / JMS / File

13 Service unit vs service assembly Service Unit: LoanRequestProcess/LoanRS WS/LoanProcessorEJB/ecc. Service Assembly: package containing all the service units

14 Open ESB

15 Components in Open ESB Application Mashup AOSD Aspects Aspect SE Communications These components provide different methods of communicating with other components of the Enterprise Service Bus. ADABAS Natural CICS BC CORBA BC DCOM BC File BC FTP BC HL7 BC HTTP BC SIP BC UDDI BC XMPP BC Data Conversion Translating different data formats among systems with varying requirements. ETL SE XSLT SE Data Extraction and Transformation ETL SE SQL SE Data Integration ETL SE Data Mashup Database Connection Components that allow connection and inspection of databases. Informix IMS BC JDBC BC Oracle SAP Sybase Event Processing IEP SE Java EE SQL SE Orchestration and Collaboration BPEL SE Scripting Scripting SE Work List Manager WLM SE

16 Apache ServiceMix Flexible, open source integration container that unifies: ActiveMQ - message broker (JMS) - reliable messaging Camel - rule-based routing on the NMR Drools - rule engine CXF - web service stack (SOAP/REST) EIP - deployable routing patterns content-based, message-filter, pipeline, etc. ODE - business process execution Karaf - OSGi runtime EXEC - for executables and binaries FILE - Integration to the file system SAXON On FTP/HTTP/JMS/SOAP/MAIL/SNMP/XMPP

17 Camel A CamelContext contains: components - endpoint factory endpoints - identified by URIs Internal Components: AMPQ, Atom, Aws, Bean, Cxf, Ejb, Exec, File, Ftp, GHttp, Gmail, Http, Irc, Javaspace, Jbi, Jdbc, Jetty, Jms, Jmx, Jpa, Ldap, Nagios, Rmi, Rss, Servlet, Sftp, Spring, Tcp, Udp, Xmpp, Xquery, Xslt External Components: ActiveMQ, Esper, Hibernate Camel implements Enterprise Integration Patterns

18 Integration Patterns

19 Integration Patterns

20 Integration Patterns

21 ServiceMix Integration Example Using Camel <?xml version="1.0" encoding="utf-8"?> <blueprint xmlns=" xmlns:xsi=" xsi:schemalocation=" <camelcontext xmlns=" <route> <from uri="file:camel/input"/> <log message="moving ${file:name} to the output directory"/> <to uri="file:camel/output"/> </route> </camelcontext> </blueprint> Move a file from one folder to another

22 ServiceMix Integration Example <blueprint xmlns=" xmlns:xsi=" xsi:schemalocation=" <camelcontext xmlns=" <route> <from uri="file:camel/input"/> <to uri="file:camel/output"/> <setbody> <simple> FileMovedEvent(file: ${file:name}, timestamp: ${date:now:hh:mm:ss.sss}) </simple> </setbody> <to uri="activemq://events" /> </route> </camelcontext> </blueprint> Generates an event message and send it to ActiveMQ

23 ServiceMix Integration Example <blueprint xmlns=" xmlns:xsi=" xsi:schemalocation=" <camelcontext xmlns=" <route> <from uri="activemq://events"/> <to uri="log:events"/> </route> </camelcontext> </blueprint> Receives the event message and routes it to the log

24 Mule ESB

25 Enterprise Service Backbone Mule is an open-source Enterprise Service Backbone (ESB) 24

26 SOA Swiss Army Knife

27 SOA Swiss Army Knife } Supports a variety of service topologies including ESB

28 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model

29 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging

30 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet

31 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book)

32 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book) } Breadth of connectivity; 60+ technologies

33 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book) } Breadth of connectivity; 60+ technologies } Transparent Distribution

34 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book) } Breadth of connectivity; 60+ technologies } Transparent Distribution } Transactions; Local and Distributed (XA)

35 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book) } Breadth of connectivity; 60+ technologies } Transparent Distribution } Transactions; Local and Distributed (XA) } Fault tolerance; Exception management

36 SOA Swiss Army Knife } Supports a variety of service topologies including ESB } Highly Scalable; using SEDA event model } Asynchronous, Synchronous and Request/Response Messaging } J2EE Support: JBI, JMS, EJB, JCA, JTA, Servlet } Powerful event routing capabilities (based on EIP book) } Breadth of connectivity; 60+ technologies } Transparent Distribution } Transactions; Local and Distributed (XA) } Fault tolerance; Exception management } Secure; Authentication/Authorization

37 Why do developers choose Mule?

38 Why do developers choose Mule? No prescribed message format } XML, CSV, Binary, Streams, Record, Java Objects } Mix and match Zero code intrusion } Mule does not impose an API on service objects } Objects are fully portable Existing objects can be managed } POJOs, IoC Objects, EJB Session Beans, Remote Objects } REST / Web Services

39 Why do developers choose Mule? No prescribed message format } XML, CSV, Binary, Streams, Record, Java Objects } Mix and match Zero code intrusion } Mule does not impose an API on service objects } Objects are fully portable Existing objects can be managed } POJOs, IoC Objects, EJB Session Beans, Remote Objects } REST / Web Services

40 Why do developers choose Mule? No prescribed message format } XML, CSV, Binary, Streams, Record, Java Objects } Mix and match Zero code intrusion } Mule does not impose an API on service objects } Objects are fully portable Existing objects can be managed } POJOs, IoC Objects, EJB Session Beans, Remote Objects } REST / Web Services Easy to test } Mule can be run easily from a JUnit test case } Framework provides a Test compatibility kit } Scales down as well as up

41 Use of Advanced Technologies SEDA Staged Event-Driven Architecture Java NIO Java New Input/Output 27

42 SEDA SEDA decomposes a complex, event-driven software application into a set of stages connected by queues This design avoids the high overhead associated with thread-based concurrency models, and decouples event and thread scheduling from application logic By performing admission control on each event queue, the service can be wellconditioned to load, preventing resources from being overcommitted when demand exceeds service capacity SEDA employs dynamic control to automatically tune runtime parameters (such as the scheduling parameters of each stage) as well as to manage load Decomposing services into a set of stages also enables modularity and code reuse, as well as the development of debugging tools for complex event-driven applications 28

43 NIO NIO is a collection of Java programming language APIs that offer advanced features for intensive I/O operations NIO facilitates an implementations that can directly use the most efficient operations of the underlying platform NIO includes: Buffers for data of primitive types Character set encoders and decoders A pattern-matching facility based on Perl-style regular expressions (in package java.util.regex) Channels, a new primitive I/O abstraction A file interface that supports locks and memory mapping A multiplexed, non-blocking I/O facility for writing scalable servers 29

44 Mule Node Architecture

45 Mule Topologies Mule can be configured to implement any topology:

46 UMO UMOs in Mule can be any object POJOs, EJBs, Remote Objects, WS/REST Services A service will perform a business function and may rely on other sources to obtain additional information Configured in Xml, or programmatically Mule Manages Threading, Pooling and resource management Managed via JMX at runtime

47 Endpoints Used to connect components and external systems together Endpoints use a URI for Addressing Can have transformer, transaction, filter, security and meta-information associated Two types of URI scheme://[username][:password]@[host][:port]?[params] smtp://ross:pass@localhost:25 scheme://[address]?[params] jms://my.queue?persistent=true

48 Routers

49 Routers Control how events are sent and received Can model all routing patterns defined in the EIP Book

50 Routers Control how events are sent and received Can model all routing patterns defined in the EIP Book Inbound Routers Idempotency Selective Consumers Re-sequencing Message aggregation

51 Routers Control how events are sent and received Can model all routing patterns defined in the EIP Book Inbound Routers Idempotency Selective Consumers Re-sequencing Message aggregation Outbound Routers Message splitting / Chunking Content-based Routing Broadcasting Rules-based routing Load Balancing

52 Filter A filter optionally filters incoming or outgoing messages that are coming into or going out from a connector. For example, the File Provider comes with a FilenameWildcardFilter that restricts which files are read by the connector based on file name patterns. For example only files with the.xml extension can be routed. Filters are used in conjunction with Routers. 35

53 Transformers

54 Transformers Converts data from one format to another Can be chained together to form transformation pipelines

55 Transformers Converts data from one format to another <jms:object-to-jms name="xmltojms"/> Can be chained together to form transformation pipelines <custom-transformer name="cobolxmltobusxml" class="com.myco.trans.cobolxmltobusxml"/> <endpoint address="jms://trades" transformers="cobolxmltobusxml, XmlToJms"/>

56 Mule Event Flow Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation Inbound Component The nine stages of a mule event first 2 inbound middle 4 component last 2 outbound Interceptor Outbound Router Outbound Transformer Outbound Endpoint (Message Dispatcher) 37

57 Message Receiver Endpoint Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation Interceptor Some event triggers a message flow A file being written into a folder A message arriving on a message queue A record in a database Data written to a socket Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 38

58 Inbound Router Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) The inbound router is the fist step in a message. Functions typically performed by an inbound router Filtering Remove duplicate messages Matching messages Aggregation (combining) Re-sequence data Forwarding See also IdempotentReceiver CorrolationAggregator CorrelationResequencer 39

59 Interceptor Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation Used to intercept message flow into your service component Used trigger monitor/events or interrupt the flow of the message Example: an authorization interceptor could ensure that the current request has the correct credentials to invoke the service. Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 40

60 Inbound Transformer Endpoint (Message Receiver) Inbound Router Interceptor If the inbound data is not in the correct format for the service it must be transformed at this point Inbound Transformer Service Invocation Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 41

61 Service Invocation Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation The actual service is performed In mule, this is generally a Java object Service invocation can also be a "pass through" Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 42

62 Outbound Router Endpoint (Message Receiver) Inbound Router Interceptor Dispatching the data to all the relevant endpoints Inbound Transformer Service Invocation Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 43

63 Routers Inbound Outbound Response Idempotent Receiver Filtering Outbound Router Response Aggregator Selective Consumer Aggregator Resequencer Forwarding Consumer Recipient List Multicasting Router Chaining Router Message Splitter Filtering List Message Splitter Filtering Xml Message Splitter Exception Based Router 44

64 Outbound Transformer Endpoint (Message Receiver) Inbound Router Interceptor Inbound Transformer Service Invocation Any transformations that needs to be done on the message after a service has been performed on the message can be executed before it is put into the endpoint See Also EnvelopeInterceptor Interceptor Outbound Router Outbound Transformer Endpoint (Message Dispatcher) 45