Roadmap to Competitive Advantage: Focus on Integration

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 — quote.requests@gartner.com.

Integration Scenario:Integration is the New Competitive Edge

Massimo Pezzini

Business Reasons for Application Integration

Regulatory compliance– Basel 2– IAS– Sarbanes-Oxley

B2B collaboration– EDI– UCCnet

Mergers and acquisitions Deploying new packaged

applications Single view of Information Implementing self-service portals

– Customer– Employee

Improve data quality

Reasons That Do Not Normally Convince Executives to Invest in Application Integration

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

The Mission of Application Integration

Application level: Data, business process, orchestration, semantics

Middleware: Web services, JMS,J2EE,.NET, CORBA, IIOP, SQL, JDBC, ODBC

Network: TCP/IP, other

Application Integration: Making Independently Designed Applications Work Together

OS and foundation

DBMS

Application Object

model Data

model Process

model

Applicationserver

Language

DBMS

Application Object

model Data

model Process

model

Applicationserver

Language

OS and foundation

Application1 Application2

Applicationintegration

Interoperability

Client Issues

1. When and why will enterprise servicebuses (ESBs) become relevantto mainstream businesses?

2. How will companies address the threecore problems of application integration:data consistency, multistep processesand 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

Middle-wareLevel

Appli-cation Level

ApplicationIntegration

NetworkLevel

Interoperability

EDI, OAG,HIPAA, SWIFT, ACORD, UCCnet, RosettaNet

Web Services, JMS,J2EE, .NET, CORBA,IIOP SQL, JDBC, ODBC

Standardize

TCP/IP, SNA, SPX/IPX,DECnet, DNS

Customize

Transform, Route, BPM, Adapters, Packaged Composite Applications, Packaged Integrating Processes,

Adapter Development Toolkits

Gateways: .NET-CICS, MSMQ-MQSeries

SQL-SQL, SQL-IMS

Routing Tables,Configuration

Using Point-to-Point Web Services

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

Web Services"Providers"

Web Services

"Consumers"

SOAP/HTTP or Other Protocols

Service

Client

Wrapper

Client Client

Service Service

Using ESB Infrastructure

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

Web Services"Providers"

Web Services

"Consumers"

Service

Client

Service Service Service Wrapper Service

Client Client Client Client

ESB: Service Binding, Messaging, Web Services, Protocol Switching, Security, Failover, Load Balancing, Management, Monitoring, Policy Implementation ENS

ESBs Combine the Strengthsof Previous Middleware

TCP/IPRPC, COM,

CORBA MOMWeb Services

April 2005 ESB

Documented Interfaces and events Y Y Y

Service and event registration & discovery Y Y Y

Industry standards Y ½ ½ Y Y

Qualities of service ½ Y ½ Y

Management ½ ½ ½

SOA Interactions Y ½ Y Y

Event notificationand other messaging Y Y

Y = Yes, feature is supported ½ = Feature is partially supported

ESBs Are Helpful, but Insufficient by Themselves, for Many Integration Scenarios

IntegrationLayer (ENS)

Service binding, messaging, Web services, protocol switching, security, management, monitoring, policy implementation

Enterprise Service Bus (ESB)

Consumers (Clients )

Person-alization

Portal

User-interfacing

Logic

App. Server

ContentMgmt.

Web Server

MobileDevices

Multichannel Gateway

ServiceProviders

Data-FacingLogic

App. Server

Data-FacingLogic

App. Server

BusinessLogic

App. Server

RoutingRules

BPM

Transform,Validation

Rules

XSLT, XQuery

ProcessModels

BPM

EventMgmt.Rules

BEM

PartnerMgmt.

B2B

Applications Are Integrated Using Three Kinds of Relationships

Composite Application

Data Consistency

Multistep Process

Data-facingLogic

Data-facingLogic

Data-facingLogic

ProcessModels

BPM

Composite Applications May Use an ESB, Adapters and Microflow BPM

ServiceLayer

ENS

DeliveryLayer

User-facingLogic

Data-facingLogic

Browser

ESB

Adapter

Client/server SOArelationships

MonolithicStack User-facing

Logic

Browser

Data Consistency Relationships May Usean ESB, Adapters, Routing and Transformation

Transform,Validation

Rules

XSLT, XQuery

Data-facingLogic

Data-facingLogic

Data-facingLogic

ESB

Adapter

Event-driven relationships

RoutingRules

Routing

ServiceLayer

ENS

Multistep Processes May Use an ESB, BPM/Workflow, Routing and Transformation

Transform,Validation

Rules

XSLT, XQuery

Data-facingLogic

Data-facingLogic

Data-facingLogic

ESB

RoutingRules

Routing

MacroflowBusinessProcess

Workflow

Event-driven relationships

ServiceLayer

ENS

Platform-Independent Platform-Based

ENS Infrastructure Product Packaging

Independent ESB

Has no native portal or other delivery channels

No data-facing app. server

Someintegration features

Assumes most applications are packaged or legacy

Integration Suite

Has native portal and other delivery channels

No data-facing app. server

Very broad integration features

Assumes most applications are packaged or legacy

App. Server

May have native portal and other channels

Is a data-facing app. server

No native integration features

Assumes most applications are new and run natively

APS

Has native portal and other delivery channels

Has data-facing app. server

Broad integrationfeatures

Assumes many applications are new and run natively

Integration Is Conducted Using Many Different Technologies

Simple Integration Projects Complex

Virtual DBMS

Packaged Adapters

Stand-Alone ESB

Integration Suites

Screen Scraping

Programmatic Integ. Servers

Gateways

Portals

ETL Tools

APS

CEPFactors No. of apps. No. of

messagesper 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 planand application architecture.

Roadmap to Competitive Advantage: Focus on Integration

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 — quote.requests@gartner.com.

Integration Scenario:Integration is the New Competitive Edge

Massimo Pezzini

Roadmap to Competitive Advantage: Focus on Integration

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 — quote.requests@gartner.com.

Integration Scenario:Integration is the New Competitive Edge

Massimo Pezzini