Basis Overview

8/8/2019 Basis Overview

1/35

1 / 29 April 2008 / EDS INTERNAL

ERP Architecture and Database

Administration


2/35


Contents

Role of an ERP AdministratorERP ArchitectureDatabase AdministrationSummary


3/35


Role of an ERP AdministratorHardware Requirements Planning (Hardware Sizing)

Installation & ConfigurationMonitoring System Health/Performance in terms of ERPApplication, Database, OS and Network

Support & Maintenance


4/35


Contents

Role of an ERP AdministratorERP ArchitectureDatabase AdministrationSummary


5/35


ERP architecture

User interface (presentation)Business logic execution (application)

Business data storage (database)


6/35


Client Server Configuration


7/35


ERP System Landscape

Three system landscape


8/35


Pre-requisites for ERP Implementation

Server HardwareOperating System

Database SystemNetworking (LAN / WAN)


9/35


Server Hardware Compatible For ERPSystems

1. Sun Sparc/Enterprise Servers2. IBM RS/ 6 000 Servers3 . HP Proliant or HP/9000 Servers4 . Dell Servers

(Using 64 -bit processors similar toIntel Itanium-II processors)


10/35


Recommended HardwareConfiguration

1. Minimum 1 GB of RAM and several GB is required forenterprise installations2. Typically 100 GB of Disk space is required only for ERP

software3 . The mission-critical nature of the application demands

several log files to be maintained forcing larger disk

sizes.4 . Once again the large disks must be high-speed &

highly available by way of redundancy measuressuch as RAID

5 . High End RISC processors


11/35


ERP Recommended Operating Systems

ERP software would need a high-end operating system thatsupports multi-tasking, multi-user application and multi-threading to support high performance.To provide scalability the operating system should supporthigh-end processor features such as 64 -bit support, SMPsupport etc.The leading operating systems such as high-end Unixversions (Sun Solaris, HP-UX, Dec-Unix, IBM AIX) wouldsupport ERP; Lately, Red Hat Linux also started supportingERP applications.Other leading edge operating systems like Windows NT,IBM OS/ 4 00, IBM MVS also support ERP.However not every ERP software vendor ports theirsoftware to every operating system


12/35


ERP Database Platforms

Oracle

Microsoft SQL ServerIBM DB2SAP DBInformix


13/35

1 3 / 29 April 2008 / EDS INTERNAL

LAN / WAN Connectivity

Types of Access Networks:EthernetFiber OpticWireless LAN

Types of Wide Area Networks:V-SATLeased Lines

Radio Frequency Links


14/35


Network Security in ERPERP systems applications depend on network security to

prevent inappropriate exposure of resources, which couldcircumvent application controls.

Based on the Three Tier model the network should besegmented and proper Access Control list (ACL) and orfirewalls should be utilized to ensure security for the entireERP solution.

Based on the Three-tier approach the WEB front endshould be separated for the Application backend.

Further separation should occur between the Applicationserver and the Backend database. Some ERP applicationswill not function properly if not configured to vendorspecifications.


15/35


Network Security in ERP contd.


16/35


ERP Application level Security - Example

Role

Profile


17/35


Batch Data Creation

Purpose:Lets you move long-running or resource-intensive program runs to times when thesystem load is lowERP background processing automates routinetasks and helps you optimize yourorganizations ERP computing resources


18/35


Storage Sub-systems

1. EMC2 . N etApp3 . H itachi4 . IB M5 . SUN

I ntelligent S torage Arrays (with S AN) areused for H igh Availability andPerformance .


19/35


D evelopment, Release, andTransport of Repository Objects


20/35


Transports in a Three-SystemLandscape - Example


21/35


Contents

Role of an ERP AdministratorERP ArchitectureD atabase AdministrationSummary


22/35


Database Administration

A Central DatabaseDB Modifications for Very Large DatabasesMonitoring for Alerts, Thresholds, ExpensiveSQL statements, critical situations like deadlocks etc.

Database Backups and ArchivingStandby/Failover configurations and DisasterRecovery planning


23/35


Why Central Database?

Avoids complexity of Distributed DatabasesReduces Redundancy of DataReduces Maintenance Costs like costs of ServerHardware, Backup, Archiving etc.

Reduces need for more Administrators


24/35


Monitoring

Thresholds like Table/Tablespace getting full.SQL statements running too long (Expensive SQL)could be due to a problem with statement itself,index design, CBO statistics, big tables or with lowOS resources of Database Server etc.Dead locks reduce overall performance whenfrequently used tables get locked and unable tounlock due to dead lock situation where A is waitingfor B to unlock and B is waiting for A unlock first.


25/35


DB Modifications for VLDB

