System Administration (AS ABAP and/or SAP Java)

Unit 3 Lesson: Logon Group in AS ABAP

1. Explain the benefits of logon groups in AS ABAP
End users to have comparable response times
Load Balancing
Every instance of an SAP system is assigned to the logon group SPACE
2. Set up logon groups in AS ABAP
Logon groups are set up in transaction SMLG
Unit 3 Lesson: Fundamental Concepts of Java
3. Use basic Java terminology

The Java programming language was first introduced in 1995 by Sun

Microsystems Inc. Java is an object-oriented and platform-independent
programming language that has spread across many areas.
Java has been designed to be platform independent.
2 types of Java programs: Applications and applets.
Applications are computer programs with the full functional range also
provided by other programming languages.
Applet is a small computer program that runs in a Web browser and is
written in the Java programming language.
The bytecode generated by the Java compiler
A Java Development Kit (JDK) includes the software required to create
and test Java applications and applets, the packages with the Java
classes that are part of the basic configuration, and the online
documentation. The software includes the Java compiler, the Java
Runtime Environment for running applications, the applet viewer for
running applets, a Java debugger, and various utilities.
Products of Java:

Java Standard Edition (Java SE)

Java Enterprise Edition (Java EE)
Java Micro Edition (Java ME)

SAP NetWeaver AS Java does not require a JDK from the operating
system manufacturer instead; the SAP-specific JDK is used on all
operating systems.
Some of the SAP JVM properties were developed especially to meet the
requirements of SAP customers:

Additional Supportability
Profiling and Memory debugging
Debugging on demand

Java compiler generates a separate file for each class. You can also
combine multiple class files into a compressed archive file.
The bytecode of a Java application is executed by calling the Java Virtual
Machine JVM. In Java there are also small Java programs (clases) These
programs are known as Java Beans.
The Java EE server uses Java Server Pages (JSP) and Java Servlets to
generate HTML pages or XML data. Java Server Pages and Java servlets
are executed in a Web Container.
Java Server Pages (JSP) are a technology developed by Sun, which
essentially allow the simple dynamic generation of HTML and XML output
for a Web server. Each application component is executed in a
container.
Processing of a Client Request by the Java
1. The client sends a request to the server.
2. A servlet (Controller) processes the request and calls the
corresponding Java Beans.
3. The Java Beans (Model) execute the application logic and use
services that are provided by the application server during the
execution.
4. The servlet selects the appropriate JSP to dynamically display the
result
5. The JSP (View) fetches the result form the model and dynamically
builds it into a HTML template.
6. The result is returned to the client

Unit 3 Lesson: Java Cluster Architecture

4. Explain the term Central Services of SAP NetWeaver AS Java

Client request to SAP NetWeaver AS Java are received by ICM. The ICM
distributes new incoming requests to the available server processes
using a round robin algorithm. The server processes are
implemented as multi-threaded servers and can therefore process
multiple requests in parallel.
Central Services
The central Services run on one host and form a separate Java Instance.
They consist of the Java message server and the Java enqueue server.

Message service administers a list of the ICM and the server

processes of the Java cluster. Load balancing between a large
number of Java instance and the information for the SAP Web
Dispatcher
Enqueue service administers logical locks

5. Understand and use concepts such as Java instance, ICM, and

server

The following components are part of Java instance:

Server Processes provide the infrastructure in which the Java
run.
ICM distributes the client request to the free server processes of
the instance.
An instance always runs on one physical server, but there can be
multiple instances on one server. An instance is defined using the
system ID(SID) of the SAP system and the instance number. An SAP
system consists of a database and one or more instances.
All Java components of an SAP system are known as a Java cluster. A
Java cluster consists of:

A Java instance with an ICM and at least one server process

The Central Services, which contain a message server and an
enqueue server
A database for the central storage of data

Message service
The message service is an individual program used to communicate
between the elements of a Java cluster.
The message service performs the following tasks in the Java cluster:

