Introduction to Business Integration &
`Message Brokers
`Mark Swinson
`
`Las Vegas, Nevada June 12-16, 2000
`
`HP_1028_0001
`
`
`Message Brokers
`Mark Swinson
`
`Las Vegas, Nevada June 12-16, 2000
`
`HP_1028_0001
`
`
`
`Objectives & Agenda
`
`Integration: Combination into a whole
`
`Objectives:
`Provide an introduction to Business Integration and explain the "why and how" of
`message brokers
`Survey analyst and customer views on business integration and the march towards
`e-business
`
`Agenda:
`An introduction to integration... application integration
`Integration matures... brokered integration
`Integration gets sophisticated... new technologies
`The wide wide world of business integration... enabling the world of e-Business
`
`HP_1028_0002
`
`
`
`The Application Environment: History
`
`The application environment has changed through the
`’90s:
`Away from centralised, monolithic...
`To distributed, modular, client/server applications
`Increasing use of packaged applications
`New e-business applications - B2B & B2C
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0003
`
`
`
`Application Integration: History
`
`Integration requirements have changed and evolved:
`Initially middleware was a means to tie new systems
`into legacy applications
`Bridge the gap between disparate systems
`As adoption of ERP increased, middleware connected
`subsystems from different vendors
`As ERP extends into supply chain and CRM - often
`through acquisition - middleware is used inside systems
`e-business drives the need for front to back-end
`integration
`Integration across the supply chain
`Zero latency is the goal
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0004
`
`
`
`Application Integration: Quotes from Analysts
`
`Enterprise Application Integration
`Enterprise Application Integration as important as the introduction of databases in the 80s
`and ERP systems in the 90s (Computer Business Review, 11/98)
`30% of entire IT budget is spent on building, maintaining & supporting application integration
`(Forrester)
`35% of application deployment is dealing with spaghetti" (Gartner)
`
`ERP
`For every $1 spent on software, $9 is spent to integrate it (Fortune magazine)
`90+% of applications to be integrated are not ERP’s (Gartner)
`ERP offers only 30% of function needed (Gartner)
`90% of ERP implementations end up late or over budget (Standish)
`
`Message Brokers (Gartner)
`The market is beyond the Type A (innovative) customers ...Type C (wait-&-see,
`conservative) are being forced...by merger & acquisition
`By 2001, message brokers will be involved in >25% of all Web-based integration solutions
`By 2001, 50% of Type A enterprises will use message brokers
`
`HP_1028_0005
`
`
`
`Application Integration: Approaches
`
`Much integration is undertaken piecemeal for a number
`of reasons:
`Multiple dimensions of application incompatibility
`Operating systems
`Databases
`TP monitors
`Data models & semantics
`Pressure to solve immediate business problem
`Difficult to measure Return on Investment for
`strategic/visionary approaches
`Integration sophistication tends to increase
`Linking systems introduces new problems:
`Co-ordination of data
`Resolution of inconsistencies
`
`HP_1028_0006
`
`
`
`Interapplication Spaghetti
`
`Gartner coined the term ’Interapplication spaghetti’ to
`describe the complex web of point-to-point connections
`arising from piecemeal integration
`
`Application B
`
`Down-
`load
`File
`
`Extract
`Program
`
`Load
`Program
`
`Screen
`Scrape
`
`Program
`
`Program
`
`Message
`queue
`
`Trans-
`action
`file
`
`Extract
`Program
`
`Load
`Program
`
`Down-
`load
`File
`
`Program
`
`Program
`
`Database
`replicator
`
`Extract
`Program
`
`Message
`queue
`
`Application C
`
`Down-
`load
`File
`
`Load
`Program
`
`Trans-
`action
`file
`
`Program
`
`Program
`
`HP_1028_0007
`
`
`
`Spaghetti Integration
`
`The results of implementing piecemeal integration and
`building interapplication spaghetti are:
`Costly and time consuming to maintain
`Particularly if critical knowledge is with few staff
`Reconciling inconsistencies in data from different
`sources is difficult
`Inconsistent reconciliation policies arise exacerbating
`problems
`Tracking/auditing data & flow is very difficult
`
`HP_1028_0008
`
`
`
`Message Oriented Middleware:
`Value Propositions
`MOM facilitates application connectivity because it
`provides:
`Asynchronous connection
`Applications do not need to be available to service
`requests immediately
`Applications can process work in parallel
`Accessing multiple servers
` Environment independence
`Programmers work with a consistent API across
`multiple platforms: O/S, network, communications
`protocol
`MQSeries is an example of ’Message Oriented
`Middleware’ (MOM)
`
`HP_1028_0009
`
`
`
`MOM: The Application Burden
`
`MOM does not solve all of the application developer’s
`problems...
`The application needs to handle:
`Data formatting
`Collecting and structuring data to send in a message
`Interpreting structured data arriving in a message
`Quality of service
`Deciding how the message should be handled
`Persistence, security, CoD, etc
`Message routing and distribution
`Deciding on the route(s) and destination(s) for the
`message
`
`HP_1028_0010
`
`
`
`MQSeries: Increasing the Value of MOM
`
`Data formatting services
`MQSeries Common Message Interface (CMI)
`Relieve application from dealing with data structure:
`Deal with fields via API
`Externalise parser & dictionary from application
`Flexibility to modify/change parser/dictionary without
`impacting application
`Routing and Quality of Service
`MQSeries Application Messaging Interface (AMI)
`Externalise configuration of destination(s) and QoS
`options from application
`Simplify application code
`New interface options
`eg simple file handling
`
`HP_1028_0011
`
`
`
`Message Routing and Distribution:
`Message Brokers
`The message broker:
`An intelligent 3rd party between applications
`A logical hub that processes messages:
`Message handling is specific to the needs of producers
`and consumers
`Based on reusable components & GUI-based tools
`A point for consolidation of data from multiple sources
`Messages, databases, applications, objects
`Leads to an alternative classification: Integration Broker
`A point for management and control
`Definition of business relationships
`Auditing
`Monitoring
`Data structure and semantics: Metadata dictionary
`
`HP_1028_0012
`
`
`
`Brokered Integration
`
`“In-House”
`Customer Service
`Application
`
`Client
`
`Client
`
`Program
`
`Program
`
`Change
`Customer Contact
`
`Program
`Level
`
`Purchased
`Financials Package
`
`Program
`
`Program
`
`Data
`Level
`
`Import New Parts Catalog
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0013
`
`
`
`Publish/Subscribe and Message Brokers
`
`A few words about pub/sub:
`The aim of pub/sub is to separate producers of information from consumers
`Producers are unaware of the needs of consumers
`Consumers are unaware of the source(s) of information
`Message brokers can implement pub/sub
`Consumers register subscriptions and route publications accordingly
`Centrally controllable but allows autonomy
`Alternative approach is bus or broadcast
`All data sent to all consumers
`Consumers filter data to discard unwanted
`
`Broker
`
`Bus
`
`HP_1028_0014
`
`
`
`Importance of IT Benefits from
`Application Integration
`
`Increase IT flexibility,
`quality, and responsiveness
`
`Decrease elapsed time to
`field for new system
`
`Improve relations with user
`departments
`
`Reduce person-hours per
`new interface
`
`Replace hardware or communications
`infrastructure requirements
`
`Replace software (eg EDI or middleware
`replaced by application integration tool)
`
`Source:
`Gartner Group
`AI Study
`March 2000
`
`0
`
`1
`
`2
`
`3
`
`4
`
`5
`
`HP_1028_0015
`
`
`
`Application Integration Benefits Are Qualitative
`
`Many organisations found it difficult to establish a direct
`link between AI and business benefits
`Most benefits are derived from broader business and
`technology initiatives, to which AI is an important, but
`not dominant contributor
`Most benefits have only a second order economic
`impacts:
`IT departments can respond more quickly to business
`requirements; if the business changes are
`revenue-generating or cost saving, AI contributes to the
`benefit
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0016
`
`
`
`But Who Owns the Integration Problem?
`
`The real problem is that no group is stepping up to own the integration
`opportunity...
`
`To quote from customers interviewed by Forrester:
`"The largest challenge we face in implementing real-time integration is the
`administrative overhead for messaging. We don’t have the resources for a
`full-time employee to monitor the queue so we can be proactive in a bad
`situation." (Insurance company)
`"Our challenges have centred on time constraints and technology issues. We
`have so many other projects going on that it is very difficult to find the time to
`do this sort of integration. We have been struggling with the middleware and
`the tuning and testing that’s involved." (Retail company)
`"We want to get the different development groups excited about connecting
`their apps to those in other parts of the company. The problem is that they
`have so much on their plates. Often, their focus is on the immediate demands
`of maintaining their systems. They are less concerned with making their
`systems talk to others." (Industrial equipment company)
`
`Source: Forrester Research "Integrating Business Processes", March 1999
`
`HP_1028_0017
`
`
`
`Centralisation Issues
`
`Centralising integration logic in a message broker is
`good for a number of reasons...
`See previous charts
`But there are some drawbacks...
`Single point of failure
`Potential bottleneck
`Shared control may be necessary
`Security implications
`Mitigation strategies include:
`Multiple instances of a single configuration
`Clustering - MQ and o/s / hardware
`Federation
`Share responsibilities between multiple brokers (often
`by function or geography)
`
`HP_1028_0018
`
`
`
`Complexity Issues
`
`Back to a previous point: Integration sophistication
`tends to increase:
`Integration creates alternative data sources and sinks
`Linking systems creates new dependencies and
`relationships
`Expose inconsistencies and introduce management
`issues
`Handling integration complexities can be as big a
`problem as integration
`Leads to "transactional choreography"
`Long running, multi-participant,
`heterogeneous interactions
`between applications
`
`HP_1028_0019
`
`
`
`Transactional Choreography
`
`Aggregating multiple responses
`Building one answer to a question with several parts
`Defining scenarios to handle error conditions:
`Multiple updates; one fails: How to ’roll back’ the others
`Timed events: What happens if an operation does not
`complete within a deadline
`Involve people where necessary & stay within the
`solution
`Introducing people brings us into workflow
`Defined roles and relationships
`Defined tools and applications to handle work
`Essentially the difference between a "technical
`transaction" and a business transaction
`
`HP_1028_0020
`
`
`
`Making Sense of the Bigger Picture:
`Business Process Modelling
`
`Business
`Process
`Modelling
`
`Application
`Architecture
`
`Application
`Design
`
`HP_1028_0021
`
`
`
`New technology: New Dimensions to Integration
`
`Developments in technology and
`standards are introducing new
`dimensions to integration:
`XML - a "lingua franca" for integration
`A flexible structure for self-describing
`data
`An overhead in passing data around
`A moving target!
`The potential for universal data access
`Pervasive devices
`A new scaleability challenge
`Requirements for security and content
`transformation
`
`<?xml version="1.0" standalone="no"?>
`
`<!--
` $Revision: 6.0.1 $
` $Date: 07 December 1998 $
` Open Applications Group Sample XML Data
` Copyright 1998, All Rights Reserved
` $Name: 010_get_po_003.xml $
` 6.0.0 12/07/98 Initial Release
`-->
`
`<!DOCTYPE GET_PO_003 SYSTEM "010_get_po_003.dtd">
`<GET_PO_003>
`<CNTROLAREA>
`<BSR>
`
`<VERB>GET</VERB>
`<NOUN>PO</NOUN>
` <REVISION>003</REVISION>
`</BSR>
`<SENDER>
`<LOGICALID>CPAG</LOGICALID>
`<COMPONENT>PURCHASING</COMPONENT>
`<TASK>POISSUE</TASK>
`<REFERENCEID>CPAGPOBERLIN02</REFERENCEID>
`<CONFIRMATION>0</CONFIRMATION>
`<LANGUAGE>EN</LANGUAGE>
`<CODEPAGE>CP000111</CODEPAGE>
`<AUTHID>RSCHULTE</AUTHID>
`</SENDER>
`<DATETIME qualifier = "CREATION" >
`<YEAR>1996</YEAR>
`<MONTH>12</MONTH>
`<DAY>07</DAY>
`<HOUR>16</HOUR>
`<MINUTE>08</MINUTE>
`<SECOND>59</SECOND>
`<SUBSECOND>0000</SUBSECOND>
`<TIMEZONE>+0100</TIMEZONE>
`</DATETIME>
`</CNTROLAREA>
`<DOCUMENT>
`<GET_PO>
` <POHEADER returndata = "1">
`
`<POID>PO12345</POID>
`</POHEADER>
`<POLINE returndata = "1"/>
`</GET_PO>
`</DOCUMENT>
`</GET_PO_003>
`
`HP_1028_0022
`
`
`
`New technology: New Dimensions to Integration
`(cont)
`
`e-business / e-commerce / B2B / B2C
`Co-ordination between enterprises
`Predefined and ad-hoc
`Alignment of data syntax and semantics
`Application servers
`Bridging the object world to the asynchronous world
`Leverage scaleability, performance, robustness & development tools
`Leverage business logic in other domains
`
`Internet
`Internet
`Order
`Order
`
`Customer
`Customer
`
`Telephone
`Telephone
`Order
`Order
`
`Reseller
`Reseller
`
`SitesSites
`
`Inventory
`Inventory
`Flow of orders
`Flow of orders
`Available-to-promise
`Available-to-promise
`Order Status
`Order Status
`Shipping Information
`Shipping Information
`
`Internet
`Internet
`
`Contract
`Contract
`Manufacturer
`Manufacturer
`
`Product
`Product
`Delivery
`Delivery
`
`Application Server Software
`
`WebSphere
`Transaction Mgmt &
`Distributed Objects
`
`DB2 UDB
`
`e-business
`Application
`
`Domino
`Collaboration
` & Workflow
`
`WebSphere
`Application
`Adapters
`
`MQ Integrator
`& Workflow
`
`DataJoiner
`
`& Propagator
`
`MQSeries
`
`Connectors
`
`HP_1028_0023
`
`
`
`The Future? Process Integration Servers
`
`A "wide-angle" view of the business:
`Treat existing applications as process
`"components"
`Exposing business events driving
`packaged/legacy app’s, monolithic
`systems become suites of rich corporate
`services
`Allows corporate app’s - and underlying
`business functions they support - to be
`rapidly deployed and redeployed without
`significant disruption
`Knit process components together into new
`business offerings
`New apps can draw from resources across
`the company - and from third parties -
`while presenting a consistent interface and
`current data.
`
`Source: Forrester Research "Integrating Business Processes", March 1999
`
`HP_1028_0024
`
`
`
`Process Integration Servers
`
`Process integration servers consist of:
`Reliable communication
`Asynchronous, synchronous, and transactional connections
`Component platform technologies like Enterprise JavaBeans and Microsoft’s
`COM+, and interfaces to multiple middleware services
`Adapters to make the application connection
`Connections via lightweight, non-invasive adapters to take existing corporate
`apps "as is"
`Adapters for standards like SQL and XML and packages like SAP, PeopleSoft,
`and Manugistics
`Tool kits to minimise custom interface code by configuring most event and
`data translation through centrally managed metadata
`A robust engine for managing process flow
`Interprets and forwards events based on the rules of the business process
`Multiple servers distribute and share the load for performance and fault
`tolerance
`Tools for the business analysts
`Process integration development tools
`
`Source: Forrester Research "Integrating Business Processes", March 1999
`
`HP_1028_0025
`
`
`
`What is being Integrated?
`
`Extending core business processes to embrace
`customers and suppliers.
`Transformation of business processes, such as
`supply chain management and customer relationship
`management.
`
`CUSTOMERS
`
`ENTERPRISE RESOURCES
`
`Supply
`Chain
`Management
`
`Enterprise Resource
`Planning
`Back Office
`
`Customer
`Relationship
`Management
`
`Business Integration
`(inter/intra-enterprise)
`
`S UP P L I ER S
`
`HP_1028_0026
`
`
`
`Forces Driving e-Business Integration
`
`Technology
`
`Globalisation
`
`1. Mergers &
`1. Mergers &
`acquisitions
`acquisitions
`2. Packaged
`2. Packaged
`application
`application
`integration
`integration
`(ERP)
`(ERP)
`3. Customer
`3. Customer
`Relationship
`Relationship
`Management
`Management
`
`integration
`
`4. Supply chain
`4. Supply chain
`5. Straight-through
`5. Straight-through
`processing
`processing
`6. Web Integration
`6. Web Integration
`
`Cost & Cycle Time
`
`Competition &
`Consumer power
`
`HP_1028_0027
`
`
`
`Integration Brokers are More Widely Used Among
`Companies Integrating e-Business Functions
`
`36% of respondents who are integrating e-business
`applications are implementing integration brokers; only
`21% of respondents not focused on e-business are
`implementing integration brokers
`GartnerGroup believes there are two key drivers of
`more widespread use of integration brokers for
`e-business:
`Companies integrating e-business applications are
`more likely to be early technology adopters
`E-business integration is more likely to touch on
`multiple systems, and is therefore more likely to require
`the management and workflow functionality of
`integration brokers.
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0028
`
`
`
`Business Integration: Customer Stories
`
`"We are shortening up the supply chain to achieve more efficient
`management of inventory and procurement, and faster order
`and delivery."
`"We are tying our supply chain into our transactional systems."
`"We are providing a single, consistent interface to our customers
`to all our systems."
`"We’ve given the customer a more consolidated picture of their
`relationship with us."
`"A claim for a lost check has gone from one and a half months to
`ten days. It used to take two weeks to pay a bill, now it takes
`two days."
`"Integration has enabled us to effectively take orders over the
`Internet."
`
`Source: Gartner Group AI Study, March 2000
`
`HP_1028_0029
`
`
`
`Business Information Exploitation
`with MQSeries
`
`Business event
`query stock
`update customer
`record
`
`access ERP package
`
`calculate discount and convert to £
`
`publish new address details
`
`Mobile
`Mobile
`
`WebSphere
`WebSphere
`
`Adapters
`Adapters
`andand
`Gateways
`Gateways
`
`CRMCRM
`
`SCMSCM
`
`Business Information
`Broker
`
`Information
`Visualization
`Enrichment
`Transformation
`Routing
`Pub/sub
`
`Meta-data
`Repository
`XMLXML
`Custom
`Custom
`Industry
`Industry
`
`CICSCICS
`ERPERP
`
`Adapters
`Adapters
`andand
`Gateways
`Gateways
`
`DB2DB2
`
`B2BB2B
`
`HP_1028_0030
`
`
`
`Business Process Exploitation
`with MQSeries
`
`
`Sequence of
`business events
`Order
`Order
`Entry
`Entry
`
`Credit
`Credit
`Check
`Check
`
`Supply
`Supply
`Check
`Check
`
`Invoice
`Invoice
`
`Shipping
`Shipping
`
`Mobile
`Mobile
`
`WebSphere
`WebSphere
`
`Adapters
`Adapters
`andand
`Gateways
`Gateways
`
`CRMCRM
`
`SCMSCM
`
`Business Process
`Broker
`
`Activity Visualization
`Flow sequencing
`Time activities
`Staff activities
`
`CICSCICS
`ERPERP
`
`Adapters
`Adapters
`andand
`Gateways
`Gateways
`
`DB2DB2
`
`B2BB2B
`
`Meta-data
`Repository
`
`Business
`process
`Flow
`definitions
`
`HP_1028_0031
`
`
`
`MQSeries Software Platform
`Addresses Business Integration
`
`SCM
`
`Legacy
`Web &
`
`
`
`CRM
`
`ERP
`
`Foundation
`Foundation
`... to extend the reach
`... to extend the reach
`
`MQSeries
`MQSeries
`Integration Foundation
`Integration Foundation
`
`Foundation Services
`Foundation Services
`... to make it easy
`...
`to make it easy
`
`Transform
`Services
`
`Routing
`Services
`
`Adapter
`Services
`
`Integration Services
`Integration Services
`... to make it happen
`...
`to make it happen
`
`Repository Admin
`
`Workflow
`
`Partner
`Services
`
`Power to Embrace, Extend and
`Integrate e-business Processes
`
`HP_1028_0032
`
`
`
`Conclusions
`
`Middleware is evolving to provide a wider range of
`services to meet the needs of businesses implementing
`application integration
`Message/Information Brokers are becoming an
`established component of MoM
`And gaining widespread acceptance
`New technologies will continue to drive the evolution of
`middleware
`There is a "coming together" of existing technology
`strands that currently overlap to provide a consolidated
`and consistent "whole"
`New business requirements are driving a "bigger
`picture" view of integration.... Business Integration
`
`HP_1028_0033
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
