Jazoon2010 - Edgar Silva - Open source SOA on Steroids
2 likes•825 views
This document discusses combining the JBoss Enterprise Service Bus (ESB) with the Apache Camel integration framework. It provides an overview of both technologies and how they can be used together, such as creating new listeners for the JBoss ESB using Apache Camel and new components for Apache Camel. The document also introduces the breakingwoods project as an example of mixing the two solutions.
Jazoon2010 - Edgar Silva - Open source SOA on Steroids
- 1. Open source SOA on Steroids: Combining the robustness of JBoss ESB with the flexibility of Apache Camel Edgar A Silva JBoss, by Red Hat Submission ID 88
- 2. About the Speaker Working with Java and Distributed Computing since 1998
- 3. Worked as an architect for large scale Java solutions in Brazil, such as: New Federal Brazilian Lottery System
- 4. JBoss Employee in charge to bring technology and business viewing at Red Hat Brazil
- 5. Agenda Systems Integrations Overview
- 6. What about: Apache Camel
- 7. JBoss ESB
- 8. Where they meet each other Creating new Listeners for JBoss ESB
- 9. Creating new Components for Apache Camel
- 11. Introducing breakingwoods project http://code.google.com/p/breakingwoods
- 12. Level One Level Two How do you integrate your solutions today?
- 13. Where and how to plug in ?
- 15. Enterprise Integration Patterns There are just 4 Integration Styles : File Transfer
- 16. Shared Database
- 17. RPC
- 19. That's why JBoss ESB
- 20. Apache Camel Both are adherent with the EIP's principles and recommendations
- 21. Implementations from a ServiceBus and a Compoenent Framework that made the systems integrations easier
- 23. Introducing Apache Camel http://camel.apache.org
- 24. Apache Camel is a powerful open source Integration Framework based on known Enterprise Integration Patterns
- 25. Apache Camel uses URIs so that it can easily work directly with any kind of Transport or messaging model, for instance: mina:tcp://localhost:6200?textline=true&sync=false
- 27. Apache Camel can to Act as... Event Consumer
- 28. Event Producer Source Protocols HTTP FTP JMS GOOGLE AMQP SMTP Others Destination Protocols HTTP FTP JMS GOOGLE AMQP SMTP Others
- 29. Available Components URI ActiveMQ / activemq-camel
- 30. ActiveMQ Journal / activemq-core
- 37. CXF / camel-cxf
- 41. Esper / camel-esper in camel-extra
- 44. Flatpack / camel-flatpack Freemarker / camel-freemarker
- 45. FTP / camel-ftp
- 46. FTPS / camel-ftp
- 52. HDFS / camel-hdfs in camel-hdfs
- 53. Hibernate / camel-hibernate in camel-extra
- 54. HL7 / camel-hl7
- 56. IRC / camel-irc RSS / camel-rss
- 58. Smooks / camel-smooks in camel-extra
- 63. SQL / camel-sql
- 65. TCP / camel-mina
- 66. Others Full Components List: http://camel.apache.org/components.html
- 67. Routing (from...to) From an URI (Process the Exchange) deliver to another URI from ("direct:start") .setHeader(HttpConstants.HTTP_METHOD, constant(org.apache.camel.component.http.HttpMethods.POST)) . to ("http://www.google.com") . to ("mock:results");
- 68. “ Show me the source code” !
- 70. Camel Component Model Consumer Endpoint Component Producer
- 71. Creating a New Apache Camel Component Infinispan (Cache/Datagrid) http://www.jboss.org/infinispan
- 72. “ Show me the source code” !
- 74. Why do I need an ESB ? You shall be bored to listen it again though :) An ESB can promote an “Event Architecture” simply due to the capacity to listen the events that the company produces and must to react based on them.
- 75. Would be great we think in Clouds of ESBs, clustering and making them HA.
- 77. Transport warranty (JMS Clustering + Fault Tolerance)
- 78. Events are like Messages for ESBs
- 79. ESB vs Standards There is no JSR that standardize an ESB, however the majority of ESB are created on top of many standards, for instance: JDBC, JMS, JAX-WS, JAX-RS, JNDI etc ESB (Service Bus) offers an way to integrate several applications through standards and common protocols such as File Systems, FTP, E-mail etc
- 80. Caution: Sometimes is better to adopt an standardized document / protocol to perform data interchange as well as integrations Ex: XML+Schema , JSON, CSV etc
- 82. JBoss ESB Scalable however Lightweight Enterprise Service Bus
- 83. Inherits benefits from the traditional JBoss Application Server
- 84. Many required services “out-of-the-box” CBR based on Rules Engines ( Drools )
- 85. Workflow based on JBPM
- 86. Services Orchestration via BPEL (Riftsaw/Apache ODE)
- 87. Transformation Services via Smooks
- 88. Adapters ( File, FTP, Http, REST, JMS etc)
- 89. InVM Transport Available at: http://www.jboss.org/jbossesb
- 90. esbgen.sh Creating a new ESB Project made easy
- 91. Using JBoss ESB Effectively
- 92. “ Show me the source code” !
- 93. Introducing Breakingwoods Project http://code.google.com/p/breakingwoods
- 94. Adding a New Event Gateway/Listener
- 95. “ Show me the source code” !
- 97. Apache Camel is already present in JBoss ESB 4.9 svn trunk Thanks David Ward ! http://community.jboss.org/wiki/CamelGateway
- 98. <jbossesb xmlns=" http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd " parameterReloadSecs="5"> <services> <service category="camel_helloworld" name="service1" description="Hello World" invmScope="GLOBAL"> <listeners> <camel-gateway name="gateway1"> <from uri="file://.../samples/quickstarts/camel_helloworld/build/input1?delete=true"/> <from uri="file://.../samples/quickstarts/camel_helloworld/build/input2?delete=true"/> </camel-gateway> </listeners> <actions> <action name="action1" class="org.jboss.esb.actions.SystemPrintln"/> </actions> </service> </services> </jbossesb>
- 100. Proposed Architecture JBoss ESB Server CBR, Drools, CEP, Workflow, BPM, BPEL, EJB, Transactions, Clustering, Loadbalancing etc Java Virtual Machine Apache Camel Data Consumer Cloud
- 108. Books Camel In Action
- 109. Edgar A Silva Red Hat Inc [email_address] QA Thank you