1 / 28

Implementácia SOA pomocou ESB

Implementácia SOA pomocou ESB. Michal Maliarik, IBM SLK. Agenda. Komponentový prístup vs SOA Čo je to ESB SW Produkty pre implementáciu ESB Aké sú hlavne funkcie a výhody Možnosti integrácie. Tvorba aplik ácie. Funkčne orientovaná Postavené pre výkon Jeden dlhý vývojový cyklus

tavi
Download Presentation

Implementácia SOA pomocou ESB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementácia SOA pomocou ESB Michal Maliarik, IBM SLK

  2. Agenda • Komponentový prístup vs SOA • Čo je to ESB • SW Produkty pre implementáciu ESB • Aké sú hlavne funkcie a výhody • Možnosti integrácie.

  3. Tvorba aplikácie

  4. Funkčne orientovaná Postavené pre výkon Jeden dlhý vývojový cyklus Aplikačné silá Pevne viazané (tightly coupled) Štruktúrované aplikácie využívajúce komponenty a objekty Známa implementácia Procesne – servisne orientovaná Postavené pre zmeny Inkrementálny vývojový cyklus Orchestrované spolupracujúce riešenia Volne viazané (loosely coupled) Štruktúrované aplikácie využívajúce služby Implementačná abstrakcia Porovnanie funkčne a servisne orientovanej aplikácie

  5. Shape = Transport protocol Color = Data format The Enterprise Service Bus An Enterprise Service Bus (ESB) is a flexible connectivity infrastructure for integrating applications and services. An ESB performs the following between requestor and service • MATCHES & ROUTEScommunications between services • CONVERTSbetween different transport protocols • TRANSFORMSbetween different data formats • IDENTIFIES & DISTRIBUTESbusiness events

  6. Enterprise Service Bus

  7. ESB offerings from IBM WebSphereWebSphere delivers the most complete ESB solution WebSphereMessage Broker Built for universal connectivity and transformation in heterogeneous IT environments WebSphere ESBBuilt on WebSphere Application Server for an integrated SOA platform WebSphere DataPowerIntegration Appliance Purpose-built hardware ESB for simplified deployment and hardened security

  8. ESB offerings from IBM WebSphereEach delivers a common set of ESB capabilities • Mediations to enable common patterns • Transformation of common data formats • Connectivity via common protocols • Leading web services standards • First class interoperability between ESB products • Mission-critical qualities of service

  9. WebSphere MQ Reliable messaging backbone for SOA • Reliable messaging for applications and Web services • Integrates virtually any commercial IT system • Proven qualities of service and availability for mission-critical applications • Supports industry standard interfaces • Connects Web Services with non-Web Services • Ubiquitous transport to extend and underpin your ESB Enterprise Messaging Backbone: WebSphere MQ Enterprise Service Bus HP-UX Windows zLinux Solaris AIX zOS OS/400 Linux NSS OVMS

  10. Highlights of WebSphere Message Broker 6.1 • Consumability and Productivity • Reduced time to get started • Simplify debug, test, deploy tasks • Enhanced SOA Support • WS-Addressing and WS-Security built-in • DataPower as WS-Security option • WSRR Integration • Extended Connectivity • Gigabyte file support, including FTP • SAP, Siebel,PeoplSoft nodes • SMTP and JDBC Database nodes • Administration and Security • Enterprise security with LDAP and TFIM • MB Explorer and real-time performance • Numerous manageability improvements • Performance and Platform Coverage • More 64 bit platforms; JDBC XA; Java 5 • Ultra High Performance XML parser • Compacted memory footprint

  11. WebSphere Service Registry and Repository WebSphere (WAS/Portal) 3rd-party App Server provider SOAP/JMS SOAP/JMS WebSphere Message Broker SOAP/HTTP SOAP/HTTP .NET provider .NET Client XML/HTTP XML/HTTP Legacy/custom provider Some Client COBOL Copybook/MQ XML/MQ Client XML/MQ CICS IDOC/ALE Text/MQ Client Text/MQ SAP WebSphere Message Broker Scenario – Heterogeneous service mediation

  12. ODBC WAS JMS DB2 Oracle Sybase ODBC JMS FTP/ FTP over SSL Data Power XI50 3rd-partyJMS MQ 3rd Party App Server WMQ HTTP/ HTTPS WebSphere Data Power Integration Appliance XI50Scenario – Protocol bridging • First-class support for message and transport protocol bridging • Protocol mediation with simple configuration • HTTP MQ WebSphere JMS FTP Tibco EMS • Request-response and sync-async matching • Able to configure to preserve fully guaranteed, once-and-only-once delivery

  13. Customer ServiceReps Customers FTP Warehouse Application WebSphere ESB XML/JMS Service Mediations Web Applications Credit Application JDBC Business Services Customer MasterDB2 WebSphereAdapter JDBC SOAP/HTTPS Application DataOracle DB ERP System Suppliers WebSphere ESBScenario – Composite application service hosting and mediation

  14. WebSphere Service Registry and Repository Publish Govern Manage Enrich Find Service WebSphere Service Registry and Repository (3) Retrieve requestor information (4) Retrieves accurate and up-to date candidate providers information and metadata ESB Mediation Message Message Message (1) A Message is received (2) Invokes a selection mediation. (5) Executes matching algorithm to identify the provider service for requestor service (6) Message is transformed and routed to the selected endpoint.

  15. WebSphere Service Registry and Repository Publish Govern Manage Enrich Find Service Scenario - Metadata-driven Runtime Performance and health alerts are generated based on operational data and recorded in the WSRR Service Management Repositories Performance data Policies • Retrieve monitoring policy for the message from the WSRR Operational data • Mediation records the operational data about the running service Mediation • The ESB routes the message to an intermediate logging mediation or agent Message • The ESB then continues with the invocation of the service. Message • During service invocation a message is received by the ESB Message Message

  16. Analytici potvrdzujú budúcnosť viacnásobných ESB ESB Adoption Trends - Gartner “80% of large companies will have ESBs or similar SOA infrastructure products from three or more vendors in 2009. (0.7 probability)” “…half of all large companies will apply a systematic, federated approach to managing their disparate SOA domains and ESBs in 2009. (0.7 probability)” – Roy Schulte, Gartner, “Succeeding With Multiple SOA Service Domains and Disparate ESBs”, May 2007 ESB Adoption Trends - Forrester “Some of Forrester's most advanced clients got on the ESB bandwagon years ago and today find that they have an embarrassment of riches, with multiple ESBs. This outcome is almost inevitable for larger enterprises; no single ESB today can satisfy all requirements equally well across the whole of a large enterprise.” – Larry Fulton, Forrester, “Shaping Your Middleware Strategy to Benefit from ESBs, May 2007

  17. Multiple ESB Configurations Working Together Extranet Specialized Appliance HQ Data Center Branch Office Branch Office Branch Office

  18. Example of Federated ESB (I) Enterprise Secure Zone WMB V6 (distribute events) Subscribers Publishers MQ MQ Demilitarized Zone MQ DataPower XS40 WebSphere Web services Partner DataPower XI50 (Dynamically Route and log Web services) SOAP/ HTTP SOAP SOAP/ HTTP Web services for CICS Web Application TFIM WSRR

  19. Example of Federated ESB (II) Retail Store POS/Store Applications Point of Sale Terminal Lightweight commercial Java-based ESB Point of Sale Terminal Headquarters MQ MQ Mainframe DBMS Full-featured ESB with richer mediation & connectivity Retail Store MQ POS/Store Applications SOAP/ HTTP Point of Sale Terminal TP Monitor MQ SOAP/ HTTP Lightweight commercial Java-based ESB MQ MQ JMS Point of Sale Terminal Enterprise Applications J2EE Server

  20. Service Consumer Consumer Instance Service Provider Provider Instance Interaction ESB1 ESB2 Federated interaction Mediation Instance1 Mediation Instance2 Mediated interaction Mediated interaction Direct interaction Federation – Models (work in progress) • In a federated bus environment, service interactions via N buses • Can be modeled as N recursive mediated interactions: Mediated interaction == consumer -> mediation -> provider • Can be modeled as N+1 recursive direct interactions: Direct interaction == consumer -> provider • The consumer - mediation direct interaction • Can run local to the consumer, or run remote from the consumer • The mediation in a mediated interaction can offer two forms of provider address resolution • Static, using 'fixed' addresses (development or deploy time) or dynamic, using a service registry • The observations allow us to describe a simplified model of bus federation • Federation interactions treated as recursive direct interactions • Mediation instances, or virtual services, may offer dynamic target resolution via a service registry • A federated SOA can contain both local and hub-based mediations in a more or less arbitrary logical topology with physical behavior controlled by the service registry

  21. WESB and WMB

  22. ESB deployments benefit from complementary technologies Management technologies will become increasingly important to ESB deployments over the next few years, especially in large enterprise with massive SOA deployments and federation across multiple domains WebSphere Service Registry and Repository Tivoli Composite Application Manager for SOA (ITCAM for SOA) Tivoli Federated Identity Manager (TFIM)

  23. Tivoli Federated Identity Management • Provides identity and access control services that enable architects and developers to migrate identity processing out from applicationsinto reusable services • Provides standards-based, end-to-end identity translation and access control from point of contact (e.g. XML firewall) –to– mainframe (e.g. CICS) • Includes Tivoli Access Manager • TFIM makes an Enterprise Service Bus “identity aware” • WebSphere Enterprise Service Bus • WebSphere Message Broker • WebSphere DataPower Integration Appliance XI50 • ….Other ESBs (via open standards) Service A Identity = ray Identity = ray@ibm.com Service B Federated ESB Exchange this representation of this user from Service A for one that Service B will understand New representation of user identity for Service B Authorized ? Security Token Service(powered by Tivoli Federated Identity Manager) Tivoli Access Manager Yes / No

  24. ESB offerings from IBM WebSphere • WebSphere ESB: built on WebSphere Application Server for an integrated SOA platform • WebSphere Message Broker: built for universal connectivity and transformation in heterogeneous IT environments • WebSphere DataPower Integration Appliance XI50: purpose-built hardware ESB for simplified deployment and hardened security

  25. Reducing IT Complexity is Easier with an ESB • The role of the ESB is to decouple connectivity logic from application and process logic, thus making the benefits of SOA possible • IBM has the broadest ESB portfolio, plus products to extend your ESB • The IBM strategy is to provide a family of ESBs that are optimized to uniquely meet customer needs

  26. For more information… WebSphere offerings for Application Integration http://www.ibm.com/software/info1/websphere/index.jsp?tab=solutions/appintegration ESB without limits from WebSphere www.ibm.com/software/integration/esb For more IBM ESB success stories, visit: www.ibm.com/software/success

More Related