Transcript Document
Integration Scenario: Integration is the New Competitive Edge Roadmap to Competitive Advantage: Focus on Integration Massimo Pezzini Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected]. The Mission of Application Integration Business Reasons for Application Integration Regulatory compliance – – – B2B collaboration – – – EDI UCCnet Mergers and acquisitions Deploying new packaged applications Single view of Information Implementing self-service portals – Basel 2 IAS Sarbanes-Oxley Reasons That Do Not Normally Convince Executives to Invest in Application Integration Customer Employee Improve data quality Clean up messy data flows Consolidate disparate middleware products into a few strategic choices Improve documentation Provide flexibility for future application changes Conform to emerging IT standards Use the latest technology Reduce IT staff Save money in the IT department Application Integration: Making Independently Designed Applications Work Together Application1 Application2 Application Object model Data model Process model Application Object model Data model Process model Language Application server Application level: Data, business process, orchestration, semantics Middleware: Web services, JMS, J2EE,.NET, CORBA, IIOP, SQL, JDBC, ODBC DBMS OS and foundation Application integration Interoperability Language Application server DBMS Network: TCP/IP, other OS and foundation Client Issues 1. When and why will enterprise service buses (ESBs) become relevant to mainstream businesses? 2. How will companies address the three core problems of application integration: data consistency, multistep processes and composite applications? 3. Which technologies and providers will dominate the Enterprise Nervous System (ENS) during 2005 through 2010? Integration and Interoperability Strategies: Standardize or Customize Standardize Application Level Middleware Level EDI, OAG, HIPAA, SWIFT, ACORD, UCCnet, RosettaNet Customize Transform, Route, BPM, Adapters, Packaged Composite Applications, Packaged Integrating Processes, Adapter Development Toolkits Web Services, JMS, J2EE, .NET, CORBA, IIOP SQL, JDBC, ODBC Gateways: .NET-CICS, MSMQ-MQSeries SQL-SQL, SQL-IMS Application Integration Interoperability Network Level TCP/IP, SNA, SPX/IPX, DECnet, DNS Routing Tables, Configuration Using Point-to-Point Web Services Client Client Web Services "Consumers" Client SOAP/HTTP or Other Protocols Service Service Service Wrapper Web Services "Providers" Use point-to-point connections on plain Web services for: Small applications of fewer than 20 services or event types Standard service levels Moderate throughput and latency requirements All clients and services using Web services technology from the same one or two middleware providers Stable business requirements, relatively slow rate of change Using ESB Infrastructure Client Client Client Client Client Web Services "Consumers" ESB: Service Binding, Messaging, Web Services, Protocol Switching, Security, Failover, Load Balancing, Management, Monitoring, Policy Implementation Service Service Service Service Wrapper Service ENS Web Services "Providers" Use ESBs or similar ENS infrastructure for: Large applications of more than 20 services or event types Demanding service levels including reliable delivery, logging, auditing, publish-and-subscribe, SLA monitoring, high security High-throughput and low-latency requirements, non-HTTP traffic Some clients and services using non-Web-services interfaces or Web services technology from two or more middleware providers Frequent changes in business requirements, new services added, services modified, new service providers inserted ESBs Combine the Strengths of Previous Middleware TCP/IP RPC, COM, CORBA MOM Web Services April 2005 ESB Documented Interfaces and events Y Y Y Service and event registration & discovery Y Y Y ½ ½ Y Y Qualities of service ½ Y ½ Y Management ½ ½ Y ½ Industry standards SOA Interactions Event notification and other messaging Y = Yes, feature is supported Y ½ Y Y ½ = Feature is partially supported Y Y ESBs Are Helpful, but Insufficient by Themselves, for Many Integration Scenarios Personalization Portal Routing Rules BPM Userinterfacing Logic Content Mgmt. App. Server Web Server Transform, Validation Rules Process Models XSLT, XQuery BPM Mobile Devices Multichannel Gateway Event Mgmt. Rules Partner Mgmt. BEM B2B Consumers (Clients ) Integration Layer (ENS) Service binding, messaging, Web services, protocol switching, security, management, monitoring, policy implementation Enterprise Service Bus (ESB) DataFacing Logic DataFacing Logic Business Logic App. Server App. Server App. Server Service Providers Applications Are Integrated Using Three Kinds of Relationships Data Consistency Multistep Process Composite Application Composite Applications May Use an ESB, Adapters and Microflow BPM Browser Monolithic Stack Delivery Layer User-facing Logic Browser Process Models Adapter User-facing Logic Client/server SOA relationships ENS BPM ESB Data-facing Logic Datafacing Logic Datafacing Logic Datafacing Logic Service Layer Data Consistency Relationships May Use an ESB, Adapters, Routing and Transformation Event-driven relationships Adapter Transform, Validation Rules Routing Rules XSLT, XQuery Routing ENS Datafacing Logic Service Layer ESB Datafacing Logic Datafacing Logic Multistep Processes May Use an ESB, BPM/Workflow, Routing and Transformation Event-driven relationships Macroflow Business Process Transform, Validation Rules Routing Rules Workflow XSLT, XQuery Routing ENS Datafacing Logic Service Layer ESB Datafacing Logic Datafacing Logic ENS Infrastructure Product Packaging Platform-Independent Platform-Based App. Independent ESB Server Integration Suite APS Has no native portal or other delivery channels Has native portal and other delivery channels May have native portal and other channels Has native portal and other delivery channels No data-facing app. server No data-facing app. server Is a data-facing app. server Has data-facing app. server Some integration features Very broad integration features No native integration features Broad integration features Assumes most applications are packaged or legacy Assumes most applications are packaged or legacy Assumes most applications are new and run natively Assumes many applications are new and run natively Integration Is Conducted Using Many Different Technologies CEP Virtual DBMS Integration Suites APS ETL Tools Stand-Alone ESB Packaged Adapters Gateways Programmatic Integ. Servers Portals Screen Scraping Simple Integration Projects Complex Factors No. of apps. No. of messages per day Integration style No. of business units No. of dev. teams Scope (A2A, B2B) Budget Recommendations To meet the escalating requirements of modern business, every company must have: An application integration strategy An integration competency center A comprehensive ENS middleware infrastructure Use business component architecture in all major new applications. Prepare for event-driven applications: the "next big thing." Add an ESB to your IT strategic plan and application architecture. Integration Scenario: Integration is the New Competitive Edge Roadmap to Competitive Advantage: Focus on Integration Massimo Pezzini Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected]. Integration Scenario: Integration is the New Competitive Edge Roadmap to Competitive Advantage: Focus on Integration Massimo Pezzini Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected].