Building Enterprise Services, Using the Enterprise Service Bus (ESB) and Data Transformation Appliance

Transcription

1 Building Enterprise Services, Using the Enterprise Service Bus (ESB) and Data Transformation Appliance Narayan Chintalapati Application Architect/ Director, ebusiness Marriott International David Hecksel Senior SOA Architect Oracle Corporation BOF JavaOne SM Conference Session 8484

2 Session Goal Explain ESB Technology in general and explain the evolution of SOA and the use of ESB in a major travel related company 2007 JavaOne SM Conference Session

3 Agenda Why ESB? ESB Competitive Landscape Requirements and Architecture of Travel Company ESB and related products ESB and Data Transformations Data Power Appliance and advantages ESB Demo Q&A 2007 JavaOne SM Conference Session

5 Why ESB? ESB is an architectural pattern that addresses end-end integration challenges JavaOne SM Conference Session

6 Why ESB? Data Transformation Canonical Data Protocol Transformation Virtualizing Endpoints Service Virtualization and Routing Consolidating multiple BPM Integration implementations Common Services Separate integration from application/business logic 2007 JavaOne SM Conference Session

7 Why ESB? Usage Patterns Data Transformation Web Application Customer DB Customer ESB Customer 2007 JavaOne SM Conference Session

8 Why ESB? Data Transformation Convert data as it flows through the bus Canonical or point-to-point transformations Standard XSLT for expressing transformations Drag-and-drop graphical mapping tool Smart mapping tool, dictionary-based Domain-Value Maps for fast, static, in-memory lookups 2007 JavaOne SM Conference Session

9 Why ESB? Usage Patterns: Canonical Data Model All messages on the bus are converted to a common data model Reduces the overall number of maps to generate Respective application owners only need to know about 2 data models: their own one + the canonical one. CRM Marriot.com CRM Marriot.com COMMON DATA MODEL (Customer Object) Rewards Billing Rewards Billing 2007 JavaOne SM Conference Session

10 Why ESB? Usage Patterns Protocol Transformation Marriot.com SOAP JMS Marriot Rewards ESB 2007 JavaOne SM Conference Session

11 Why ESB? Virtualizing Endpoints: Connecting to Target Systems Web Services: PeopleSoft, Amazon, Applications: e-business Suite, SAP, Peoplesoft, Legacy: CICS, Tuxedo, Technologies: database, file, JMS, Non-WS Connectivity through Adapters Standard JCA 1.5 Transactional (whenever possible) Wizards-driven, graphical introspection of target systems Adapters Bundled with ESB AQ, MQ, RDBMS, File, FTP, JMS, MQ, Oracle Applications and 300+ more available via OEM (iway, Attunity)! 2007 JavaOne SM Conference Session

12 Why ESB? Usage Patterns Virtualizing Endpoints Host: , Port:2320 Marriot Rewards Native API [proprietary protocol] Native API CRM Marriot Rewards CreateCustomer.wsdl [SOAP] JCA Adapter Native API Host: Port:2320 [proprietary protocol] Native API CRM ESB Service consumers no longer need to talk proprietary protocols 2007 JavaOne SM Conference Session

13 Why ESB? Usage Patterns Service Virtualization and Routing Marriot.com Courtyard Renaissance Marriot.com SOAP ESB 2007 JavaOne SM Conference Session

14 Why ESB? Consolidating multiple BPM Integration implementations Process 1 DB 3 rd Party Vendor DB 3 rd Party Vendor Process 2 ESB Audit DB DB 3 rd Party Vendor Business process remains unchanged Audit DB added 2007 JavaOne SM Conference Session

16 ESB Competitive landscape - There are a number of ESB vendors in the market: - IBM - Oracle - Sonic - BEA - Sun - Open Source - In this presentation we do not want to present a solution specific to a vendor - But to give an in depth technical presentation we reference IBM and Oracle ESB solutions 2007 JavaOne SM Conference Session

