Enterprise Integration Snapshots

1
Enterprise Integration Snapshots

• Enterprise Integration is vertical and
  horizontal alignment of plans, business
  processes, and information systems across
  organizations and functional boundaries to
  provide competitive advantage.
•  Business Integration Journal, December 2005
  Issue, http//www.bijonline.com
• IBM Systems Journal, Vol. 41, No. 4, 2002,
  http//www.research.ibm.com/journal/sj41-4.html
• Concepts
• Examples
• Questions
• Answers

2
Standards Bodies and Examples

3
Metadata

• Metadata is information regarding the
  characteristics of any artifact, such as its
  name, location, perceived importance, quality or
  value to the enterprise, and its relationship to
  other artifacts that an enterprise has deemed
  worth managing.
• Michael Belcher, BIJ, Nov/Dec 2005
• Example
• For any table of data, table definitions are
  examples of basic metadata.
• Higher-level metadata (metadata for metadata) is
  needed in Data Warehousing and Service Oriented
  Development of Applications (SODA) or Service
  Oriented Business Applications (SOBA) where
  needed metadata is expressed in terms of Which
  services exist? What does each service invoke?
  What data (db/elements) does each service use?

4
Service Oriented Architecture

• Service oriented architecture views existing
  packaged or homegrown applications, generally all
  programs and data resources, as components from
  which to assemble (compose) new applications.
  Each component provides a set of services. New
  applications are composed by orchestrated calls
  to these services.
• Michael Carey, Ph.D., BIJ, Nov/Dec 2005
• SOA Orchestration Scope
• 1.      Simple web services
• 2.      More than request-reply services
• 3.      Policies, procedures, protocols
• 4.      Message oriented enterprise service bus
  (ESB)
• 5.      Services platforms and frameworks
• 6.      Quality of service (QOS)
• 7.      Standards and strategic technologies
  rather than product features set
• Daryl Plummer, BIJ, Nov/Dec 2005

5
Quality of Service (QOS)

• (Classic but now encompassing more distributed
  and interoperable environments)
• 1.      Availability
• 2.      Reliability
• 3.      Integrity
• 4.      Manageability
• 5.      Scalability
• 6.      Performance
• 7.      Security
• 8.      Transaction management
• Massimo Pezzini, BIJ, Nov/Dec 2005

6
Rules-Based Application Processing

• Business Process Management (BPM), Application
  Integration, Simulation, and Business Activity
  Modeling
• Out-boarding the business logic (rules),
  allowing user controls over critical business
  rules.
• BPM orientation requires making the business
  rules explicit in implementation and allows
  modification of system behavior during its use.
• Example (1) Meaning of a crown jewel customer,
  (2) Dashboards to alter business process flows or
  applications.
• Jim Sinur, BIJ, Nov/Dec 2005

7
Adapters for EI Facilitation

• Adapters are enterprise integration middleware.
• Examples of functionality
• 1.      Capture and recognize events
• 2.      Collect and transform data
• 3.      Process micro-flow
• 4.      Handle exceptions
• Examples of categories
• 1.      Database
• 2.      Legacy applications
• 3.      Technology protocols
• Benoit Lheureux, BIJ, Nov/Dec 2005

8
Integration Composition Platform

9
Integration Services Repository

10
Transaction Processing (many simultaneous
users, frequent servicing)

• Messimo Pezzini, BIJ, Nov/Dec 2005
• Large Scale Classical Business Critical OLTP
  Examples
• 1.      Airline reservations
• 2.      Insurance claim processing
• 3.      Telecom billing
• 4.      Bank branch operations
• 5.      Package tracking
• Old TP Platforms Examples
• 1.      Fujitsu-Siemens UTM
• 2.      Bull TP 7/8
• 3.      IBM CICS/IMS/TPE
• 4.      Unisys TP
• New TP Examples (distributed applications)
• 1.      BEA Tuxedo, WebLogic
• 2.      IBM Tx Services
• 3.      J2EE Enterprise Application Server (EAS)
• 4.      Oracle Application Server 10g
• 5.      Microsoft MSAP, .NET