R/3 System administrator Tasks

Maintain the systems health

Monitor system performance and logs
monitor backup jobs of the SAP database and any required
operating system level files
Create, test, and execute the SAP disaster recovery plan
Be willing to work the hours required to support the system
Keep proper documentation
Use checklists
Use the appropriate tool for the job
Perform preventive maintenance
Do not change what you do not have to
Do not make changes to the system during critical periods
Do not allow direct database access
Refer SAPNet R/3 notes when necessary
Keep tasks as simple as possible.

CCMS Activities

Starting/Stopping an R/3 System: Windows NT

Starting/Stopping an R/3 System: UNIX

Alert Monitor

Workload Monitor

Administration Tasks

Analysis of Logs/Dumps

Starting/Stopping an R/3 System: Windows NT

You start/stop the SAP System with the Microsoft

Management Console(MMC).

MMC only allows you to start/stop an SAP instance that is

installed locally on the host

If the MMC is configured for centralized system

management, you can start/stop the entire SAP System
from a single host.
The SAP System can also be started at the command prompt.

Starting/Stopping an R/3 System: Windows NT

Start Processing
1.

Start the R/3 services.

When the Windows NT system is booted, the R/3 service
( SAP<SAPSID>_<Instance number> , e.g. SAPC11_00 )
is always started automatically. The service evaluates
entries from the Windows NT Start Profile and reads the
necessary environment variables from the Registry.

2.

Start the R/3 processes.

start the R/3 processes using the Microsoft Management
Console (MMC).
DCOM communication is set up with the R/3 service and
messages for starting the appropriate R/3 instance are sent
to the service.
The R/3 service interprets the Windows NT start profile
and starts the processes started by the program
sapstartsrv.exe ).

Starting/Stopping Architecture: Windows NT

Start Processing

Starting an R/3 System: Windows NT

Starting an SAP System with MMC

1.

start the MMC with Start Programs SAP R3 Management

Console.

2.

select the node representing the central instance

3.

By choosing the right mouse button choose Start.

Stopping an R/3 System: Windows NT

Stopping an SAP System with MMC

1.

start the MMC with Start Programs SAP R3 Management

Console.

2.

select the node representing the central instance

3.

By choosing the right mouse button choose Stop.

Starting/Stopping an R/3 System: UNIX

To Start
1.

Log onto UNIX as the SAP administrative user ( <SAP System

name>adm )

2.

Enter the following command from your home directory.

startsap [DB|R3|ALL]
To Stop
1.

Log onto UNIX as the SAP administrative user ( <SAP System

name>adm )

2.

Enter the following command from your home directory.

stopsap [DB|R3|ALL]

DB starts the database system

R3 starts the instances and associated processes of the

R/3System (using the sapstart program)

ALL starts both the database system and the R/3 System.
ALL is the default and can be omitted.

Starting/Stopping SAP System: NT Command Prompt

To Start
1.

Log onto UNIX as the SAP administrative user ( <SAP System

name>adm )

2.

Enter the following command .

Drive:\usr\SAP<SID>\SYS\exe\run\
sapstart pf=\usr\sap\<SID>\SYS\profile\START_DVEBMGS00

To Stop
1.

Log onto UNIX as the SAP administrative user ( <SAP System

name>adm )

2.

Enter the following command from your home directory.

Drive:\usr\SAP<SID>\SYS\exe\run\
sapstart pf=\usr\sap\<SID>\SYS\profile\START_DVEBMGS00

CCMS Alert Monitor

The CCMS provides an alert monitor for helping you to monitor

and run your R/3 System, host systems, and database.

Status indicators (green, yellow, red) for all components.

Alerts if a status indicator is not in the green range.

Easy access to methods for analyzing alerts.

Alert tracking and management .

CCMS Alert Monitor

Procedure
1.

Call Transaction RZ20.

2.

Display the Entire System monitor by positioning the

cursor on any template and choose
Monitor Load monitor.

CCMS Alert Monitor

Procedure
3.

Check the state of your SAP System

The Current system status reflects the most recent

performance values and status messages reported to
the alert monitor.

CCMS Alert Monitor

Green: The component is running normally. Everything is

ok.

Yellow: A warning or "yellow-alert" has been issued.

Red: A problem or critical condition has been reported, a

"red alert.

4.

Choose Open alerts to see what has happened recently in

the system.

Open alerts are those that have not yet been

analyzed.

CCMS Alert Monitor

5.

Respond to an alert in the Open alerts view by positioning

the cursor on a yellow or red and choose Display alerts.

6.

Analyze an alert.

Start analysis method to start the problem analysis

transaction .

Display details to display details on the monitoring

tree element.

CCMS Workload Monitor

The workload overview provides system administrators
with various detailed information about the most important
workload data, such as

CPU time

Average Response times

Average time that an unprocessed dialog

step waits in the dispatcher queue for a free
work process

DB Calls

Average time when dialog process sends a

request to the dispatcher and the time at
which the dialog is completed and the data
is transferred to the user.

Average Wait Time

Average time that a work process uses the

CPU of the application server e.g (loading,
generation, processing database requests)

Number of calls to the database

DB Access

Number of logical ABAP accesses to the

data in the database through the SAP
database interface.

CCMS Workload Monitor

Number of configured instances for each SAP system

Number of users working on the different instances

Transactions with the highest response time and database

time

Memory usage for each transaction or each user per dialog

step

Workload through RFC, listed by transactions, function

modules and destinations

Number and volume of spool requests

Statistics about response time distribution, with or without

the GUI time

Optional: Table accesses

Workload and transactions used listed by users, payroll

number, and client

Workload generated by requests from external systems

CCMS Operating the Workload Monitor

Procedure
1.

call transaction ST03N.

UserMode:
What section of
functions and
period of time
should be
displayed

EditViews:
Save , Load , switch between views

HeaderData:
Specifies
instance , time
period and
task type of the
data fields
displayed in
the window
below

Functions:
What period of
time should be
displayed?

AnalysisViews:
From what point of
view do the
workload statistics
interest me?
-User

OutputArea:

-Transaction

System Load by the user mode , time period , and

analysis view .

-RFC Destination

CCMS Workload Monitor

Number of configured instances for each SAP system

Number of users working on the different instances

Transactions with the highest response time and database

time

Memory usage for each transaction or each user per dialog

step

Workload through RFC, listed by transactions, function

modules and destinations

Number and volume of spool requests

Statistics about response time distribution, with or without

the GUI time

Optional: Table accesses

Workload and transactions used listed by users, payroll

number, and client

Workload generated by requests from external systems

CCMS Operating System Alerts: al16

Number of configured instances for each SAP system

External Operating system Commands:SM69

Display Statistical Records:STAT

Workload Analysis of SAP system:st03

R/3 System administrator Tasks

Monitoring The System
1.

Call Transaction SM50

The process overview displays :

Number of processes running on the instance.

Number of Users Logged on

Estimate the current activities and resulting Load.

Cancel a process by deleting it.

R/3 System administrator Tasks

Checking System Logs
1.

Call Transaction SM21

R/3 System administrator Tasks

ABAP Dump Analysis
1.

Call Transaction ST22

R/3 System administrator Tasks

System Message
1.

Call Transaction SM02

R/3 System Active Users:al08

Active Users
1.

Call Transaction AL08

R/3 System Active Users:al08

Active Users
1.

Call Transaction AL08