Livecache Administration: Apo Overview

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 12

Scalability

APO Overview

liveCache Administration

Interface Between Backend and APO

liveCache Monitoring

CIF Monitoring

liveCache Backup and Restore

APO Software Maintenance

APO Performance

Scalability

APO and BW

Optimizers

APO Authorizations

liveCache Concepts

Disaster Recovery

liveCache Architecture

System Landscape Planning

SAP AG 2001

Scalability

Contents
APO Scalability
APO Sizing

Objectives
At the end of this unit, you will be able to:
Explain the scalability of an APO system

Perform APO sizing

SAP AG 2001

APO Scalability
VS

Very Small System (Micro System)


All APO components on one machine (currently
only under Microsoft Windows NT 4.0 / 2000)

Small System
Application, DB and optimization server on one
machine, liveCache on a separate machine
Medium System
Application and DB server on one machine,
liveCache separate, all optimizers on one separate
machine

Large System
Several application servers, DB server possibly
separate, liveCache separate, optimization servers
on high end machines

SAP AG 2001

APO Sizing: Very Small System Implementation


VS

Frontends
Generally

APO GUI
Min. 128 MB main memory
Screen resolution 1024x768 pixels
Min. 32768 colors
(True Color recommended)

APO server
APO GUI / App. server / DB server / liveCache / Optimizer on one machine

Hardware (example):
1 processor (700 MHz Intel Pentium III Xeon)
2 GB main memory
20 GB hard disk space

SAP AG 2001

APO Sizing: Small System Implementation

liveCache on a separate machine


Hardware (example):
2 processors (700 MHz Intel Pentium III Xeon)
2 GB main memory
10 GB hard disk space

App. server / DB server / Optimizer on one machine

Hardware (example):
2 processors (700 MHz Intel Pentium III Xeon)
1-2 GB main memory
25 GB hard disk space

SAP AG 2001

APO Sizing: Medium System Implementation


S

Optimizers (for SNP, PP/DS, CTM)


on a separate machine
Hardware (example):
2 processors (700 MHz Intel Pentium III Xeon)
128 MB main memory per CPU
2 GB hard disk space

liveCache on a separate machine


M
Opt

Hardware (example):
4 processors (700 MHz Intel Pentium III Xeon)
4 GB main memory
50 GB hard disk space

App. server / DB server on one machine

Hardware (example):
3 processors (700 MHz Intel Pentium III Xeon)
3 GB main memory
50 GB hard disk space

SAP AG 2001

APO Sizing: Large System Implementation


Optimizers (for SNP, PP/DS, CTM): per
optimizer one separate machine with
2 CPUs, or 2 CPUs per active
optimizer as a minimum

Hardware (example):
> 4 processors altogether
(700 MHz Intel Pentium III Xeon)
256 MB main memory per CPU
2 GB hard disk space

liveCache on a separate machine

L
Opt

Hardware (example):
16 processors
(700 MHz Intel Pentium III Xeon)
64 GB main memory
150 GB hard disk space

Multiple application servers on separate machines

DB server hardware (example):


16 processors (700 MHz Intel Pentium III Xeon)
8 GB main memory
200 GB hard disk space
SAP AG 2001

Platform Availability APO 3.0A

Operating Systems

Application server: Windows NT 4.0 / 2000 (Intel),


UNIX (HP-UX 11.0, AIX 4.3x, Sun Solaris 7, Tru64 4.0F, Reliant
UNIX 5.45)

liveCache server: Windows NT 4.0 / 2000 (Intel),


UNIX (HP-UX 11.0, AIX 4.3x, Sun Solaris 7, Tru64 4.0F)
on request - pilot phase

Optimization server: Windows NT 4.0 / 2000 (Intel)

Databases

Presentation server: Windows NT 4.0 / 2000,


Windows 95 / 98 (Intel)
Oracle (on Windows as well as UNIX platforms)
SAP DB
Microsoft SQL Server
DB2 / UDB
Informix

Up-to-date information: http://service.sap.com/platforms

SAP AG 2001

Hardware Recommendations for APO Systems


Network Connection
- High speed (FDDI,
High Performance
Switch)
- Ethernet or equivalent
APO System - Standard Configuration
APO DB server
Database with BW
-like configuration
APO SAP instance

APO server
APO SAP
instance

Frontend
SAP GUI with OCX
functionality, known
WAN issues
SAP AG 2001

Optimizer servers
SNP, PP/DS
DPS and SEQ,
CTM, ND, VSR

Frontend
SAP GUI with OCX
functionality, known
WAN issues

APO liveCache
server
liveCache
COM routines

Frontend
SAP GUI with OCX
functionality, known
WAN issues

Example: Customer Test Site Installation on NT 4.0

APO R/3 DB server + liveCache server

Windows NT Enterprise Edition 4.0 English, Service Pack 6

Microsoft Internet Explorer >= 4.01 SP1

Windows NT Resource Kit recommended

30 40 GB disk space (NTFS) on three physical disks

2 4 GB memory, 2 4 CPU

APO CDs (Kernel/Export/RDBMS) copied to local directory

Admin frontend

Microsoft Internet Explorer >= 4.01 SP1

100 MB free space on local hard disk

SAPNet access for Notes

SAPNet access for Support Packages

sapservX access for liveCache/frontend patches

SAP AG 2001

Further Documentation

For additional information about scalability, go to URL:


service.sap.com/scm
service.sap.com/platforms
service.sap.com/instguides

service.sap.com/sizing

SAP AG 2001

Scalability: Summary

You are now able to:

Explain the scalability of an APO system


Perform APO sizing

SAP AG 2001

You might also like