Integrating the Enterprise Applications

1
Integrating the Enterprise Applications

• Harry Harris
• European Solutions Architect

2
Objectives

• To explain what is meant by Integrating the
  Enterprise Applications
• What are the business reason a company wants to
  integrate
• An example of what is meant by Integration
• Some of the technologies available and a example
  of a design

3
What is Application integration

• The objective is to give the user
• a consistent view of the business process that is
  relevant to their function
• the ability to change data in real time
• a consistent set of data
• Consistent operational characteristic
• provide the ability to change the process with
  minimal overheads

4
Legacy Systems
Batch application then act on the data
Operators access application directly with local
data
5
What we mean by Enduser Integration
Network

• Messy Screen
• Paper integration
• Individual session to host data
• Problems integrating data
• Does not appear integrated

6
What we mean by Server Integration
Network

• Single view for User
• Consolidation at a single point
• Gives an integrated view

7
Why should a business integrate applications?

• IT is the backbone of business processes
• If they did not integrate applications they would
  go out of business
• IT is basically distributed processing
• There are legacy application that cannot be
  replaced economically
• Most applications are provided by vendors

8
How do they integrate Data Integration
Business Data logic Routing Format
GUI
Joins Replication File transfer
For Easy(If Homogenous) Cheap Recovery Single
Point of control
Homogeneous Heterogeneous
Against Do not always have API Difficult to build
in resilience for a distributed system Format
some time in business logic Can expose data
integrity Difficult to use with ERP solutions
9
Application Integration
Business Data Logic
GUI
Business Logic Routing Format
Business Data Logic
Fors Includes business logic Can Maintain data
integrity Reusable components

• Against
• Can be complex
• Multiple points of controls difficult recovery
  and management
• Reusable components

10
Data Application Integration Examples

• Hotmail
• All the data held on the server
• Outlook Express
• data shared between server and user requires data
  replications facility
• Internet banking
• Security shared
• Functions execute on remote hosts
• Progress reflected to user

11
Query and Update Data Operations

• Query
• No data is changed
• Sharing causes no real problems
• Update Can cause problems
• Data is changed
• Sharing and duplication causes problems
• Sharing can be handled by locking but this
  affects performance
• Local copy of data means local data could be out
  of date
• handled by before/after image or currency counts

12
Transactions
Atomicity Consistency Isolation Durability
Transaction manager is a contract manager vital
in error situations
13
Typical IT System
SAP/R3 Applications
Webb Server Gateway
Java Applications
IT Systems
Internet Access
Branch LAN
Batch Applications
Corporate Network
CICS Applications
Active X Applications
Workgroup Server Gateway
14
eBusiness Production Model
Competitors
15
The Dream
Security Auditing Management Monitoring
Voice Channel
Internet Channel
Branch Channel
Branches
Web Users
Phone Users
Call Center
Web/App Servers
Relationship Management Business Logic
Logical Single View of the Customer
Core Systems
Mortgage
Retail Bank
Cards
Life and Pensions
Unsecured Loans
Corporate Banking
16
The Reality
Talk to Agent
BRANCH
ITP
Email
WEB
Video
ENABLED
VPN
Audio

Chat
ATM
Voice
ACD
IP
Multimedia Desktop
Customer
IVR
WEB
Sally Hansen
CTI
CLI
GENESYS
909766590
SERVER
Sales Prompts
IP
XML
Mortgage
COM
EMAIL
COM
Applications
Advisor
SERVER
CORBA
Video / Audio /Chat
NetACD
SIEBEL
APPL
CORBA
SERVER
COM

Security

Translation


Tandem

CICS
Security


Security

CORBA

Security

Translation
COM
Translation
Translation
CICS
MTS
IBM
UNIX
NT
17
Types of communications
Conversational
Message Queue
RPC
Program
Program
Program
Program
Program
Program
Callee
Queue Manager
Caller
Stub
Stub
LU6.2
Logical
Logical
TCP/IP
Network
Network
SNA
Physical
Path Control
Network
Physical
Physical
Network
Network
Network
Sender/Receiver can change
Sender/Receiver Fixed
Permanent application connections
Connection via Queue managers
18
Publish and Subscribe Comms Model

• Good Asynchronous communications model
• Neither application need have any knowledge of
  its partner
• 3 parts
• Broker
• provider of information
• gather of information
• Selection of information
• Content
• Topic

Publishing Application 1
Publishing Application 2
Subscribing Application 1
Subscribing Application 2
19
Application Production Architecture
20
Middleware Services

• Transformation
• Tag/Value structure
• XML (extensible Mark-up Language)
• Routing
• Directory
• Lightweight Directory Architect Protocols
• Publish and Subscribe Brokering
• Work Load Balancing
• Resilience

21
What is, HTML, XML and DOM
Metadata
Document Markup
Allows data to be presented on a Browser screen
How to describe a markup language
SGML
HTML
lth1gtIntroductionlt/h1gt ltpgtWhen Tim Berners-Lee was
looking for a representation for the documents
to be shared over the World Wide Web, he turned
to SGML. lt/pgt
DOM Tooling
Transformation
ltperson idHAHAR" gt ltnamegt
ltfamilygtHarrislt/familygt ltgivengtHarrylt/given
gt lt/namegt ltemailgtHarry_a_Harris_at_hotmail.co
mlt/emailgt lt/persongt
XML
Metadata
Markup indicates structure and semantics Decouples
from presentation
22
Enterprise Application Integration
Business to Business Integration
Business Process Integration
Workflow Management
Application Integration
Data Integration
Monitor and Manage Authenticate and Authorize
Business Logic
Batch
Real Time
Transactions
File Transfer
Distributed Databases
Component Models
Database Replication
Distributed File Systems
Application Adapters
Data Adapters
Presentation Logic
Session Management
Data Exchange
Message Queuing
RPC
Networking
Encryption
Transformation Routing
23
Conclusions

• Application Integration is a cornerstone of
  solutions
• Rarely do you design a system from scratch
• You will incorporate some supplied packages
• Must have an architecture
• Ensures consistency
• make re-use easier
• Many technologies to choose from
• Always bear in mind systems must be
• Reliable
• Recoverable
• Maintainable