18 Requirements of Travel Company - Reservation System (Marriott.com): - A J2EE based web application - Integrates with back end mainframe system using xml/http - Integrates with Rewards J2EE system using xml/http - Uses Vignette content management system and Java api - External vendors interact with mainframe reservation system using xml/http transactions 2007 JavaOne SM Conference Session

19 Requirements of Travel Company - Need to standardize interfaces for internal and external facing applications - Use existing application implementation as much as possible - Centralize transformations and re-use transformations if possible - Centralize security - Not all applications will be ready for standard interfaces at the same time 2007 JavaOne SM Conference Session

20 Current Architecture Reservation Agent System Property Information System Enterprise Java Beans (EJBs) Web Services Reservation Web Application (Marriott.com) Xml/http Xml/https Xml/http Xml/http WebServices Rewards J2EE System Vendors Reservation Legacy System JMS System JMS Map Extenal System 2007 JavaOne SM Conference Session

21 Enterprise Services Governance Rules Technical services team approves Enterprise Services provided that: All WSDLs must conform to the published WSDL/XML standards All published WSDLs will compile using standard tools, these tools can be Java and/or non-java based All Services that the published WSDL exposes undergo required testing. Performance test plans and results are published to the Service Repository All Services meet a published set of criteria (granularity, stateful, stateless etc.) published by the technical services team JavaOne SM Conference Session

22 Enterprise Services Governance Guidelines The following guidelines are followed by the application teams when creating Enterprise Services. Acceptable and unacceptable implementation types are published and segmented by existing or new Service 2007 JavaOne SM Conference Session

23 Enterprise Services Governance Guidelines For existing Services, if the Service is an acceptable implementation type, then implementation need not change. Any implementation changes must be justified. New Services must be SOAP based For existing services, if the functionality is changing significantly, every effort must be made to make the implementation SOAP based. Application project managers must build the time it takes for services approval into their project plans. Not having enough time cannot be a reason to approve services that do not meet the above criteria JavaOne SM Conference Session

24 Acceptable Implementations SOAP JMS XML/HTTP(S) RMI/IIOP EJB 2007 JavaOne SM Conference Session

25 Unacceptable Implementations Flat Files FTP CICS Sockets The above implementations cannot be exposed to the consumers or callers of Enterprise Services. Service providers can use the above existing implementations if there are no significant changes 2007 JavaOne SM Conference Session

26 To Be Architecture UDDI Software and Hardware ESB Transformations Routing Complex Transformations Common Services Web Services Portal Vendors EDI-INT/SFTP/ ebxml/uccnet/soap/xml over https B2B and B2G Server Web Services xml over http Enterprise Java Beans (EJBs) xml over http Xml/http Web Services JMS Authentication System Web Services Reservation Web Application (Marriott.com) Reservation Agent System Rewards J2EE System System Map External System Xml/https Property Information System Reservation Legacy System 2007 JavaOne SM Conference Session

28 ESB and Related Products - As with any other vendor, IBM ESB product suite can be confusing - The IBM software stack: - WebSphere Application Server Network Deployment - WebSphere Process Server - WebSphere ESB - WebSphere Message Broker - WebSphere MQ - DataPower XI50 - WSRR, Registry and Repository 2007 JavaOne SM Conference Session

29 Oracle ESB and Related Products - The Oracle SOA software stack: - Business Process Analysis Suite - Architect, Repository, Simulator, Publisher - SOA Suite - BPEL Process Manager - Enterprise Service Bus (ESB) - Business Activity Monitoring (BAM) - Business Rules - Web Services Manager - Oracle Service Registry 2007 JavaOne SM Conference Session

30 Agenda Why ESB? ESB Competitive Landscape Architecture of Travel Company Web Sphere ESB and related products ESB and Data Transformations Data Power Appliance and advantages ESB Demo Q&A 2007 JavaOne SM Conference Session