Notification of events that arise in the cluster

Communication between different services
Prepare logon information for the SAP Web Dispatcher

Enqueue Service
The enqueue service runs on the Central Services instance of the Java
cluster. It manages the lock table in the main memory. The enqueue
server is the program or process that provides the enqueue service.
The enqueue service has the following tasks:

It is used for synchronization within the java cluster

Can lock objects are release locks again.

Unit 3 Lesson: The Internal Structure of SAP NetWeaver Java

6. Name the most important managers of the SAP NetWeaver AS
Log Manager
Application Thread Manager
Thread Manager
Locking Manager
Configuration Manager
Class loading Manager
Cluster Manager
Cluster Manager
Service Manager
7. Name the most important services of the SAP NetWeaver AS
Security Provider
Monitoring Service
Log Configurator service
Deploy Service
EJB Container Service
HTTP Provider
8. Briefly describe the function of the Java Virtual Machine (JVM)
The JVM executes the platform-independent bytecode generated by the
Java compiler on the relevant hardware.

Unit 4 Lesson: System Start: Process

9. Describe the process of the start procedure of an SAP system
The start process is triggered with the operating system user <sid>adm:
Starting the Central Services instance
Starting the database
Starting the PAS instance
Starting the AAS instace
10.
Describe the structure of the file system for SAP instances
The instances of SAP systems can be divided into 3 different categories
with different priorities for the start and stop process
Instances with enqueue but without ABAP dispatcher
Instances with enqueue and with ABAP dispatcher
All oter instances
Extra Information

In the file system, the data for the instances is contained in the
usr/sap directory
The <SAPSID> directory contains all data that must only be
accessed by SAP system
The data for PAS instance is located in the DVEBMGS<no>
directory
The directory work contains the logs of the start process
The directory exe contains the kernel
The SYS directory contains the following subdirectories in
particular:
o Global
o Profile
o Exe
The sapstartsrv program reads the start profile or instance profile
Parameters are defined in the default profile for all instances

Unit 4 Lesson: System Start: AS ABAP and AS ABAP+Java Process

11.
Describe the sequence in which the components of an SAP
system and started and stopped
1. The PAS instace is started first when the overall SAP system is
started.
2. A check is performed to see wheter the database is running,
3. The ABAP message server and the ABAP dispatcher are now started,
4. The system checks wheter the database is running. The database
was started when the PAS instance was started

5.

The ABAP dispatcher is started, which starts its work processes and
the ICM

12.
Describe the general start process for an SAP NetWeaver
AS ABAP+Java
In an instance of a dual-stack system , the Java Stack is started by the
ABAP DISPATCHER USING THE Stup and control Framework. The Java
cluster elements are started using the Startu and Control Framework. An
SAP system is stopped in the opposite sequence
13.
Evaluation of the Start, Default, and Instance Profiles
First, the sapcpe program is executed, the system checks whether the
database is already running. The start profile or instance profile for the
PAS instance specifies that the sapstartsrv process first starts the ABAP
message server. The ABAP message server evaluates the parameters of
the default and instance profile, and starts with this parameterization .
Extra Information

The instaces are started and stopped using tools such as the SAP
Management Console (SAP MC)
In an instance of a dual-stack system, the Java stack is started bye
the ABAP dispatcher usig the Startup and control Framework
The sapstartsrv processes write a 1-byte control file to the $
(DIR_GLOBAL)/sapcontrol directory every minute

Unit 4 Lesson: Overview of the Process for Starting and Stopping an

SAP NetWeaver AS Java
14.
Describe the sequence in which the components of an SAP
system and started and stopped.
The start process is performed in multiple steps. The start process is
performed with the operating system user <sid >adm:
Starting the Central Services Instance
Starting the DB
Starting PAS or AAS
The stopping of an SAP system is performed in reverse sequence. The
instances with enqueue are always stopped last.
15.
Describe the general start process for an SAP NetWeaver
AS Java
In an SAP NetWeaver AS Java system, the Startup and Control
Framework is started directly by the sapstartsrv. The Central Services
instance is started. The sapstartsrv of the PAS and AAS check before the
start of the instance whether the database is running; if it is not, it is

