Red Hat JBoss Integration and Business Rules Mgmt

Size: px

Start display at page:

Download "Red Hat JBoss Integration and Business Rules Mgmt"

Aron Booker
8 years ago
Views:

1 Red Hat JBoss Integration and Business Rules Mgmt Michelle Davis JBoss Senior Solutions Architect (240) (cell) May 6, 2014

2 Tech Day Integration and Rules Agenda v v JBoss Portfolio Integration v Why it is SOOoooooo Hard v JBoss Integration Solutions v v The Core ESB Fuse Service Works v Business Rules v v When to use Events and Planning

JBoss Integration Solutions v v The Core ESB Fuse

3 The most ambitious Red Hat JBoss Middleware release. EVER. l l Cloud-ready architecture World-class developer productivity

4 What is a cloud-ready architecture? l l l l l High degree of automation Flexible management Frugal use of resources Lean, agile development Open platform RED HAT JBOSS MIDDLEWARE PHYSICAL VIRTUAL PRIVATE PUBLIC 4 RED HAT CONFIDENTIAL ADD NAME

5 Red Hat JBoss Middleware MIDDLEWARE JBoss Developer Studio Development Tools User Interaction Business Process Management Application Integration Data Virtualization JBoss Portal JBoss BRMS JBoss BPM Suite JBoss Fuse & A-MQ JBoss Fuse Service Works JBoss Data Virtualization JBoss Operations Network Management Tools Foundation JBoss EAP JBoss Web Server JBoss Data Grid ACCELERATE INTEGRATE AUTOMATE

JBoss BPM Suite JBoss Fuse & A-MQ JBoss Fuse Service Works JBoss Data Virtualization JBoss

6 WHY INTEGRATION IS SO HARD?

7 Why Integration is so hard? 7

8 Constellation of protocols & standards 8

9 Huge family of formats 9

10 Microsoft <-> Java, Corba, DCOM? 1 0

11 Architectural Considerations Failover Cloud SDLC DSL High Availability Mediation Operations & Management Routing Support Metrics Web Console Load Balancing IDE / Tooling Alerts Transformation Configuration Management Web Console 11

Support Metrics Web Console Load Balancing IDE / Tooling

13 JBoss Fuse / JBoss Fuse Service Works JBoss Fuse / JBoss Fuse Service Works JBoss Data Virtualization

