OpenESB
•Transferir como ODP, PDF•
4 gostaram•3,356 visualizações
OpenESB open source ESB based on JBI
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a OpenESB
Semelhante a OpenESB (20)
Mais de Carol McDonald
Mais de Carol McDonald (20)
Último
Último (20)
OpenESB
- 1. OpenESB and Connecting Enterprises Carol McDonald, Java Architect
- 4. deployed on Glassfish ESB
- 7. Lots of glue code
- 10. Not scalable
- 12. SOA and Composite Applications Account Management Order Processing Inventory Data Repositories Services Composite Applications Check Customer Status Check Customer Credit Check Inventory Check Order Status Create Invoice Finance Sales Marketing External Partner Data Warehouse CRM Composed Business Processes Combined Services distributed over network, exchange messages, coordinated activity
- 14. Decouples producers from consumers
- 16. standard application integration framework Standard deployment model JBI – A Universal Plug 'n Play Layer
- 19. Normalized Message Router J2EE Platform System Management Orchestration (BPEL) Transformation (XSLT) J2EE Platform AS2 JMS WS-I Basic SOAP Service Provider Self-Description WSDL WSDL WSDL WSDL WSDL WSDL Components register the services they provide JBI Core Services
- 22. Can be deployed and managed as a single entity
- 25. XSLT SE
- 26. JavaEE SE
- 27. IEP SE
- 28. ETL SE
- 29. SQL SE
- 31. HL7 BC
- 32. SAP BC
- 33. SMTP BC
- 34. HTTP BC
- 35. JMS BC
- 36. File BC
- 37. CICS BC
- 39. CASA
- 40. JBI Mock
- 42. Aspect SE
- 43. Encoding SE
- 44. Rules SE
- 45. Scripting SE
- 47. App Server App Server IDE Web Server BPEL Editor Java EE SE JBI Bus XSLT SE HTTP BC FTP BC FTP BC Many More SEs… FTP BC Many More BCs… XSLT Editor Composite Application Project IEP Editor Composite Application Manager Runtime BPEL SE Java EE EJBs Servlets Java EE SE JBI Bus XSLT SE HTTP BC FTP BC FTP BC Many More SEs… FTP BC Many More BCs… BPEL SE Java EE EJBs Servlets Design-Time Management 3 rd Party Service Platforms 3 rd Party Service Platforms Open Standard Based Service Bus WS-Reliable Messaging WS-Security WS-FastInfoSet, … Many More Editors Many More Editors IEP Monitor BPEL Monitor XSLT Monitor Many More Editors Many More Monitors
- 51. Deployed in Glassfish
- 53. Master Data Management Components (Project Mural)
- 57. GlassFish admin console supports JBI
- 58. Java EE Service Engine JBI
- 59. Java EE (ear/war/jar) JBI composite application
- 60. JBI part of Glassfish clustering architecture
- 62. Types of SOA “NetBeans” Projects
- 69. ETL (Extract, Transform, and Load)
- 70. EDM (Enterprise Data Mashup)
- 71. And more
- 74. NMR BPEL XSLT JavaEE WS-I BP JMS File JBI-based Infrastructure
- 75. NMR Loan Request Process Transform Report Loan Processor EJB LoanRS WS ReportMail ReportStore BPEL XSLT JavaEE File JMS WS-I BP JBI-based Infrastructure Client Business Partner thru FTP Legacy thru JMS
- 76. NMR Loan Request Process Transform Report Loan Processor EJB LoanRS WS ReportMail ReportStore BPEL XSLT JavaEE File JMS WS-I BP
- 77. Creating the Loan Approval Service: 1) Define the Client Interface http://www.netbeans.org/kb/61/soa/homeloanprocessing.html
- 78. NMR Loan Request Process Transform Report Loan Processor EJB LoanRS WS ReportMail ReportStore BPEL XSLT JavaEE File JMS WS-I BP JBI-based Infrastructure Client Example WSDL
- 79. WSDL Elements Abstract Definition Protocol, Encoding, Location Definition
- 81. Netbeans XML Schema Loan Example: Message
- 83. Netbeans WSDL Netbeans WSDL
- 84. Example: Binding, Port, Service < binding name="loanBinding" type="ns:loanProcessWSDLPortType"> < soap:binding style=" document " transport ="http://schemas.xmlsoap.org/ soap/http "/> <operation name="applyForLoanWSDLOperation"> <soap:operation/> <input name="input1"> <soap:body use=" literal "/> </input> <output name="output1"> <soap:body use="literal"/> </output> </operation> </binding> < service name="loanService"> < port name="loanPort" binding="tns:loanBinding"> <soap:address location= " http://localhost :loanService1/loanPort" /> </port> </service> protocol and encoding set of related ports Endpoint address
- 86. BPEL Orchestrating Process (BPEL) Partner Service Partner Service Partner Service Client Partner Service WSDL Web services are described in WSDL orchestrated interaction between Web services
- 88. Correlate message exchanges
- 92. data model for message exchange
- 96. debugging of business processes
- 99. BPEL Document Structure < process> <!– Definition and roles of process participants --> <partnerLinks> ... </partnerLinks> <!- Data/state used within the process --> <variables> ... </variables> <!- Properties that enable conversations --> <correlationSets> ... </correlationSets> <!- Exception handling --> <faultHandlers> ... </faultHandlers> <!- Error recovery – undoing actions --> <compensationHandlers> ... </compensationHandlers> <!- Concurrent events with process itself --> <eventHandlers> ... </eventHandlers> <!- Business process flow --> (activities)* </process>
- 103. NMR Loan Request Process Loan Processor EJB LoanRS WS BPEL JavaEE WS-I BP JBI-based Infrastructure Client Example BPEL
- 104. Example Business Process Invoke <LoanProcessor> Reply <Loan Response> Receive <LoanApplication> <sequence> </sequence>
- 105. Sample Activities in BPEL <sequence> <receive partnerLink=“clientPL” portType=“loanProcessPortType" operation=“applyForLoanOperation” variable=“IN” /> < assign name="setProcessorInput"> <copy><from variable=”clientIn”/><to variable=”ejbIn”/> </copy> < assign/ > <invoke name="InvokeProcessLoan" partnerLink=“ejbLoanProcessorPL” portType=“loanProcessPortType” operation="processLoanApplicationEJB" inputVariable="inventoryRequest" outputVariable="inventoryResponse" /> < assign name="setProcessorOutput"> <copy><from variable=”ejbOut”/><to variable=”clientOut”/> </copy> < assign/ > <reply partnerLink=“clientPL” portType=“loanProcessPortType” operation=“applyForLoanWSDLOperation” variable=“ApplyForLoanOperationOut"/> </sequence>
- 106. LoanRequestProcess BPEL LoanProcessor EJB Web Service WSDL WSDL <receive /> <invoke /> <sequence> < assign / > < assign / > <reply /> </sequence>
- 108. WSDL files
- 110. Java EE With JBI Creating the Loan Approval Service: EJB Service
- 113. Java EE call JBI
- 115. SOAP/HTTP
- 116. JAX-WS
- 117. JAXB Unmarshal xml
- 119. HTTP BC
- 120. Marshall xml
- 121. SOAP/HTTP
- 122. Network layer JBI Container N M R BPEL SE BPEL process EE SE SAP BC HTTP BC HL7 BC HTTP HL7 RMI WSDL WSDL WSDL WSDL BPEL process WSDL ejb.jar WSDL application.ear WSDL
- 124. HTTP BC
- 125. Marshall xml
- 126. SOAP/HTTP
- 127. Network layer
- 128. SOAP/HTTP
- 131. Security context propagation JBI Container N M R BPEL SE BPEL process EE SE SAP BC HTTP BC HL7 BC HTTP HL7 RMI WSDL WSDL WSDL WSDL BPEL process WSDL ejb.jar WSDL application.ear WSDL
- 133. LoanRequestProcess BPEL LoanProcessor EJB Web Service WSDL WSDL <invoke />
- 137. Deploy the application to the JBI server
- 138. Build and run JUnit tests
- 139. Monitor the status of JBI application
- 143. Build and run JUnit tests
- 146. Composite applications can send/receive messages
- 152. Send alerts, trigger services Filter Join 4 2 1 3 1 3 2 4 A4 A3 A2 A1 B4 B4 B2 B1 AB4 AB1 AB2 AB3
- 153. Intelligent Event Processor Real-time event trend detection & proactive management Example: Target offerings to customer behavior ... online, walk-in, call center
- 154. Netbeans Project
- 155. http://www.javapassion.com/soaprogramming/index.html Online SOA class: IEP Application that Captures Incoming Stock Data Stream
- 156. Future Work
- 160. Project Fuji Basis for GlassFish ESB v3 https://fuji.dev.java.net/
- 162. Complementary to more sophisticated orchestration
- 165. Java EE can be Service components in JBI
- 167. Glassfish ESB = Glassfish + OpenESB
- 169. http://open-esb.org
- 172. http://netbeans.org
Notas do Editor
- Mention what the NMR does and how it msgs are sent across including metadata to describe what is happening.
- Completeness of the Suites Beyond traditional integration to include identity management, single customer view, ETL... Integration of the Suites Lowest TCO due to integration of tools & runtimes Identity Built into the Fabric of the Architecture Industry Leading Directory and Access Management IT Professional – Java Professional Collaboration Best Composite Applications: All artifacts automatically exposed as Web services in a common registry available to tools Best Productivity: Graphical tools supporting IT and business collaboration and round-tripping to Java IDE, BPEL and other editors Standards Support: Interoperability and Application Portability Java EE, JBI, JMS, WS-I Basic Profiles, XML Legacy: EDI, de jure and de facto protocols and standards Sun Platform: Architected for a Services Architecture Best SOA Platform: Solaris TM 10, T1 chip, CoolThreads TM Technology
- .
- ETL stands for extract, transform, and load. That is, ETL programs periodically extract data from source systems, transform the data into a common format, and then load the data into the target data store, usually a data warehouse. ETL processes bring together and combine data from multiple source systems into a data warehouse, enabling all users to work off a single, integrated set of data — a single version of the truth. EDM Service Engine is an enabler for building Enterprise mashups by performing the datamashups at the server-side and avoiding huge data sets to be joined at the client-side which could lead to sudden surge in bandwidth requirements and thus makes even the concept of mashups feasible. It serves the new breed of Business users who are part of the organizations transforming themselves to Enterprise 2.0. For example, a Business Analyst wants to get a view of Sales distributed geographically for which he wants to join an internal Data source with an external geospatial data sources.
- WSDL specification defines 7 element types.
- In this example, two messages are defined - the first one is called GetLastTradePriceInput and the other one is called GetLastTradePriceOutput. As you can tell, these are request and response messages of stock quote service. Now please note that message definitions refer to the data types we just defined, TradePriceRequest and TradePrice. Now I said portType is just a collection of operations. In this example, we have only one operation. What is an operation? As I said in previous slide, it is an action, and an action is made of input and/or output messages we just defined using message elements. So in this example, the GetLastTradePrice operation will be performed as a combination of input message, GetLastTradePriceInout, and output message, GetLastTradePriceOutput message. Please note that here there is no mentioning on which XML protocol or transport will be used. This is why we call these elements as abstract definitions. And obviously they have to be bound to a concrete XML and transport protocol. And that is what we are going to see in the next slide.
- In this example, two messages are defined - the first one is called GetLastTradePriceInput and the other one is called GetLastTradePriceOutput. As you can tell, these are request and response messages of stock quote service. Now please note that message definitions refer to the data types we just defined, TradePriceRequest and TradePrice. Now I said portType is just a collection of operations. In this example, we have only one operation. What is an operation? As I said in previous slide, it is an action, and an action is made of input and/or output messages we just defined using message elements. So in this example, the GetLastTradePrice operation will be performed as a combination of input message, GetLastTradePriceInout, and output message, GetLastTradePriceOutput message. Please note that here there is no mentioning on which XML protocol or transport will be used. This is why we call these elements as abstract definitions. And obviously they have to be bound to a concrete XML and transport protocol. And that is what we are going to see in the next slide.
- So in this example, the portType called StockQuotePortType is bound to SOAP as communication protocol. SOAP can support either document style or RPC style. In this example, document style is chosen. And the data format of the operation named GetLastTradePrice will use literal. Finally this service has one communication endpoint which is represented by one port element which specifies the endpoint address for a particular protocol. And in this example, the address happened to be http://example.com/stockquote.
- Ultimately, a BPEL document gets compiled and deployed to a BPEL engine. At that point it is ready to to actuallygo live as a process. Here is a diagram showing the relatiionship of a deployed BPEL process and it partner services. The lines connecting the partners represent the messages flowing back and forth between the BPEL process and its partners. Bear in mind all these messages are exclusively Web Service messages Charles – Mike, I get it!! All of those partners are BPEL too!! Mike – Well, not quite Charles. Those partners are definitely web services and some of them may also be BPEL processs, but it is highly unlikely that they are ALL BPEL processes. Charles – Why not? Mike – Well because somebody has to do the real work. BPE is not a general purpose programming language. Remember a BPEL process is an “orchestration” and orchestration implies delegation. And delegation implies that somebody else is doing the work. BPEL can't do everything.
- What does it mean to say that BPEL is an XML based langauge? You are all familiar with programming languages like Java. You are probably all familiar with XML documents and have seen XML used for specifying things like deployment descriptors. But you may not have seen XML used as a programming language. This means that the BPEL specification has defined an XML vocabulary, a collection of XML elements and their attributes which collectively form the BPEL language. It further means that a BPEL programmer “programs” a BPEL process by authoring an XML document which utilizes these BPEL specfic XML elements. Here is the skeleton of a BPEL process. You can see it is highly structured. There are well defined sections. You can also see that there is ofthen quite a bit of “set up” before you actually get to the heart of the process ... the activities. The activities are where the real orchestration takes place. We will cut to the chase and focus on the activies ... next slide.
- * Invoking other web services, using <invoke> * Waiting for the client to invoke the business process through sending a message, using <receive> (receiving a request) * Generating a response for synchronous operations, using <reply>
- And thirdly, BPEL provides structured activities which allow the BPEL programmer to order a collection of activites in various logical combinations – sequentially or parallel, conditionalized and in arbitrarily nested scopes.
- .
- .
- Intelligent Event Processing the scenario is about tracking how, a bank's customers for example, tend to switch between using different channels to get their business done. The scenario tracks changes in behavior over a period of three months. The background is about the bank trying to predict the behavior to say, sell services that may be useful based on the current behavior. What does EDA enable that a BI system does not? A BI system would run reports every quarter to analyze all customers at once as opposed to an EDA system tracking customers individually on their own calender - banks could respond to change in customer behavior much faster than waiting for the end of quarter to run a BI report.