Beruflich Dokumente
Kultur Dokumente
Chapter 14
Problems of Enterprise-Wide
Computing
• Slow response time during peak traffic
loads
• Different time zones, systems, upgrades
• Heterogeneous database problem
• Multiple platforms
R/3 and Enterprise Computing
• Development of “middleware” enables portability
across platforms
– Technologies include:
• Db replication, messaging, XML, remote procedures
• R/3 supports:
– TCP/IP
– RFC
– SQL & ODBC
– OLE, MAPI, EDI
R/3 Server Installations
• 3-tier C/S preferred
– Homogeneous - same OS on one or more
platforms
– Heterogeneous - a variety of platforms ex. UNIX,
NT, Windows on application server
• UNIX with Oracle, Informix, DB2 on db server
– R/3 solves the distributed multiple heterogeneous
platform problem with “middleware”
Benefits of Multiple Application
Servers
• An alternate server can be automatically
selected if one is unavailable
• “Load balancing” of clients to least busy
server
• Can optimize queries and reduce load on db
server to improve response time
• Because it is scalable, servers can be added as
more processing capability is needed
C/S Scenarios
• Centralized host computer performs all tasks
including db, applications, and presentation
• 2-tier C/S - db server is separate from “thick
client” which processes apps and presentation
• 3-tier C/S - separate systems for db, apps, and
presentation (preferred by R/3)
• N-tier C/S – extension using servers on Internet
SAP R/3 Basis System
Hardware UNIX Systems Data
AT&T General Sequent
Bull IBM IBM
Bull/Zenith HP (Intel) SNI
Digital SNI AS/400
Compaq IBM (Intel) ...
HP SUN
ADABAS D
Databases DB2 for AIX ADABAS D
INFORMIX-OnLine 7 MS SQL Server 6.0 DB2/400
ORACLE 7 ORACLE 7
Windows 3.11,
Dialog
Windows 3.11, Windows 95, Windows NT, OSF/Motif, Windows 95,
SAP-GUI
OS/2-Warp, Macintosh Windows NT,
OS/2-Warp
Languages
ABAP/4, C, C+ +
R/3 Middleware Transfer
Protocols
• Front-end (presentation tier)
– R/3 GUI uses resident OS resources to cut flow
of data to 1-2 KB
– whole screens are not passed but only logical
control information and user inputs
• DB interface (between app and db servers)
– SAP SQL within ABAP/4 environment
– then translates queries into “native” SQL
More Middleware Functions
• Interprogram communications
– synchronous vs. asynchronous
• Synchronous uses CPI-C, from IBM in the late ’80s
– RFC/RPC libraries and DLLs to call R/3
functions/modules
– SAP is closely aligned with COM from MS
• Transaction management
– ALE -distributes db availability to several sites
• routes data, maintains security
• creates IDOC master which contains info about the data
• SAP experimenting with XML for internal messaging
Application Linking & Enabling
(ALE)
• Allows users to set up applications and
databases at distributed locations
• Not only routes data, but knows what data
are needed in given situations; “intelligent
middleware”
– ALE checks for consistency of data, updates
– uses IDOCS to send message between loosely
coupled systems, with possibly dif. R/3 ver.
– Asynchronous RFC means if system is down on
target it will retry again
R/3 Distribution Scenarios
• Initially, R/3 was designed with one
centralized db in mind (from late ’80s)
• ALE technology was developed to enable
different integration scenarios
– Contained in Business Blueprint
• Centralized, integrated DB and application server
• Centralized by module on servers
• Completely decentralized R/3 with central db
• “Next Generation” architecture
DEV QAS PRD
CUST
DW environments
EAI Server Legacy Applications
INFORMATION INTEGRATION
PROCESS INTEGRATION
J2EE ABAP
DB and OS Abstraction
Evolution of SAP App
development
• ABAP & SAP Basis WAS and Java
25.0 2500
$2 BILLION
20.0 2000
$ Billion
$ Million
15.0 1500
10.0 1000
5.0 500
$150 MILLION
0.0 0
1996 2001 1999 2003
Source: G2 Source: IDC, 1999
• Customer Driven
• Transaction Driven
• Multi-Media Access
• 1-800 Access
• Anytime Availability
• Limited Availability
• Fully Integrated
• Stand Alone Units
• Technology Enabled
• Technology
Constrained • Enterprise Capabilities
• Limited Capabilities • Profit Centers
• Cost Centers • CRM Centers
• Call Centers
eCRM Technology Architecture
Integrated Touchpoints
Web Internet
Self-service &
Collaboration
Relationship
Marketing
Content
Management Legacy Customer
Database Database
SFA
eCRM Vendors
Vendor Demonstrated Functionality
BroadVision Web Personalization
CenterCore Call Center Furniture
CNT Legacy Middleware Integration
Compaq NT servers and Desktop PCs
Genesys Computer Telephony Integration, E-Mail
Grahl Ergonomic Call Center Seating
Avaya Switch/ACD, Internet Telephony Gateway,Internet Call Center,
Call Management Server, Telephones & Headsets
Microsoft Microsoft ASP
Nuance Communications Speech Recognition
Siebel Systems Customer Service and Support Application, Sales
ForceAutomation
Sun Microsystems Unix Servers
Symon Communications Reader Board Messaging
Vignette Web Content Management
Cisco Web Collaboration/Integration
Xchange Campaign Management
Aspect Communications Workforce Management