16 And Thus is Born: The New ESB Core Bringing together the basis for supporting common integrations cn M ( as i (a h o I r g o I MM na 16

17 What is Apache Camel?

18 80+ Endpoint Components activemq cxf flatpack jasypt activemq-journal cxfrs freemarker javaspace amqp dataset ftp/ftps/sftp jbi atom db4o gae jcr bean direct hdfs jdbc bean validation ejb hibernate jetty browse esper hl7 jms cache event http jmx cometd exec ibatis jpa crypto file irc jt/ CONFIDENTIAL - NDA 18

direct hdfs jdbc bean validation ejb hibernate jetty browse esper hl7 jms

19 80+ Endpoint Components language properties seda stream ldap quartz servlet string-template mail/imap/pop3 quickfix sip test mina ref smooks timer mock restlet smpp validation msv rmi snmp velocity nagios rnc spring-integration vm netty rng spring-security xmpp nmr rss spring-ws xquery printer scalate sql xslt 19 19

restlet smpp validation msv rmi snmp velocity nagios rnc spring-integration vm

20 19 Data Formats bindy castor csv crypto dozer flatpack gzip hl7 jaxb json protobuf serialization soap syslog tidy markup xml beans xml security xstream zip =Ap c fi =Ap " chv: t eseq q seqac "/r =Ap c fi =Ap "t ch eseqac "/r ( p c pa p n c fi "geqac ) =c dh g=(a q c fi u p n c"/r (At h /W ic (hpa p n c/wcah /r 20 20

zip =Ap c fi =Ap " chv: t eseq q seqac "/r =Ap c fi =Ap "t ch eseqac "/r ( p c

21 JBoss A-MQ, aka Apache ActiveMQ Standards-based: Ø JMS 1.1, J2EE 1.4, JCA 1.5, JTA and XA Ø C, C++, C#/.Net, Python, Perl, PHP, Ruby and Java Ø multi-protocol broker that supports STOMP, AMQP, MQTT, Openwire, Ø SSL, and WebSockets. Ø Integrated to: Geronimo, Spring, Tomcat, JBoss and any JEE container (e.g., WebLogic/WebSphere) Ø Fastest open source JMS provider by some margin and close, or better than, the proprietary alternatives Highly scalable messaging: Ø Load balancing, Clustering, peer-to-peer, master/slave HA and federated networks support Ø Distributed Destinations, smart routing features like exclusive queues and message groups 21

22 CXF for ESB Core Web Services A Flexible container for hosting web services. p n A= aaq( u a (: p a ac o A( : P cd ac ( A( Aaa c (=(pa ==ip va i/ A(t h / Aac ) p i = =(A d A nq( qap n Acv A a p=qic A nq(v A p( ci; p A ( c p c n(v A u pcd = d t i (; v: : ia=t c c t P a c qn ) a d t ca x x At =ip c p ( ( pt =i t cv A A p t Ac (: p a = p v A a ; qa Aq( P AaaP wf P ( t pvp qi AE P i P At P AAni P At At 22

23 Fuse ESB the Technologies ps amo( sm cn r g h a h cn cn i c na A A ( l ta g l t n A vm a r as (am(g A n (a r na A A A A 23

24 FUSE SERVICE WORKS CONFIDENTIAL - NDA

25 JBoss Fuse Service Works Make it an ESB: add in JEE, governance, and make it easy, please gnom nmv g c g(or as ( h o I r g o I cn c g(or as Mn a (c a a vai r (c a a vm ai sg r as o i (a g a r as c(q cq( P a (: p xa(p c : ia=t (: p : ia=t c a (acxa( ( q==a(c A( pac(p qc P (Aaax q va i A( A t A i (p: caaip n pt =ip (: p p ; i q va i eqp: i u pcd. n u pcd a A( Aaa a ; t pn( va (At ( ca dap A x A( A( c 25

26 JBoss Fuse Service Works: Bound by Switchyard Switchyard makes all the components work for you ( C ns I o I r g c am m ((gm X F Service First Development with Switchyard and SCA Contract-based development for messages, policy, SLA Dependency Management Binding Abstractions for interfaces & endpoints Declarative Transaction & Security Policy Declarative Data Handling for transformation & validation 26

27 Service Component Architecture (SCA) OASIS standard for creating service-oriented applications Describe Assemble Build Defines how to create components and how to combine those components into larger structures called composites. Set of specifications for building applications 27

28 Whats it all About? 28

29 SwitchYard App Switchyard Tooling 29

30 Service Bindings FSW Service Bindings 30

31 Implementation FSW Service Implementations 31

32 JBoss Fuse Service Works: Rule Your Enterprise Governance tools around all key components, all the time ( C ns I (c - h nms E (c q vt =Aip ; A( t c p = c A a (: p : (ia( A: =(A: p a (q vt na: ( i vt v: pc; ( =A(v n A( a (: p c( a va : c i; apa A(( iv A u pcdp (Aaa a (: p a (apac p A(t v A aq==a(ca dpaca(p i ; apa A qap aa v: pc; aqica (At cd qap aa =Aip p a d ( ( ; Acd ( = =ip v A a 32

33 Your Choice: lightweight services integration or fully capable ESB Get only capabilities you need, with the same great technology. ( (MM vm h o I r g o I (MM vm cn ( em Q A m o ( v sma i va i (a gnse 33

34 REMEMBER THOSE RULES?

35 Complex Policies, Rules (BR1) The manager of a department must belong to that department. (BR2) An employee cannot earn more than her manager. (BR3) A department of the Toronto office can only be managed by an employee who has 10yrs experience. (BR4) An employee can only participate in projects associated with her department 35

36 Scheduling Issues Every organization faces planning problems; There are products and services with a limited set of constrained resources (employees, assets, time, and money). Employee/Patient Rosters. Creating timetables for nurses and keeps track of patient bed management. Educational Timetables. Scheduling lessons, courses, exams, and conference presentations. Shop Schedules: Tracking car assembly lines, machine queue planning, and workforce task planning. Cutting Stock: Minimizing waste by reducing the consumption of resources such as paper and steel. 36

37 Benefits of a BRMS BRMS allows decoupling management of business logic from the software development team. Business rules can be versioned separately from the code. Rules are constructed in a manner more understandable by nontechnical staff by means of using flows, decision tables, and specific languages. Requirements can be naturally translated into rules. Each rule models an isolated, small portion of the business logic and is not part of a monolithic program. It is easier to modify a rule than a Java program and to determine the impact of this change on the rest of the application. 37

38 Use a Rules Engine When The issue is too complex to be dealt with using the standard if else approach in the code The issue is not too complex to be dealt with using the standard if else approach in the code, but the solution might be subject to frequent changes that could break the existing architecture. The solution to the problem would comprise of too many nested if else statements. The hardcoded version of the solution would be unmaintainable. The issue is complex and you cannot think of any way of dividing the problem into a series of smaller ones. You want to provide ways for a nontechnical business analyst to enter new rules. 38

39 A single, integrated, certified distribution for Business Rules Management and Complex Event Processing, based on open source community projects: 39

40 BRMS Components How this works Authoring Tools for Business Users Business Analysts Repository Business Rule Definitions Decision Service Facts Decisions Enterprise Applications Authoring Tools for Developers Business Data Developers 40

41 New in

42 qi qcda(p n dap a 42

43 Key BPM Technology Complex Event Processing Systems : ca Detect events of significance to a business by recognizing time-based patterns in one or more real-time data feeds... Applying Business Rules Benefits: ʻActive decision makingʼ: Business makes timely decisions & responds quickly to external events Weather delay in London 43

44 44

45 45

46 Questions 46

How to secure your Apache Camel deployment

How to secure your Apache Camel deployment Jonathan Anstey Principal Engineer FuseSource 1 Your Presenter is: Jonathan Anstey Principal Software Engineer at FuseSource http://fusesource.com Apache Camel