DB Modifications for Very Large Databases (VLDB)================================What is a Very Large Database?--Large amount of Data i.e. > 4 0 GB--Large No. of Transactions i.e. > 1 lakh/hour--Big Tables i.e. > 1 GB--Large Amount of log file data i.e. > 1 GB/day--Large No. of Users i.e. > 3 00--Big Batch Jobs


26/35


Contd

L arge amount of D ata i . e . >40 G B--Disk Layouts, More disks for data files, More disks for Roll BackSegments, RAID LevelsB ig Tables i . e . > 1 GB-- Table StripingL arge N o . of Transactions i . e . > 1 lakh/hour-- Tuning the Redolog I/OL arge Amount of log file data i . e . > 1 GB /day--Enlarge/Move Redolog FilesL arge N o . of Users i . e . > 300

--Install Addl. RBSB ig Batch Jobs--Enlarge RBS


27/35


BackupD atabase (or Full ): Full database backups are the default and the starting point for allother types of backups. A full database backup captures the entire database, including allentries in the transaction logexcluding any unallocated extents in the files. Pages are readdirectly from disk to increase the speed of the operation.

D ifferential : Differential backups capture all the data that has changed since the last fulldatabase backup. Differential backups will increase the speed of the backup operation as wellas the restore. Because only the changed or newly allocated extents (bitmap tracking) arecaptured, differential backups are faster and smaller than full database backups. During arecovery, the last differential backup can be restored without applying a series of theindividual transaction log backups or differential backups. All changed data is captured in thelast differential backup.

Transaction log : Transaction log backups serially capture modifications to the database.Backups of the transaction log provide a history of the transactions that have taken placewithin the database. The backups of the log are then used in the recovery process to restorethe database fully, to a point in time. Transaction log backups are applied to recover adatabase by rolling forward (redoing) any committed changes not reflected in the databaseand rolling back (undoing) uncommitted.


28/35


Data Archiving in ERP

It provides a protection layer to the ERP database and resolves underperformanceproblems caused by huge volumes of data. It is important that SAP users should keeponly minimal data to efficiently work with database and servers. Data archiving ensuresthat the ERP database contains only relevant and up-to-date data that meet yourrequirements.

Data archiving uses hardware components such as hard disks and memory. For efficientdata archiving, minimum number of disks and disk space should be used.

It also reduces the system maintenance costs associated with the ERP database. In theERP database there are various procedures such as, data backup, data recovery, and dataupgrade.

ERP data archiving complies with statutory data retention rules that are common andwell-proven techniques.


29/35


Standby/Failover configurations and Disaster Recovery planning

Standby Server is used to switch in case of primary server is downWhen primary server is up, standby server canbe used for backups, reporting etc. to reduceload on primary database serverDisaster Recovery planning should be in placefor situations like database crash due tomanual or physical error or due to accidents ornatural calamities


30/35


Contents

Role of an ERP AdministratorERP Architecture

Database AdministrationS ummary


31/35


Summary

Before implementing an ERP software it is extremelycritical to understand the system and userrequirements from a hardware configurationperspectiveThe selected configuration should be scalablekeeping in view the world wide consolidations thatare happening in industryDatabase administration is critical to ERPimplementation. A Large Central Database in ERPsystem should be protected through Standby Serverand with Disaster Recovery procedure in place.


32/35


SAP Basis Activities

Landscape Design

Hardware SizingSecurity PoliciesBackup, Recovery & ArchiveStrategiesDisaster Recovery and BusinessContinuity Plan DesignDisk LayoutsLogon Load balancingWorkload DistributionCCMS ConfigurationBackground Job AdminPre-Installation Preparations,Installation and Post-Installation

Transport & Change Management

(SPAM, SAINT, SNOTE etc.)Kernel UpgradeVersion UpgradeDB RefreshClient AdministrationPrinters & Spool AdminOperation ModesSecurity Administration

Hardware Capacity VerificationMemory ManagementDatabase AdministrationPerformance Tuning


33/35


Questions?


34/35


Recommended Reading

Database Administration: The Complete Guide to Practices and

Procedures by Craig S. MullinsConcepts in Enterprise Resource Planning (Second ed.) by Monk,Ellen & Wagner, Bret (200 6 ), ISBN 0- 6 19-21 663 -8Enterprise Integration by Kent Sandoe, Gail Corbitt, RaymondBoykin, ISBN: 9 7 8-0- 47 1- 35 99 3 - 7Enterprise Resource Planning by Mary Sumner, Southern IllinoisUniversity, Edwardsville, ISBN-10: 01 3 1 4 0 3435 ISBN-1 3 :9 7 801 3 1 4 0 3437

Mission Critical: Realizing the Promise of Enterprise Systems(Hardcover) by Thomas H. DavenportOracle Database Administration: The Essential Reference (O'Reilly)by David C. Kreines, Brian Lackeys


35/35


THANK YOU !!!

Basis Overview

Documents

Transcript of Basis Overview