started before the PAS or AAS is started if the database is installed on

the same host where PAS or AAS is installed.

16.
Describe the general start process for an SAP NetWeaver
AS ABAP + Java
The instances are started and stopped using the Management Console
(SAP MC). The start of the Java stack is controlled by the ABAP
dispatcher. The ABAP dispatcher sends a start command to the Startup
and Control Framework.
The tools communicate with sapstartsrv. This is a service in Windows
operating systems; it should be scheduled as a daemon in toher
operating systems. There is an sapstartsrv for each instance; this is
responsible for starting and stopping the instance
Unit 4 Lesson: Tools for Starting and Stopping SAP Systems
17.
Operate the tools to start and stop an SAP NetWeaver AS
ABAP
SAP Management Console allows you to display varilous monitoring
information and perform administration task such as start and stop
operations in the same interface on different operating systems.
To start the SAP MC after installing the relevant SAP NetWeaver AS, enter
the following URL in your browser:
http://<hostname>:5<instance number>13
Starting and stopping the database with the SAP Management
Console and SAP Host Agent
The SAP MC receives the information form sapstartsrv, on which
computer the DB runs and connects with the SAP Host Agent, which
starts or stops DB through the Port 1128
Start Sequence during the start with the SAP MC
1. The SAP Host Agent receives the command to start the database
2. The SAP Host Agent starts the DB if it is in the state stopped
3. The sapstartsrv of the instance with the priority 1 gets the command
to start instances according to their priority
4. The sapstartsrv of the instance with the priority 1 starts its instance.
5. The sapstartsrv of the instance with the priority 1 triggers the
sapstartsrv of the instance with the priority 3 to start its instance
6. The sapstartsrv of the instance with the priority 3 starts its instance

Previosly on SAP system installed under UNIX, you executed the scripts
startsap and stopsap to nitiate the start and stop processes

Unit 4 Lesson: Tools for Starting and Stopping

18.
Operate the tools to start and stop SAP NetWeaver AS
ABAP + Java
The SAP MC allows you to start and stop all the SAP NetWeaver AS ABAP
+ Java instances as well as the Central Services.
With tools such as sapcontrol the database is only started, when a PAS or
AAS instance is started on the same computer on which the DB is
installed too.
The SAP MC receives the information from sapstartsrv, on which
computer the DB runs and connects with the SAP Host Agent, which
starts or stops DB through the Port 1128.
Instances of SAP NetWeaver AS ABAP + Java can be started and stopped
independently of the operating system using the SAP Management
Console. This tool also evaluate the developer traces.
SAPControl allows the Web services of the sapstartsrv processes to be
addressed. Is part of the kernel, and is available on all operating
systems.
19.
Operate the tools to start and stop SAP NetWeaver AS Java
With the Microsoft Windows operating system, you can use both the SAP
Management console and the Microsoft Management Console
To start an instance of the SAP SYSTEM, OPEN A TELNET CONNECTION
AND ENTER THE FOLLOWING COMMAND: STARTSAP NAME=<SID>
nr=<Instanz-Nr.> SAPDIAHOST=<Rechnername>
To stop a instance of the SAP system, open a telnet connection and enter
the following command: stopsap name=<SID> NR=Instanz-Nr.>
SAPDIAHOST=<Rechnername>
Unit 4 Lesson: System Start: AS ABAP Logs
20.
Use the AS ABAP start logs to analyze problems
The start process is an especially important phase, which is logged bye
the operatin system, the SAP system, and the database.

Logging the Start Process in the SAP System

