The Architecture of an Enterprise System
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
The Architecture of an Enterprise System
Objectives Introduce enterprise system architecture.
Discuss system landscape.
Enterprise System DiversityEnterprise systems must run on a diversity of
hardware and software platforms.
Enterprise System Requirements: Standard database technologies.
Standard data communications protocols.
Real-time support for key business processes throughout the organization.
Enterprise System Architecture
Logical Architecture defines the components and functionalities supported by systems. The database is the heart of the logical support for
integrated business processes.
Physical Architecture defines how specific components are implemented on computer and communication systems.
Logical Architecture
EnterpriseStructure
&Environment
Data
end users
Applications
OperationalData
ACCOUNTING
SALES &DISTRIBUTION
PRODUCTION
HR
Logical Architecture
The database contains operational data related to the realities of business transactions, including enterprise structure and environmental data.
To support planning and analysis activities, a data warehouse is typically created as an additional database layer.
Definition of Data Warehousing
Inmon’s Formal Definition of DW:
“A Data Warehouse is a subject-oriented, integrated, nonvolatile, time-variant collection of data in support of management’s decisions.”
Operational Databases are Ill-suited as a Data Source Supporting Discovery
Traffic generated by accesses to organizational data to support data mining, DSS, OLAP, etc. negatively impacts organizational operations.
Data required to discern the patterns of behavior within which discovery emerges is not retained in operational databases.
Logical Architecture of R/3
R/3R/3BASISBASIS
FIFIFinancialFinancial
Acctg.Acctg.
COCOControllingControlling
AMAMAssetAssetMgmtMgmt
PSPSProjectProjectSystemSystem
WFWFWorkflowWorkflow
MMMMMaterials Materials
MgmtMgmt
HRHRHumanHuman
ResourcesResources
SDSDSalesSales
PPPPProductionProductionPlanningPlanning
QMQMQuality Quality MgmtMgmt
PMPMPlantPlantMaint.Maint.
ISISIndustryIndustry
SolutionsSolutions
R/3 is the client/server system technological tier for SAP that replaced R/2, the legacy system version of SAP.
Physical Architecture Database Layer.
Application Layer.
Presentation layer.
Database Layer
Typically a relational database distributed across multiple servers.
Application Layer
Application servers are responsible for specific applications stored as compiled versions of the application.
Workload considerations may cause work to be rerouted to different servers; e.g. multiple concurrently available application servers.
Application servers retain application-specific data in caches to provide quicker access to recent versions of that data.
Application Layer A work process defined for specific tasks help
coordination between application servers.
Application components supporting user interactive access bind to dialog work processes.
Application components that generate background work bind to batch processes.
Additional work processes coordinate activities between servers.
Presentation LayerThe purpose of the presentation layer is to accept essential data
from the user and provide preformatted reports to the user.
Presentation Layer Characteristics: Provides the menu-driven GUI interface between users and
applications.
May reside locally on a user’s desktop computer or be a completely separate presentation server on the LAN.
May keep in temporary, local storage a list of recently invoked transactions and data specific to the process being supported to alleviate the need to access the server.
May be customized for a specific user.
Open Systems Approach
RFC
CPI-C
OLEEDI
ALE
TCP/IP
OLE – Object Linking and EmbeddingRFC – Request for CommentsCPI-C – Common Programming Interface for CommunicationsALE – Application Link and ExecutionEDI – Electronic Data InterchangeTCP/IP – Transmission Control Protocol/Internet Protocol
Tiered Configurations
Application
Database
Presentation
Database, application, presentation processes
Central system Two-tier Three-tier
Presentation processes
Database,application processes
Database processes
Application processes
Presentation processes
3-tier Enterprise System Scalability
Scalability
Application
Database
Presentation
Master Data
Organizational structure
Programs
Log files
Database server
Application servers
Database: Contains most objects
Data dictionary
Transaction Data
Application servers
Application Servers:Contain work processes
Database serversDispatcher
Wor
k P
roce
ss
Wor
k P
roce
ss
Wor
k P
roce
ss
Application Servers:Contain work processes
Dispatcher
Wor
k P
roce
ss
Wor
k P
roce
ss
Wor
k P
roce
ss
Work process can be:• Dialog• Batch• Update• Spool• Message• Gateway
Message Server: Coordinates message exchanges between different application servers.
Gateway Server: Allows the communication between R2, R3, and external systems.
System Landscape
Attempt to isolate production system from development, testing, and training systems
One System Landscape
PRD
Development
Development Testing
Quality Assurance
End User Training
Sandbox
Production
PRD – Production
Two System Landscape
Development
Development Testing
Quality Assurance
End User Training
Sandbox
DEV
Production
PRD
DEV – DevelopmentPRD – Production
Three System Landscape
Production
PRD
QAS
Development
Development Testing
Quality Assurance
End User Training
Sandbox
DEV
Customizing Master
QAS – Quality AssuranceDEV – DevelopmentPRD – Production
Transport Management
Version management.
Import changes in an orderly manner.
Apply changes consistently.
Development
Transport Directory(FIFO Buffer)
release
apply
releaserelease
applyapply
Test Quality testuser training Production
Summary Introduced enterprise system
architecture.
Discussed system landscape.