31 ESB and Data Transformations - An example of data transformation can to convert all instances of htl into hotel or convert, into ; - Now the next question is should ESB do these transformations - Our recommendation is to keep business logic with the application and do minor data transformations in ESB - How about transformations between xml formats, xmlother formats? - Consider the following two examples on the next pages - ESB containers are very good at doing this kind of transformations and we must do these transformations in ESB 2007 JavaOne SM Conference Session

32 Protocol Transformations - This is a very powerful feature within most ESB products - ESB can convert between SOAP, http, JMS, ftp, EJB, RMI - For example if there an EJB interface then having an ESB between the EJB application and the client will let us call the EJB in SOAP Services or http - This will let us change the applications gradually to be SOA or in some cases there will be no need to change the applications - In the previous slides we talked about acceptable and unacceptable interfaces. There is no need to change acceptable interface, only change unacceptable interfaces to be Service governance compliant 2007 JavaOne SM Conference Session

33 Security - Role based security can be enforced at ESB layer thus making the applications not worry about security - Encryption/Decryption can also be done at ESB level - WS-I security can be enforced using ESB 2007 JavaOne SM Conference Session

34 Versioning - What happens if an interface changes and some applications are not ready for the new versions - Making both versions of the Service can be done at the ESB level - This will let the application migrate to newer versions of the Service over time - Multiple Service definition versions are stored in a Registry 2007 JavaOne SM Conference Session

36 Data Transformations using Appliance - Using a hybrid of software and hardware solution for data transformations is a new trend that can make transformations very fast thus reducing the perceived latency of SOA - Data transformations can be complicated and take lot of CPU cycles - Appliance can centralize the transformations and do it at almost wire speed adding very little transformation overhead 2007 JavaOne SM Conference Session

37 Data Transformations using Appliance - Data Power Appliance has a very low foot print and is similar to a firewall router rather than a middleware component - Data Power Appliance supports server side and mutual SSL - Appliance supports load balancing and can alternatively work with an external load balancer - Configuring the appliance is more like configuring a load balancer, requires systems level technical skills 2007 JavaOne SM Conference Session

38 Data Transformations using Appliance Integration Appliance XI50 - XML Parsing - XML Schema Validation - XML Transformation - Schema, Stylesheet caching - Multistep processing - XML Path Language (XPath) Content Based Routing - Extensible Stylesheet Language Transformation (XSLT) - XML and SOAP Firewall - Data Validation - Field Level XML Security - WS-Security - XML Web Services Access Control - Integration with 3 rd party security providers - Web Services Management - Service Virtualization - Any-to-Any Transformation Engine - Binary or flat text XML - XML binary or flat text - Binary binary - XML XML - Protocol Bridging (HTTP,MQ, FTP, etc.) - Message Enrichment, message augmentation 2007 JavaOne SM Conference Session

39 Data Transformations using Appliance Software ESB Hardware ESB Appliance Common Services Transformations Complex Transformations Applications - Applications connect to hardware appliance for transformations - Hardware appliance is not a java container and cannot provide more sophisticated transformations or interfaces like EJB etc - Any common services are also provided by software ESB - For more sophisticated interfaces and transformations applications connect to software ESB 2007 JavaOne SM Conference Session

40 Agenda Why ESB? ESB Competitive Landscape Architecture of Travel Company Web Sphere ESB and related products Data Power Appliance and advantages ESB and Data Transformations ESB Demo Q&A 2007 JavaOne SM Conference Session

41 Summary ESB is a great technology if used wisely ESB should be used as an application platform based on our experience Consult your Security Architecture team to determine how best to protect ESB Services and conform to your Security Architecture Consider using an appliance for transformations ESB should be used as integration back bone 2007 JavaOne SM Conference Session

42 Agenda Why ESB? ESB Competitive Landscape Architecture of Travel Company Web Sphere ESB and related products Data Power Appliance and advantages ESB and Data Transformations ESB Demo Q&A 2007 JavaOne SM Conference Session

43 Q&A SOA Suite and JDeveloper Get started today - Free download, fully functional JavaOne SM Conference Session XXXX 4 3