Usr/sap/<SID>/<Instance><No>/work/
Stderr1n=Logs of the processes started by SAPSTARTSRV
Sapstartsrv.log= Trace file of the program SAPSTARTSRV
Sapstart.log= Start log and trace info for the database the message
server, and the dispatcher
Dev_ms= trace file of the message server
De_disp=trace file of the dispatcher
Dev_w0n= trace file of the work processes
Logs about the start process of the SAP system are stored in the file
system
You can set the granularity of the logged information using the profile
parameter rdisp/TRACE profile parameter. The possible values for this
parameter are:
0: No trace
1: Error messages
2: Full trace. The trace entries dependend on the SAP program that is
being traced
3: As 2: but data blocks are also traced.
The times in which the instance was started and stopped are logged on
available.log
Unit 4 Lesson: Java Startup and Control Framework
21.
Use the term Startup and Control Framework
This framework is used to start, stop, and monitor Java stack processes
within the SAP system
JStart- Instance Controller
The instance Controller starts stops, and monitors the processes
of a Java Instance.
Restart terminated processes, ends hanging processes and sends
a shutdown signal to the processes of the Java stack.
Reads the description of the instance from profile files.
Starts the Server processes and the ICM.
Creates a shared memory segment for the internal administration
data of all processes
22.
Describe the individual steps during the start and stop
processes of a Java Instance
Start
1. The Instance Controller is started
2. The Instance Controller connects to the Central Services instance
3. The Instance Conroller reads the file instance.properties in the cluster
directory

4. Run-level 1: The Instance Controller reads configuration files form the

file system and starts a jstart process that transfers the offline
deployment
5. Run level 2: The Instance Controller reads configuration files from the
file system and starets a jstart process that carries out the bootstrap
process and synchronizes data from the database to the file system
6. The Instance Controller reads the file instance.properties
7. The Instance Controller reads configuration files from the file system
Stop
1. The Signal Handler of the Instance Controller receives a stop
signal from the sapstartsrv
2. The Instance Conroller passes the signal on to all running server
processes via named Pipe and waits until they are stopped
3. When the server processes of this instance are all stopped, the
Instance Controller sends the stop signal to the ICM
Unit 4 Lesson: Logs of the Start and Stop Processes of SAP NetWeaver
AS Java
23.
Find the storage locations of trace and log files of the
Startup and Control Framework
This directory is called usr/sap/<SID>/<instance name>/work
24.
Name the most important trace and log files of the Startup
and Control Framework and review their content
Trace and Logs of the Startup and Control Framework
Dev_jstart
Dev_<node name>, such as dev_server0
Jvm_<node name>.out, such as jvm_bootstrap.out
Std_server<X>.out, such as std_server0.out
Log_bootstrap<Nr.>.log , such as log_bootstrap.0.log
Unit 4 Lesson: Logs of the Start and Stop Processes of SAP NetWeaver
AS Java
25.
Plan an schedule downtimes in your SAP Systems using the
SAP Solution Manager
SAP Solution Manager execute work modes for technical systems,
databases, technical scenarios, instances and logon groups. Work Mode
Management is used to define business Work Modes, which helps you to
adapt the monitoring thresholds of the involved systems to the current
system load.
You can use Technical Work Modes helps you to inform users of planned
downtime and maintenance windows for activities like
Patch upgrades

Upgrades
Database, hardware or operating system maintenance
Configuration or customizing changes
Migration

Types or Work Modes

Peak Business Hours

Non-Peak Business Hours
Non-Business Hours
Planned Downtime
Maintenance

The work mode management comprises all tasks to handle downtime

management in your system landscape. These are:

Downtime Planning
Notification Management
Alert Management
Task Management
Execution of the Downtime

Unit 5 Lesson: How the System Evaluates Its Parameters

26.
Determine the configuration of profile parameters
The profile files are automatically created during installation in this
directory: /usr/sap/<SID>/SYS/profile.
The SAP system has two or three types of profiles
Start profile
Default profile
Instance profile
The instance-specific start profile specifies which processes are to be
started for each instance.
There is only one default profile for each SAP system, and it is read by all
instances. It contains the system name, name of the database server,
name of the enqueue server or also the default logon client.
The instance profile defines parameters that apply for one instance.
The current values of the profile parameters can be displayed in the system.
There are 2 ways to do this: Transaction RSPFPAR and RZ11. Both display
profile parameters for the instance in which the user is currently logged on.
Unit 5 Lesson: How to set Profile Parameters
27.

Adjust the profile parameters using profiles

Profile administration in the SAP system offers a number of advantages

to the user:
Central administration and maintenance of the instances
Changes in profiles checked for consistency
Administration of multiple versions of a profile
There are 3 different levels for maintaining the profiles. The administration data
contains the type of profile a short description, the path of the file, the name of
the instance, and the time of the last activation.
You can import profiles in Transaction RZ10. And you can view a change history
of the parameters in transaction TU02
Unit 5 Lesson: Setting up Operation Modes
28.
Set up a dynamic switch of work process types using
operation modes
Using the operation modes, you can adjust the type and distribution of
the work processes to the varying load distribution during the day
Steps to Configure Operation Modes
1. Create operation mode
2. Set up work process distribution as defined for the instance
3. Adjust work process distribution
4. Define schedule
Two particular types of work processes are the reserved work processes and
the dynamic work process
Reserved Work Processes are always of type dialog
Dynamic work process are started only in the profile parameter
rdisp/dynamic_wp_check=TRUE is set.
The Operetion mode switching with dynamic and reserved work processes
shows that the reduction of dialog workprocesses by 2, the reduction of
reserved work processes by one and increase of Batch processes by one results
the following image by the opating type Night.
Monitoring and Consistency Check (RZ03)
The Control Panel allows you to monitor the instances and the operation modes
and provides functions to:

Check the status of all instances and of the operation modes

Manually switch operation mode
Display an overview of the work processes
Switch to the Alert Monitor

Unit 5 Lesson: Overview of the Administration Tools

29.
Name various configuration and administration tools for
SAP NetWeaver AS Java
SAP NetWeaver Administrator
Config Tool
SAP Management Console
Shell Console Administrator
30.
Describe the primary usage areas of configuration and
administration tools
Config Tool
o Configuration of the Java VM parameters
o Configuration of services, managers and application
SAP NetWeaver Administrator
o Display of service, manager, and application properties and
parameters.
o Starting and stopping intances processes, services and
application
o Monitoring and configuration of different system functions
and applications
SAP Management Console
o Starting and stopping instances and processes
o Monitoring the processes and special funcitons
o Analyzing of logs and traces
Shell Console Administrator
o Emergency tool
o Stopping processes
o Starting and stopping services and applications
o Displaying and changing settings
Unit 5 Lesson: Basic Configuration of AS Java with the Config Tool
31.
Maintain settings for the SAP NetWeaver AS Java with the
Config Tool
The memory area of a Java Virtual Machine is mainly divided into 3
areas; young generation, tenured generation and permanent generation.
The Garbage Collector forms part of the VM is to prevent the occurrence
of situations in which there is a danger of memory bottlenecks.
The memory space that is available is called the available memory or
allocated memory. The memory space that is actually used by Java
applications is referred to as used memory.
Unit 5 Lesson: Further Configuration Activites
32.
Check and maintain properties of the Central Services
The Central Services consist of the message server and the enqueue
server. The internal communication port for the message server is

defined using the parameter rdisp/msserv_internal. The HTTP port of the

message server is specified with the profile parameter ms/server_port_0.
The profile parameters that are relevant for the enqueue server in the
instance profile of the Central Services instance. The port is usually set
to 32<instance number> and the instance number is defined using the
parameter enque/serverinst
33.
34.