1/22/2020

SAP NetWeaver Library: Function-

Oriented View
Generated on: 2020-01-22

SAP NetWeaver 7.5 | SPS07

PUBLIC

Original content: https://help.sap.com/viewer/ff18034f08af4d7bb33894c2047c3b71/7.5.7/en-US

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/viewer/disclaimer.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 1/115
1/22/2020

SAP NetWeaver Library: Function-Oriented

View
Note
The following image contains links to more information.

Application Server
Overview
The purpose of an SAP NetWeaver Application Server is to provide programmers with an efficient means of expressing business
logic and relieve them from the necessity of platform-related and purely technical coding.

An application server achieves this goal by de ning a programming model based on a set of abstractions that represent the
underlying platform and technical resources that a programmer has to manipulate.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 2/115
1/22/2020
Different application servers usually differ with respect to the set of abstractions which they expose as well as with respect to the
programming language which they support.

Systems and Instances

An SAP NetWeaver Application Server comprises speci c entities called “System” and “Instance”. The two terms are often used
incorrectly and this can cause confusion. Below is a de nition of the most important entities contained in ABAP and Java systems.
Their relationship to each other is also described.

SAP system – installed software system that provides a de ned set of functionalities that are part of an SAP solution.
These functionalities are implemented in a set of software components. An SAP system is installed and con gured as a
unit. It consists of a logical database, one or more application server instances (ABAP or Java), central services (such as a
message server and enqueue server), and optional components (such as TREX and liveCache). The system is identi ed by
its SAP system ID, which consists of 3 letters or digits (e.g. PRD).

Application server instance – administrative unit that puts together components of an SAP system running on one
physical host. Application server instances provide the actual data processing functions of a system and offer the
corresponding services. Instances are started, stopped, and monitored as one unit. There can be multiple instances
(belonging to the same system or to different systems) on one host. An instance can be uniquely identi ed by the host
name and a two-digit instance number.

There are ABAP systems and Java systems. These system types are built in the same way from the corresponding instance type. A
system can have only one system type. ABAP instance or Java instance.

The instance types in turn consist of different processes.

The main instance types are the following:

ABAP server instances are often called “dialog instances”. This term is however incorrect because ABAP server instances
and client requests also work as background jobs. They consist of common components such as ICM (Internet
Communication Manager), IGS (Internet Graphics Server), and ABAP work processes of different types: dialog (for mostly
interactive use), batch (for background processing), update (for update processing, which plays an important role in the
ABAP transaction model), and spool (for printing) depending on the purpose of the instance and the work load
characteristics.

Java server instances consist of common components such as ICM, IGS, and Java server processes, each running on one
Java Virtual Machine (JVM).

Central services instance (SCS) – each ABAP or Java system has one SCS consisting of a message server for
communication between instances and an enqueue server for lock management.

In addition to the instance types described here there are others, such as TREX, Web Dispatcher, and enqueue replication
server.

Documentation Structure
The documentation structure re ects the different types of application servers and the infrastructure componets used by both
stacks.

Chapter Content

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 3/115
1/22/2020

Chapter Content

Application Server Infrastructure

Architecture of Application Server

Internet Communication Manager

Standalone Enqueue Server

Connection

SAP Web Dispatcher

SAProuter

IPv6 Support in SAP NetWeaver

Reverse Invoke

Adaptive Computing

SAP Management Console (SAP MC) and SAP MMC

System Landscape Directory

Application Server ABAP

ABAP Development

Administration tools for AS ABAP

Development of the presentation layer

ABAP-Based Services

Application Server Java

AS Java (Application Server Java)

Developing Java EE 5 Applications

Using Central Development Services

Developing Java Web Dynpro Applications

Find services in the services registry

Con guring the Services Registry

Con guring, Working with and Administering System Landscape

Directory

Application Server Infrastructure

Use
The following links give you an overview of Application Platform features and services:

Topic Features

Architecture of the SAP NetWeaver Application

Server Architecture of SAP NetWeaver Application Server ABAP

Architecture of SAP NetWeaver Application Server Java

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 4/115
1/22/2020

Topic Features

Components of SAP NetWeaver Application Server

Internet Communication Manager (ICM) - SAP NetWeaver

SAP Web Dispatcher

Gateway

Monitoring and Administration of the SAP Message Server

Standalone Program SAProuter

Standalone Enqueue Server

SAP Start Service

The Startup Framework for AS Java

Functions and Tools of SAP NetWeaver Application

Server Connectivity

IPv6 Support in SAP NetWeaver

Reverse Invoke

The sapcpe Program

System Landscape Directory Security Guide

Architecture of the SAP NetWeaver

Application Server
SAP NetWeaver Application Server Application Server can be installed in various speci cations depending on the SAP product and
applications used. You differentiate between ABAP systems and Java systems. Depending on the SAP product used, not every
speci cation may be available.

Architecture of the SAP NetWeaver Application Server

A pure ABAP system provides the complete infrastructure for developing and running ABAP-based applications. With an installed
ABAP system, both ABAP applications and selected SAP Java applications can be run.

Application Server Java provides a Java platform Enterprise Edition 5 (Java EE5) compliant environment for developing and
running Java EE programs. With a Java installation you can run Java EE applications, but not any ABAP applications.

Since the architecture of SAP NetWeaver Application Server depends on the speci cations installed, below is a list of references to
system-speci c architecture documentation.

Related Information
Architecture of SAP NetWeaver Application Server ABAP
Architecture of SAP NetWeaver Application Server Java

Architecture of SAP NetWeaver Application

Server ABAP
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 5/115
1/22/2020
SAP NetWeaver Application Server for ABAP provides both the runtime environment and the development environment for all
ABAP programs.

The design of SAP NetWeaver Application Server is aimed at providing an exceptionally high level of robustness and supportability
for the applications running on it. The architecture of SAP NetWeaver Application Server ABAP and basic terminology are
explained below. For details, see the component-speci c documentation.

Instances of SAP NetWeaver Application Server ABAP

An SAP NetWeaver Application Server ABAP system has various instances. An instance is an administrative unit containing
various components of an SAP system. The components of an instance are parameterized in a shared instance pro le. Each
instance is identi ed by a system ID and an instance number. A distinction is made between application server instances and
ABAP SAP Central Services instances (ASCS instances).

There can be any number of application server instances in an SAP NetWeaver application server. The instances process incoming
user requests. An ABAP application server instance contains one Internet Communication Manager, one ABAP dispatcher, one
gateway, one SAP start service, and any number of work processes.

As well as multiple application server instances, there is one special instance that contains the message server, the enqueue
server, and a separate start service - the ASCS instance (ABAP System Central Services instance). The ASCS instance cannot
process any dialog requests - it is used to manage locks, exchange messages, and balance workload in the SAP system.

Overview of the Components of SAP NetWeaver Application Server ABAP

SAP NetWeaver Application Server ABAP is made up of the following components:

Internet Communication Manager (ICM)

ABAP dispatcher

Task handler

Any number of work processes (dialog, update, print, background, and so on)

RFC Gateway

Standalone enqueue server

SAP Message Server

The system can be enhanced with the following optional components:

SAP Web Dispatcher

SAProuter

The following gure shows the components of an ABAP system. For a better overview, series lines have not been used. Incoming
requests are handled directly by the Internet Communication Manager or SAP Web Dispatcher, ABAP Dispatcher, or Gateway,
depending on the request type. There is one database for each ABAP system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 6/115
1/22/2020

Architecture of SAP NetWeaver Application

Server Java
Use
Application Server Java provides a Java platform Enterprise Edition 5 (Java EE5) compliant environment for developing and
running Java EE programs. With this installation you can run Java EE applications but not ABAP programs.

The design of SAP NetWeaver Application Server is aimed at providing an exceptionally high level of robustness and supportability
for the applications running on it. The architecture of SAP NetWeaver Application Server Java and basic terminology are explained
below. For details, see the component-speci c documentation.

Instances of SAP NetWeaver Application Server Java

An SAP NetWeaver Application Server Java system has various instances. An instance is an administrative unit containing various
components of an SAP system. The components of an instance are parameterized in a shared instance pro le. Each instance is
identi ed by a system ID and an instance number.

A distinction is made between application server instances and system central services instances (SCS instances).

There can be any number of application server instances in an SAP NetWeaver Application Server for Java application. The
instances process incoming user requests. A Java application server instance contains one Internet Communication Manager, one
SAP start service, and any number of Java server processes.

As well as multiple application server instances, there is one special instance that contains the message server, the enqueue
server, and a separate start service - The SCS instance (system central services instance). The SCS instance cannot process any
dialog requests - it is used to manage locks, exchange messages, and balance workload in the SAP system.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 7/115
1/22/2020

Components of SAP NetWeaver Application Server Java

Java server processes

Startup framework

Internet Communication Manager

Enqueue Server

Message Server

SAP Start Service

The following gure shows the components of a Java-only system. For a better overview, series lines have not been used. Incoming
requests are accepted by the Internet Communication Manager and distributed to the Java server processes. There is one
database for each Java system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 8/115
1/22/2020

Components of SAP NetWeaver Application

Server
Use
SAP NetWeaver Application Server Application Server can be installed in various speci cations depending on the SAP product and
applications used. You differentiate between ABAP systems and Java systems. Depending on the SAP product used, not every
speci cation may be available. The components of SAP NetWeaver Application Server, based on installed features, are listed
below. Optional components, such as SAP Web Dispatcher, are listed too.

Overview of the Components of SAP NetWeaver:

Component Description

Components of SAP NetWeaver AS for ABAP

Internet Communication Manager (ICM) - SAP NetWeaver

SAP Web Dispatcher

Gateway

Monitoring and Administration of the SAP Message Server

Standalone Program SAProuter

Standalone Enqueue Server

SAP Start Service

Task handler

ABAP work processes:

Updates in the SAP System (BC-CST-UP)

The SAP Lock Concept (BC-CST-EQ)

SAP Printing Guide (BC-CCM-PRN)

Background Processing

Components of SAP NetWeaver AS for Java

The Startup Framework for AS Java

SAP Start Service

Java server processes

SAP Start Service

Use
The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on
Windows, and as a daemon on UNIX. The process is called sapstartsrv.exe on Windows, and sapstartsrv on UNIX
platforms.

The SAP start service provides the following functions for monitoring SAP systems, instances, and processes.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000a… 9/115
1/22/2020
Starting and stopping

Monitoring the runtime state

Reading logs, traces, and con guration les

Technical information, such as network ports, active sessions, thread lists, etc.

These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,
SAP NetWeaver Administrator, etc.).

Features
Ports

The start service connects the following ports:

HTTP port 5<xx>13 (or sapctrl <xx> in /etc/services), where<xx> is the number of the instance

HTTPS port 5<xx>14 (or sapctrls <xx>) in /etc/services), where <xx> is the number of the instance

 Example
The start service uses HTTP port 50013 and HTTPS port 50014 for an instance with number 00.

Security

The standard SAP setup is used for secure SSL communication.

If critical functions (“protected methods”, such as restarting an instance) are not called using a trusted connection, they require
authentication with operating system user and password. On UNIX platforms trusted connections go through UNIX domain
sockets (/tmp/.sapstream<port-no>), and on Windows they go through “Windows named pipe” (\\
<host>\pipe\sapcontrol_<xx>)

Integration

The start service is registered automatically in LDAP (Lightweight Directory Access Protocol) if ldap/autoregister = 1 is
set in the pro le.

The start service is registered automatically in SAP SLD (System Landscape Directory). File slddest.cfg is required in
directory DIR_GLOBAL for the registration.

The Web service interface is compatible with the following SOAP implementations: SAP ABAP, SAP JEE, Java Axis, Microsoft .NET.

Process
An SAP instance is started differently on Windows and UNIX platforms.

 Caution
For both operating systems, the start service requires the SAP pro le. If this is not found, the service cannot start. You can nd
the related error message in le sapstartsrv.log.

UNIX

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 10/115
1/22/2020
The instance is started by the sapstartsrv process, and not directly by the start service sapstart. The process is started by
the start service, which ideally is started by the sapinit script when the operating system is booted.

The following gure shows how these processes t together:

Figure 1: Startup on UNIX Platforms

You can also still use the startsap and stopsap scripts to start and stop the instance (standard procedure in older releases).

Windows

On Windows the instance is started directly by the start service (process sapstartsrv.exe). The start service is started
automatically when the operating system is booted.

The start service reads the instance pro le and executes all commands in the instance pro le that contain an Execute_
statement. It then starts the processes of the SAP instance in the order in which the Start_Program_ statements are listed in
the pro le.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 11/115
1/22/2020

Figure 2: Startup on Windows Platforms

More Information
Systems and Instances

An SAP NetWeaver Application Server comprises speci c entities called “system” and “instance”. The two terms are often used
incorrectly and this can cause confusion. Below is a de nition of the most important entities contained in ABAP systems and Java
systems. Their relationship to each other is also described.

SAP system – installed software system that provides a de ned set of functionalities that are part of an SAP solution.
These functionalities are implemented in a set of software components. An SAP system is installed and con gured as a
unit. It consists of a logical database, one or more application server instances (ABAP or Java), central services (such as a
message server and enqueue server), and optional components (such as TREX and liveCache). The system is identi ed by
its SAP system ID, which consists of 3 letters or digits (e.g. PRD).

Application server instance – administrative unit that puts together components of an SAP system running on one
physical host. Application server instances provide the actual data processing functions of a system and offer the
corresponding services. Instances are started, stopped, and monitored as one unit. There can be multiple instances
(belonging to the same system or to different systems) on one host. An instance can be uniquely identi ed by the host
name and a two-digit instance number.

There are two types of systems: ABAP system, Java system. The system types consist of the corresponding instance types in a
homogeneous way, meaning only one type is permitted in the system: ABAP instances or Java instances.

The instance types in turn consist of different processes.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 12/115
1/22/2020
The main instance types are the following:

ABAP server instances are often called “dialog instances”. This term is however incorrect because ABAP server instances
and client requests also work as background jobs. They consist of common components such as ICM (Internet
Communication Manager), IGS (Internet Graphics Server), and ABAP work processes of different types: dialog (for mostly
interactive use), batch (for background processing), update (for update processing, which plays an important role in the
ABAP transaction model), and spool (for printing) depending on the purpose of the instance and the work load
characteristics.

Java server instances consist of common components such as ICM, IGS, and Java server processes, each running on one
Java Virtual Machine (JVM).

Central Services Instance (SCS) - Every ABAP or Java system has one SCS consisting of a Message Server for
communication between instances and an Enqueue Server for lock management.

In addition to the instance types described here there are others, such as TREX, Web Dispatcher, and enqueue replication
server.

Monitoring Tools:

The following monitoring tools use the Web service interface:

SAP Microsoft Management Console: Windows

SAP Management Console

SAP NetWeaver Administrator

sapcontrol: with sapcontrol (process name on Windows sapcontrol.exe) you can call the functions of the Web
service interface from the command eld. sapcontrol -h shows the syntax and the available options.

You can nd information for developers about using SAPControl Web services in SDN at
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60e24f7b-1ba1-2b10-c0a0-e514b855624b&overridelayout=true

The Startup Framework for AS Java

Use
You can start, stop, and monitor the AS Java using the Startup Framework for AS Java. This framework provides centralized
management of the Java server processes and monitors their life cycle. In case of cluster node failure, the framework
automatically restarts the corresponding process.

The Startup Framework provides the following services:

It serves as a single point of administration (starting, restarting, stopping, and monitoring) for the AS Java processes.

In case of a process failure, it restarts the corresponding process.

It displays the trace les, the system environment, and the SAP system environment.

It provides options for thread dump monitoring.

This option is critical for the analysis of problem situations (for example, the AS Java is hanging, 100% CPU load).

It provides options for viewing the Java VM output (useful in case of a Java server crash).

More Information
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 13/115
1/22/2020
Architecture of the Java Startup Framework : explains the components as well as the starting and stopping process on a
technical level.

Administration of the Java Startup Framework : describes administration and troubleshooting tasks related to the startup
framework.

Con guration of the Java Startup Framework : describes command line arguments and pro le parameters that can be
used for con guration of the AS Java startup and operation process.

Starting and Stopping the Application Server Java: explains how to start and stop an AS Java instance or the whole SAP
system.

SAP JVM : contains the documentation regarding SAP's Java virtual machine.

Architecture of the Java Startup Framework

Use
This section contains a detailed description of the components of the Java Startup Framework, their interaction and
communication, and the architecture of the Java Startup Framework. You can follow the steps when starting, monitoring, or
stopping an AS Java instance.

Structure
The Java Startup Framework is implemented in the JSTART program.

The JSTART program has two roles:

When running as the Java instance controller, JSTART starts, stops, and monitors the processes of a Java instance (the
ICM process and several Java server processes). In this role, JSTART provides a local port for command communication
and implements the SAP signal handling to stop the instance.

In the role of a server process, JSTART connects to the Java instance controller before loading the Java VM into its address
space. It then starts the AS Java code and represents the Java server process. The program can receive commands from
the Java instance controller and reports the status of the Java server to the instance controller. A Java server process stops
immediately when it detects that the Java instance controller has terminated unexpectedly.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 14/115
1/22/2020

Integration
The Java Startup Framework is called in different ways depending on the operating system and installation type:

In an ABAP+Java instance, the ABAP dispatcher calls the JSTART program.

In a pure AS Java installation, the following distinction applies:

Under Windows, the SAP Start Service calls JSTART to start an AS Java instance.

Under UNIX and OS/400 platforms, the SAP Start Service uses the startsap and stopsap scripts to call the
JSTART program.

More Information
AS Java Startup Framework (contains general information about the components of the Java startup and control
framework)

Startup, Operation and Shutdown of a Java Instance

For more information about the AS Java cluster and system architecture, and about the communication between the AS
Java and the other components within the SAP NetWeaver Application Server, see the AS Java Architecture Manual .

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 15/115
1/22/2020

Startup, Operation and Shutdown of an AS

Java Instance
Use
With the Java Startup Framework you can start, monitor, and stop a Java instance and its processes. This means you can:

Start, stop or restart processes

Stop or restart the whole instance

Terminate hanging processes

The JSTART program is part of the standard delivery.

Process
Startup of the Java Instance

The following steps are involved in starting the Java instance:

1. JSTART is started (in Windows by the SAP Start Service; on UNIX platforms by the startsap script). It takes the role of the
Java instance controller.

2. The Java instance controller analyzes its con guration (from the instance pro le) and examines the details of the Java SDK
de ned there.

3. The Java instance controller initializes SAP signal handling to be able to receive signals and opens the control port.

4. The Java instance controller reads the instance description (from the list of les speci ed by the
jstart/startupNodeFiles and jstart/instanceNodeFiles pro le parameters) for the rst time, searching
for nodes with a runLevel=1 property. The OFFLINE DEPLOYMENT node in the startup.properties le matches this criterion.

5. The Java instance controller starts another JSTART process with the parameters from the OFFLINE DEPLOYMENT node
and waits for the child process to terminate.

6. The child process acts as a Java process. It loads the Java Virtual Machine (JVM) into its own process, initializes the JVM
and starts the OFFLINE DEPLOYMENT program, which performs the deployment steps in the Java database.

7. The Java instance controller reads the instance description again, searching for nodes with a runLevel=2 property. The
BOOTSTRAP node in the startup.properties le meets this condition.

8. The Java instance controller starts another JSTART process with the parameters from the BOOTSTRAP node and waits for
the child process to terminate.

9. The child process loads and initializes the JVM and starts the BOOTSTRAP program. BOOTSTRAP synchronizes the binary
data in the Java database with the local le system, reads the Java instance description from the Java database and
updates the instance.properties le.

10. The Java instance controller reads the instance description from the startup.properties and
instance.properties les once more, this time focusing on nodes with a runLevel=3 property or without a
runLevel property at all. These nodes form the productive instance.

11. The Java instance controller starts the processes for infrastructure nodes, such as ICM or DEBUGPROXY.

12. When all infrastructure processes are started, the Java instance controller starts the processes for the server nodes.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 16/115
1/22/2020
13. The JSTART child processes act as Java processes and execute a similar sequence as described before. They become the
Java server processes.

The following gure shows the sequence of actions that the Java Startup Framework executes.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 17/115
1/22/2020

Operation of the Java Instance

The Java instance controller monitors the Java instance. It receives the status update messages and catches termination signals
from the child processes. When a process terminates unexpectedly, the Java instance controller starts the process again.

Shutdown of the Java Instance

Signals and commands sent to the control port trigger a Java instance to stop. The Java instance controller ensures that the order
of shutdown is obeyed and forces termination if a process does not stop within the shutdown timeout period.

The gure below shows the sequence of the actions.

An instance is stopped as follows:

1. A process (for example, the ABAP dispatcher, a start script or SAP Start Service) sends a SIGINT signal or an appropriate
command to the Java instance controller.

2. The Java instance controller updates the instance state and sends STOP commands to the server processes.

3. When the server processes are nished, the Java instance controller sends STOP commands to the infrastructure
processes.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 18/115
1/22/2020
4. Once all child processes have exited, the Java instance controller terminates.

More Information
AS Java System Architecture

Administration of the Java Startup

Framework
Procedure
The administration of the Java Startup Framework consists of the following procedures:

Administration and monitoring with the SAP Management Console

Administration and monitoring with the command line program jsmon

Monitoring and interpreting the trace and log les created by the framework, analyzing the error messages in them,
incrementing/decrementing the trace levels, creating stack traces

More information:

Developer Trace and Log Files

Incrementing/Decrementing the Trace Level

Creating a Java Thread Dump

More Information
Architecture of the Java Startup Framework

Con guration of the Java Startup Framework

Using the Command Line Program jsmon

Prerequisites
The AS Java instance is running.

You are logged on at operating system level to the computer where the AS Java instance is running. In the following <profile>
refers to the name of the pro le le with which the Java instance controller was started.

Context
The jsmon program is a command line program for monitoring and management. It provides a means to inspect the state of a
Java instance "directly", that is with as few infrastructure demands as possible.

 Recommendation
Use this program only if really necessary. SAP recommends using the Management Console.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 19/115
1/22/2020

Procedure
1. Call jsmon pf=<path to profile> from the command line.

The JStart Monitor Program is started. Some options are displayed.

2. Call -help .

A detailed list of possible commands and corresponding operations is displayed.

3. Refer to that list when performing operations.

Developer Trace and Log Files

Use
The trace and log messages of the Java Startup Framework contain important information about the status of the Java instance.
In case of errors, check and analyze these messages.

The developer trace and log les are located in the /usr/sap/SID/inst_name/work directory, where SID is the system ID
of the cluster (for example, C11) and inst_name is the instance name of the instance (for example, DVEBMGS00 or JC01).

Structure
The following trace les provide useful information in case of errors.

dev_jstart

This is the trace le of the Java instance controller.

 Recommendation
We recommend that you always check the end of this le for error messages regarding the startup of the AS Java instance.

dev_<component name>

The trace le of the corresponding JSTART server process (the <component name> can be deployment, bootstrap,
server<n>, or icm). For example, the trace le for the bootstrap process is dev_bootstrap.

std_<component name>.out

The standard and error output le of the corresponding JSTART server process (the <component name> can be deployment,
bootstrap, server<n>, or icm).

For example, the output le for the offline deployment process is std_deployment.out. Output and error messages from the
Java VM are written to this le.

jvm_<component name>.out

The standard and error output le of the JVM running the corresponding JSTART server process (the <component name> can
be deployment, bootstrap, or server<n>).

For example, the output le for the JVM running the bootstrap process is jvm_bootstrap.out.

More Information
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 20/115
1/22/2020
Incrementing/Decrementing the Trace Level

Creating a Stack Trace

Incrementing/Decrementing the Trace Level

Use
Use this procedure to increment/decrement the trace level for the developer trace les ( dev_jcontrol, dev_<component
name>) of the processes. By default, the trace level is set to 1. In some critical cases and in problem analysis, we recommend that
you increase the trace level to log more information in the developer trace les.

The value range of the trace level property can be between 0 (lowest) and 3 (highest):

0: No trace

1: Write error messages in the trace le.

2: Full trace. The trace entries that are actually written can vary with the program that is being traced.

3: Additionally, trace data blocks.

Procedure
1. Start the SAP Management Console (SAP MMC under Windows, SAP MC under UNIX).

2. Select a process from the process list.

3. From the context menu, choose one of the following:

To increment the trace level, All Tasks Increase trace level (signal URS2)

To decrement the trace level, All Tasks Decrease trace level (signal URS1)

To view the trace le, choose Developer Trace from the context menu.

Alternatively, you can send the signals USR2 and -USR1 to a process from the command line using the kill (UNIX) or the
sapntkill (Windows) command.

 Example
kill -USR2 <pid> increases the trace level of the UNIX process with the process ID <pid> .

More Information
SAP Management Console

SAP Microsoft Management Console: Windows

Creating a Java Thread Dump

Procedure

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 21/115
1/22/2020
1. Start the SAP Management Console.

2. Locate the process for which you want to create a stack dump in the AS Java Process Table .

3. From the context menu, choose Dump Stack Trace.

Results
The stack dump is written to the std_<component name>.out le located in the
/usr/sap/<SID>/<inst_name>/work directory.

 Note
The location of the stack dumps may differ depending on the Java SDK being used.

Next Steps
SAP Management Console

SAP Microsoft Management Console: Windows

Con guration of the Java Startup

Framework
Use
This section explains the command line arguments and the pro le parameters relevant to the operation of the Java Startup
Framework.

Procedure
Use this information to tune some speci c features in the Java Startup Framework. Typically, you will not need to con gure the
framework.

Command line arguments for the Java Instance Controller : The command line arguments for the Java instance controller
may occur in the developer trace of the Java instance controller or in the instance pro le for a Java-only instance.

More information: Command Line Arguments for the Java Instance Controller

Con guration les : The instance pro le contains the most important SAP pro le parameters used by the JSTART
program. These parameters apply to the whole AS Java instance. The le is located in
/usr/sap/<SID>/SYS/profile/<SID>_<inst_name>_<hostname>.

More information: SAP Pro le Parameters

Command Line Arguments for the Java

Instance Controller
Use

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 22/115
1/22/2020
The command line arguments for the Java instance controller may occur in the developer trace of the Java instance controller or
in the instance pro le for a Java-only instance.

Command Line Arguments

SAP Instance Pro le

The SAP instance pro le that contains all properties related to the AS Java instance. This le is normally created by SAPinst and
contains the SAP instance properties, such as SAPSYSTEM (system number) or SAPSYSTEMNAME (system ID), and so on.

Program argument: pf=<filename>

Internal default value: this parameter is mandatory; there is no default value

Bootstrap Mode

This option allows you to skip the offline deployment and bootstrap phases when the Java instance is started.

Program argument: -bootstrap=[yes/no]

SAP pro le property: jstart/bootstrap = [yes/no]

Internal default value: yes

Trace Level

The trace level is con gured in the instance pro le; it can be overridden for the Java instance controller with this argument.

Program argument: -tracelevel=[0..3]

SAP pro le property: jstart/TRACE = [0..3] or rdisp/TRACE = [0..3]

Internal default value: 1

Special Command Line Arguments

The following command line arguments are used by the JSTART processes to con gure the runtime behavior or to tune some
speci c properties and options.

 Caution
You cannot use these command line arguments to con gure the Java Startup Framework. These arguments are documented
here for trace le analysis only.

Shared Memory Node ID

The Java instance uses shared memory for administration, monitoring and session management. Each process that accesses this
shared memory needs a node ID that identi es the process and assigns a part of the shared memory for status reporting.

Program argument: -nodeId=<shared memory ID>

Internal default value: -1 (no relation to a shared memory segment)

Java System Properties

The Java VM provides a set of system properties, which can be extended during Java VM initialization. This command line
argument is added to the initial set of Java system properties. It may occur several times with different <name>=<value> pairs.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 23/115
1/22/2020
Program argument: -hostvm

Internal default value: -D<name>=<value>

Operation Mode

The JSTART program can operate in three different modes: Java instance controller, Java launcher, or host process for a Java VM.
This argument assigns the Java VM host mode.

Program argument: -hostvm

Internal default value: depends on the presence of several other command line arguments if the mode is not explicitly
assigned

Node Name

The node name speci es the section in the node de nition le that de nes the node. This (technical) name may differ from the
(visible) name of the node in the trace le and the management UIs

Program argument: -nodeName=<node name>

Internal default value: none

Node De nition File

This le contains the parameters for the node being represented by the JSTART process.

Program argument: -file=<file name>

Internal default value: none

Java SDK Con guration File

When JSTART operates as a Java instance controller or Java launcher, it analyzes the Java SDK de ned in the node de nition and
instance pro le. It then stores the results in the Java SDK con guration le and shares them with the Java host processes.

Program argument: -jdkFile=<file name>

Internal default value: none

Developer Trace File

The name of the developer trace le. More information: Developer Trace and Log Files .

Program argument: -traceFile=<file name>

Internal default value: none, trace messages are written to the standard output stream

Detailed Protocol in the Trace File

This option controls the output of the command line options and arguments passed to the child processes, Java VM and Java
main method.

Program argument: -protocol=[on/off]

Internal default value: jstart/protocol

Java VM Output Redirection

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 24/115
1/22/2020
This option allows you to redirect the standard and error output of the Java VM to a speci ed le.

Program argument: -jvmOutFile=<file name> or -javaOutFile=<file name>

Internal default value: none

Activate Debug Mode

This option activates Java debugging with the debugging agent. It is used to enable debugging with Java VMs from other vendors

Program argument: -debugMode=[yes/no]

SAP pro le property: jstart/debugMode

Internal default value: no

Additional Environment Settings

This option allows you to add environment settings to JSTART. The value has to be in the format:
envvar1=value;envvar2=value;…

Program argument: -environment=<list of environment variables>

SAP pro le property: jstart/environment

Internal default value: none

More Information
SAP Pro le Parameters

SAP Pro le Parameters

Use
The instance pro le contains the important SAP pro le parameters used by the JSTART program. These parameters apply to the
whole AS Java instance. The le is located in /usr/sap/<SID>/SYS/profile/<SID>_<instance
name>_<hostname>.

You can edit this le by using a text editor (if you have a Java-only installation) or by using transaction RZ10 (if you have a double-
stack system).

 Note
When editing this le, make sure that there is an empty line at the end of the le.

Structure
The following table contains the description of the instance pro le parameters.

 Recommendation
For normal operation, you will not need to change the default parameter settings. Use the following list if you really need to
change settings.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 25/115
1/22/2020

Pro le Parameter Description Unit Default Value

( old name in parantheses)

jstart/bootstrap Controls whether the initial Logical value True

offline deployment and
( jstartup/bootstrap)
bootstrap phases happen
when an AS Java instance
starts.

jstart/protocol Activates additional protocol Logical value True

output in the developer trace
( jstartup/protocol)
le.

jstart/debuggable Protects an instance against Logical value True

debugging, e.g. for
( jstartup/debuggable)
productive use.

jstart/debug_mode Activates Java debugging for Logical value false

all server processes. A Java
( jstartup/debug_mode)
VM in debugging mode is
extremely slow. When using
the SAP JVM, debugging can
be activated if necessary, i.e.
"on the y".

jstart/environment May contain additional Character

environment variables that string
( jstartup/environment)
are passed by the instance
controller to the Java
processes.

jstart/startupNodeFile Speci es the name of the le Character $(DIR_EXECUTABLE)/startup.properties

that contains the node string
( jstartup/startup_properties)
de nitions for the bootstrap
and offline deployment
phases.

 Note
Do not change the value
of this parameter.

jstart/instanceNodeFiles Provides the list of les Character <computed at runtime>

de ning the nodes that build string
(
the instance.
jstartup/instance_properties)

 Note
Do not change the value
of this parameter.

jstart/stackSize Stack size (in bytes) for the Whole The value is platform-dependent. It is 256k on
Java VM thread. number; 32-bit platforms, 1m on 64-bit Unix platforms,
( jstartup/native_stack_size)
may contain and 2m on 64-bit Windows platforms.
k , m or g as
scaling
factors.

jstart/vm/home Path to the root directory of Character $(DIR_SAPJVM)

the Java SDK string
( jstartup/vm/home)

jstart/vm/type Java VM type (for example, Character

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 26/115
1/22/2020
jstartup/vm/type server , classic , or string
client ).

The values are vendor-

speci c - refer to the Java
VM vendor's documentation.

jstart/vm/args Additional VM parameters Character

for all nodes (for example, string
( jstartup/vm/parameters)
DsomeName=someValue )

jstart/vm/libPath Speci es a list of directories Character

containing shared libraries. string
( jstart/vm/libpath)
If this parameter is set, its
value overrides the
directories found during Java
SDK detection.

jstart/vm/dllname File name of the Java VM Character

shared library (if the library string
( jstartup/vm/dllname)
name is not "jvm").

This parameter can be used

to run a debug version of the
Java VM that has a different
le name.

jstart/nice Allows you to run the node Logical value false

processes at lower priority,
( jstartup/nice)
e.g. on desktop systems.

This feature is available only

on Windows.

DIR_EXECUTABLE Directory where the Character

executable les for the string
startup framework are
located.

SAPSYSTEMNAME SAP system name. (SID) Character

string with
three
characters

SAPSYSTEM SAP instance number. Whole

number
(between 00
and 97)

jstart/TRACE Speci es the trace level for Whole Value of the rdisp/TRACE parameter.
the information logged in the number
developer trace les. (between 0
and 3)
More information:
Incrementing/Decrementing
the Trace Level .

jstart/TRACE_COMPS Speci es the trace Character Value of the rdisp/TRACE_COMPS parameter

components that may trace string
at a higher trace level. consisting of
letters for
the trace
components
and the

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 27/115
1/22/2020
strings All
or all .

jstart/TRACE_LOGGING Restricts the size of the Character The value of the rdisp/TRACE_LOGGING
developer traces. string with parameter
the following
syntax: off
| on, <n>
[ k | m ]

jstart/traceVersions Speci es the number of Whole 5

backup versions for trace number
( jstartup/keep_old_logfiles)
and log les. (between 0
and 99)
The JSTART program
replaces the last one or two
digits of the extension with
the backup generation or
appends an ".n" extension to
les that have no extension.

jstart/shutdownTimeout Speci es the shutdown Seconds 120

timeout, i.e. the grace period
( jstartup/shutdown_timeout)
for the AS Java instance to
shut down before the Java
process terminates itself.

j2ee/ms/connectTimeout Speci es the timeout for the Seconds 60

rst connection to the
( jstartup/wait_for_scs)
message server.

The AS Java instance fails to

start if this timeout expires.

j2ee/ms/reconnectTimeout Speci es the timeout for the Seconds 3600 (one hour)
reconnecting to the message
( jstartup/wait_for_reconnect)
server.

The AS Java instance shuts

down when this timeout
expires.

More Information
Administration of the Java Startup Framework

Functions and Tools of SAP NetWeaver

Application Server
Use
SAP NetWeaver Application Server Application Server can be installed in various speci cations depending on the SAP product and
applications used. You differentiate between ABAP systems and Java systems. Depending on the SAP product used, not every
speci cation may be available, and therefore not all the functions and tools listed.

Topic Description

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 28/115
1/22/2020

Topic Description

Connectivity Enables the exchange of application data between different SAP systems and with
non-SAP systems.

IPv6 Support in SAP NetWeaver Usage of IP (Internet Protocol) Version 6 for network communication (both within
SAP systems and beyond)

Reverse Invoke Reverse invoke is the technology that enables network connections to be set up
from a secure network (Intranet). This increases network security since no external
connection can get through the rewall into the network.

The sapcpe Program With program sapcpe you can organize your directory tree locally.

System Landscape Directory The System Landscape Directory is the central information repository for your
system landscape. It contains information about all installable and installed
components in a system landscape.

Application Server ABAP

Use
The SAP Web Application Server provides a complete development and runtime environment for ABAP-based applications. It is
optimized for the development of highly scalable business applications.

The ABAP development environment is used both for developing completely new applications and extending and modifying SAP
standard applications for customers. The entire, powerful infrastructure of the Web AS can be used, which even supports the
creation of the most complex applications by large groups of developers.

The ABAP technology can be used to implement complete applications including user interfaces. However, it is also possible to
implement only the core components of an application, such as the business logic and persistence in ABAP and to use de ned
interfaces (RFC, BAPIs, Web Services and so on) so that a Java-based interface can be used, or to make other applications
available.

Prerequisites

To be able to understand the documentation, users should be familiar with:

1. Basic programming knowledge

2. Database programming in SQL

3. Principles of object-oriented programming

Features
The ABAP development and runtime environment makes it possible to develop complex business applications, without having to
worry explicitly about technical details such as process or memory administration, multi-user capability, database connections or
similar issues. These are provided in the basis services or are integrated directly in the ABAP runtime. The application
development is similarly independent of the underlying platform. The Web AS decouples the application coding completely from
the operating system and database that are used.

ABAP Workbench

In addition to the pure ABAP Editor for creating ABAP source code, the development environment, which is completely integrated
in the server, also provides support for developing extensive projects in the form of:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 29/115
1/22/2020
Versioning support

Structuring the development object in packets

Interface editors for SAP GUI-based interfaces

Development tools for Web interfaces

Support for multi-lingual text elements and messages

Connection to the Transport Organizer

Direct access to all data de nitions in the ABAP Dictionary

Debugger

Tools for runtime analyses

Test tools

Modi cation assistant to compare user-de ned extensions

ABAP development projects are managed directly in the system; metadata and source code are located in the database.

ABAP Objects

The ABAP programming language uni es the advantages of an object-oriented language with those of an integrated 4GL
language. The typical OO language constructions such as classes, interfaces, inheritance and so on are available. Furthermore,
many of the server's services, which are integrated in other languages in the form of libraries and have to be addressed using APIs,
are integrated directly in the language. This includes amongst other things the direct possible use of all data types that are
managed in the central ABAP Dictionary, in particular the integration of database access.

Persistence and Transactions

A central feature of the ABAP development is the direct integration of database access. The runtime environment ensures that
every ABAP program automatically receives an open connection to the central database in the system, so that an application
programmer does not need to worry about opening and closing database connections. ABAP Objects contain Open SQL, a
platform-independent SQL dialect as a direct component of the language. It can be used to execute database accesses directly
without having to use an API or a class library. Buffer mechanisms on the application server-side ensure that highly-scalable,
complex database accesses are possible.

In addition to Open SQL, object services are offered that enable persistent objects to be de ned, whose persistence is completely
taken over by the runtime.

The runtime system provides its own lock mechanism for synchronizing accesses to data in the database. This prevents two
parallel transactions from being able to change the same data in the database. The update enables business processes to be
mapped in transactions, which ensure the integrity of the data.

UI Technologies

With Web Dynpro ABAP, Application Server ABAP provides a programming model based on the Model View Controller principle.
The architecture of this model is identical to that of Web AS ABAP and Web AS Java. Applications that were created using Web
Dynpro for ABAP are displayed using a standard browser on the user's PC.

In the past, the interfaces of classic SAP applications were based on the SAP GUI. In addition to the list-based display of data, the
dynpro technology gives you the option of programming dialogs, which are displayed at runtime using a proprietary protocol in the
SAP GUI. This type of UI programming is still possible, and additional UI programming technologies have been created.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 30/115
1/22/2020
The ITS was introduced so that you can use existing interfaces in the Web whilst keeping the work required to migrate them as low
as possible. In addition to the pure conversion of the GUI interface into the Web protocol at runtime, it is also possible to create
special, HTML-based interfaces, which are mixed at runtime with the data belonging to screens that were developed especially for
this.

The Business Server Pages model follows the server-side scripting approach. Similar to JSPs, this model makes it possible to
create an HTML-based Web application with integrated ABAP. The Business Server Page model is based on the underlying Internet
Communication Framework, which enables it to implement ABAP-based services, which respond to HTTP or HTTPS requests.

Documentation and Translation Tools

The integrated documentation and translation tools are used to create documentation and multilingual applications. New
applications and changes to SAP standard applications can be documented directly. The documentation texts are managed
similarly to the development objects. Multilingual texts can be created separately from the actual program development using the
translation tools. Connection to the transport system means that even complex documentation and translation landscapes can be
created and managed.

More Information
For more information about the Application Server ABAP, see the following sections of the documentation:

Application Development on AS ABAP

Administration of Application Server ABAP

Other Services

Application Server Java

Purpose
With the Java EE 5 certi ed application server that SAP provides you can develop Java EE applications based on the newest Java
EE standard as well as migrate existing J2EE applications.

The Application Server Java (AS Java) comprises features for ensuring its robustness, scalability, and supportability, such as
con gurable session failover support, built-in load balancing support, fast and robust shared memory based on request handling,
and robust monitoring and unique supportability of non-functional problems based on SAP's own Java VM features.

The server offers full support of the latest Java EE 5 features, updates, and adjustments for simplifying the development of
enterprise applications, such as EJB 3.0, the new JSF 1.2, the new Java Persistency API 1.0, the updated Web services stack, and
more. It provides an implementation of the Service Data Objects (SDO) 2.1 standard simplifying data programming for
applications and frameworks, support for development of standard-based portlets, and a job scheduler implementation. With the
Java Connector Architecture (JCA) 1.5 and full Java EE 5 Web Services support it enables connectivity to SAP and non-SAP
backend systems and services.

The Application Server Java provides also Web Dynpro for Java - a complete UI development and runtime environment that
developers can use to create Web-based user interfaces for Java applications. Web Dynpro delivers declarative and graphical
tools, which are fully integrated with the SAP NetWeaver Developer Studio, for rapid design of user interfaces. Its programming
model is aligned with the model-view-controller (MVC) paradigm, which provides a strict separation between UI and business
logic. As a result, developers can use Web Dynpro to create, test and maintain UI designs easily regardless of underlying
components.

Features
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 31/115
1/22/2020
In this section of the documentation, you can nd the following information:

Topic Description

Administering This section provides you with comprehensive information you may require to operate your Application Server Java (AS
Application Java) system optimally. It contains documentation about various con guration, administration, monitoring and software
Server Java logistics tasks and an overview of the tools required to perform them.

Developing This section provides the complete information you need for development Java EE standards-based applications that
Java EE 5 you can deploy and execute in the runtime environment provided by the Application Server Java.
Applications

Using Central This section provides information about a set of APIs at infrastructure-level that you can use to extend your Java
Development applications with common functions, such as logging, monitoring, or job scheduling.
Services

Developing This section provides information about Web Dynpro for Java - a complete UI development and runtime environment
Java Web that developers can use to create Web-based user interfaces for Java applications.
Dynpro
Applications

Discovering This section provides information about how to use the Services Registry to discover available Web services that can be
services in the reused in your SOA-based applications.
Services
Registry

Con guring the This section provides information about con guring the Services Registry in your system landscape.
Services
Registry

You should also consider the security aspects that you may need when operating Application Sever Java.

Solution Life Cycle Management

Use
Solution Life Cycle Management (SLCM) provides you with the technology required for the entire life cycle of your solution, from
its implementation, through running a live system, to continuous modi cations and upgrades.

Features
Solution Life Cycle Management comprises the following key capabilities:

Area Description

SAP Licenses This section gives you an overview of the tools that
manage your SAP licenses.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 32/115
1/22/2020

Area Description

SAP Business Continuity The term "Business Continuity" describes the

efforts to ensure that business-critical functions are
continually available to customers, vendors, and
companies. The aim is to reduce both unplanned
and planned downtimes of an SAP system to a
minimum.

For information about Business Continuity in

general in SAP environments, see the SAP Business
Continuity Guide in SCN at
http://scn.sap.com/community/business-
continuity .

SAP NetWeaver Con guration Here you can nd notes on technical con guration
steps which may be necessary in your SAP
NetWeaver system.

Customizing Customizing settings enable you to adapt the non-

company speci c and industry-speci c functions
shipped in an SAP system to the speci c business
requirements of your enterprise.

Security and User Administration Describes the tools and tasks for maintaining the
security con guration and user master data in your
system.

Starting and Stopping SAP NetWeaver AS Describes how SAP NetWeaver AS is started and
stopped. The procedures assume a central system
that consists of a database and a central instance
(ABAP, Java) on a single host.

Connecting a Technical System to SAP Solution Manager SAP Solution Manager gives you central access to
tools, methods, and precon gured content that you
can use to evaluate and implement your solutions.
When your implementation is running, you can use
SAP Solution Manager to manage and monitor
systems and business processes in your solution
landscape, and also to set up and operate your own
solution support.

Solution Monitoring The monitoring features in IT landscapes monitor IT

components and processes that run across
multiple components. The monitoring results are
displayed in a central system. Any problems are
displayed as alerts. You can use the relevant
analysis methods to go to an appropriate
transaction or tool to evaluate the problem.

SAP Host Agent The SAP Host Agent contains all required elements
for central provisioning, monitoring, and controlling
of any host, instance, database, or SAP system.

SAP Management Console With SAP Management Console, you can start, stop
and monitor SAP systems and their instances
centrally. Unlike SAP MMC, SAP Management
Console is a Java applet, which means that you can
manage remote systems regardless of platforms
with your browser without a local installation.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 33/115
1/22/2020

Area Description

SAP Microsoft Management Console: Windows The SAP Microsoft Management Console (SAP
MMC) provides a common framework for system
management. You can use this to start, stop and
monitor SAP systems centrally with Microsoft
Windows platforms.

SAP NetWeaver Administrator SAP NetWeaver Administrator combines the most

important administration and monitoring tools for
Java systems in a browser-based user interface.
The greatest bene ts that SAP NetWeaver
Administrator provides you are:

You can perform administration,

troubleshooting, and problem analysis
activities of your AS Java without the need
to switch between different tools.

As an administration tool, it allows you to

monitor the performance of your Java
system throughout your landscape, to start
and stop Java processes, instances and
applications, and to check con gurations
and log les.

The user interface adheres to the latest

guidelines for interface design, thus
allowing simple, rapid and task-oriented
navigation. With the use of Web Dynpro,
SAP NetWeaver Administrator runs in a
browser, thus making client-side installation
unnecessary.

System Landscape Directory The System Landscape Directory is the central

information repository for your system landscape.
It contains information about all installable and
installed components in a system landscape.

Database Administration Here you can nd more information about routine

administration of the databases that are supported
Database Administration for SAP HANA
by SAP.

You can nd further information about routine

administration of the SAP HANA database here.

SAP Printing Guide (BC-CCM-PRN) The SAP Printing Guide describes the functions of
the SAP spool system. This system was designed
for use on different platforms. To save users from
having to deal with operating-system-speci c
issues, SAP provides its own spool service and a
spool database.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 34/115
1/22/2020

Area Description

SAP Central Process Scheduling by Redwood SAP CPS provides you with landscape-wide, event-
controlled, and time-controlled job scheduling in
real time in SAP NetWeaver AS ABAP. It makes it
possible for you to automate processes by
managing all background processes that affect one
or more applications in your whole system
landscape.

You can nd the documentation for SAP Central

Process Scheduling on SCN at

http://scn.sap.com/docs/DOC-26195

System Copy If you want to change your operating system, your

database, or both, you must perform a system
copy. We also recommend that you perform a
system copy if you are planning to set up a test
system, demo system, or training system.

Backup and Recovery You need to regularly back up your operating

system and database to restore the SAP system, if
required.

Software Logistics You can use the tools and processes in Software
Logistics to implement new functions, to copy or
migrate existing systems and to support the
creation and distribution of changes in your system
landscape. You can also update your system
landscape in order to ensure smooth operation and
upgrade existing scenarios in your landscape to
new releases.

Statistics Statistics give you an overview of system

performance and system load.

Data Archiving You can use the data archiving functions to archive
any completed business transactions that are no
longer relevant for your daily operations, and so
signi cantly reduce the load on the database.

ILM Database Store (BC-ILM-STO) You can use the ILM Database Store to store
archive les in a database if you are using the
WebDAV interface standard BC-ILM 3.0.

Data Aging (BC-CCM-DAG) Data Aging allows you to move the data within a
database from the hot area to the cold area, to gain
working memory. You move the data by specifying a
data temperature for this data, which is de ned by
the application. This affects the visibility during
data accesses by the application server (AS ABAP).

Application Log (BC-SRV-BAL) The application log is a tool that collects messages,
exceptions, and errors. This information is
organized and displayed in a log.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 35/115
1/22/2020

Area Description

Troubleshooting For information about troubleshooting (problem

analysis scenarios) for particular installable
software units, see the relevant sections of the
documentation.

The SAP Technology Troubleshooting Guide

provides a central starting point for all problems
and can be found at
http://wiki.sdn.sap.com/wiki/display/TechTSG .

Testing SAP NetWeaver provides you with a full

environment for all test phases of ABAP
applications and Web Dynpro Java applications:
From creating and running tests using eCATT
through to test administration using Test
Workbench.

Remote Support Setup If you want to use SAP remote services (for
example, SAP EarlyWatch or Remote Consulting),
or if you would like to permit an SAP support
consultant to work directly in your system to make
a more precise problem diagnosis, then you need to
set up a remote service connection.

Development and Production Infrastructure You use the SAP NetWeaver Development
Infrastructure (NWDI) in your development
lifecycle.

Audit Information System SAP NetWeaver AS for ABAP provides you with a
simple audit function and the Audit Information
System.

SAP Licenses
Use
For managing the SAP licenses, the following tools are available as standard.

SAP License Keys

To use your SAP systems successfully, they must be assigned with lasting SAP license keys, as described in SAP License Keys .

More information is available on the SAP Service Marketplace under the Quick Link licensekeys .

http://service.sap.com/licensekeys

Licensing the AS Java

Documents how you request and import a license key for AS Java.

More information is available under Licensing AS Java and on the SAP Service Marketplace under the Quick Link licensekeys

http://service.sap.com/licensekeys

SAP System Measurement

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 36/115
1/22/2020
With the measurement program (transaction USMM), you can ascertain the number of users and used engines of the SAP software
for each system. You can then pass the measurement results to SAP.

Additional information is available in System Measurement , and in the SAP Service Marketplace under the alias
licenseauditing .

http://service.sap.com/licenseauditing

License Administration Workbench (LAW)

Using the License Administration Workbench, you can consolidate the measurement results of one or more systems, as described
in License Administration Workbench . You can then pass the consolidated measurement results to SAP.

More information is available on the SAP Service Marketplace under the Quick Link licenseauditing .

http://service.sap.com/licenseauditing

BPO Usage Measurement

Documents licensing for customers that sell services to other companies.

SAP NetWeaver Con guration

In this section you can nd notes on technical con guration steps which may be necessary in your SAP NetWeaver system.

Con guration using SAP Solution Manager

In the con guration phase, you use a SAP Solution Manager project and its project structure, to con gure the structure elements
for your business scenarios in the development systems. The SAP Solution Manager contains descriptions of all con guration
tasks, and leads you to automated con guration procedures, where available.

More information: Con guring SAP NetWeaver using SAP Solution Manager

Con guration using ABAP Task Manager for Lifecycle Management Automation
Perform con guration tasks in an automated way by using the ABAP task manager. The ABAP task manager guides you through
extensive con guration processes by means of prede ned task lists and offers the possibility to customize them according to your
needs.

More information: Con guration using ABAP Task Manager for Lifecycle Management Automation

Con guration using the Con guration Wizard (Java)

Use the con guration wizard to perform automated con guration and maintenance tasks for your SAP NetWeaver system. The
con guration wizard enables you to enter data centrally once only, for example, for connectivity, service users, and so on and then
the system distributes the data automatically in the SAP NetWeaver system.

More information: Con guration Wizard

Con guration using the Java Functional Unit Con guration Tool
To perform an automated initial setup of Java functional units, use the functional unit con guration tool.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 37/115
1/22/2020
More information: Java Functional Unit Con guration

Con guring SAP NetWeaver using SAP

Solution Manager
SAP Solution Manager supports you throughout the entire life-cycle of your solutions, from the Business Blueprint to the
con guration to production processing. It provides central access to tools, methods and precon gured contents which you can
use during evaluation, implementation and operational processing of your systems.

Context
You base a Business Blueprint, which contains your project structure, with your company-speci c business scenarios, on your
project that you create in SAP Solution Manager. In the con guration phase, you use your project and its project structure, to
con gure the structure elements for your business scenarios in the development systems.

The SAP Solution Manager contains descriptions of all con guration tasks, and leads you to automated con guration procedures,
where available.

Procedure
1. To be able to use SAP Solution Manager for con guring your systems, you have to import the latest available Support
Package for the SAP Solution Manager Implementation Content (Add-On ST-ICO).

SAP Solution Manager Implementation Content is available on SAP Service Marketplace at http://service.sap.com/swdc
Installations & Upgrades Entry by Application Component SAP Technology Components SAP Solution
Manager <Release> Content ST-ICO .

See also 631042 ( Release strategy for Implementation Content (ST-ICO)).

2. You create a project and a project structure in SAP Solution Manager to access the con guration tasks.

In the con guration phase, you select con guration structures with pre-delivered SAP content for your project.

You can either access the con guration task in the con guration structure or create a printable con guration guide.

For more information, see:

The SAP Solution Manager Library at: http://help.sap.com/solutionmanager SAP Solution Manager <Release of
your SAP Solution Manager system> Application Help SAP Library SAP Solution Manager <Release of your SAP
Solution Manager system> <SP level> Solution Implementation Implementation/Upgrade Work
Center Con guration

http://service.sap.com/alm Solution Documentation and Implementation

http://service.sap.com/solutionmanager Media Library How-To Documents How to Create a Con guration

Guide using SAP Solution Manager

Con guration using ABAP Task Manager for

Lifecycle Management Automation
Perform con guration tasks in an automated way by using the ABAP task manager for lifecycle management automation (ABAP
task manager).

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 38/115
1/22/2020
The ABAP task manager guides you through extensive con guration processes with prede ned task lists and offers the possibility
to customize them according to your needs.

SAP offers prede ned task lists for the following use cases:

ABAP Initial Setup

After you have installed a new SAP system, you have to perform an initial setup and con guration of the system to enable
its usage. For example, you have to install an SAP license, create logon groups, and con gure the Transport Management
System and security settings.

For more information, see the Con guration Guide Automated Initial Setup of Systems Based on SAP NetWeaver ABAP
on SAP Service Marketplace.

ABAP Post-Copy Automation

 Note
Disclaimer:

Prede ned task lists for ABAP post-copy automation are only available if you own an SAP Landscape Management
enterprise edition license. Contact your SAP representative to obtain a license to make this function available.

For more information about using the prede ned task lists with the enterprise edition of SAP Landscape Management, see
the ABAP Post-Copy Automation Installation and Con guration Guides on SAP Service Marketplace at
http://service.sap.com/instlvm .

SAP Fiori Setup

You perform system con guration tasks for Gateway or SAP Fiori Launchpad. For example, you perform basic con guration
steps for Gateway or activate launchpad OData and HTTP services on a Gateway system.

For more information, see SAP Fiori for SAP Business Suite on SAP Help Portal at
http://help.sap.com/ ori_bs2013 Con guration of SAP Fiori Infrastructure Con guration Using Task Lists .

Security Checks

You perform security system smoke tests, such as checking the Secure Sockets Layer (SSL) con guration or the basis
system con guration.

For more information, see the Con guration Guide Automated Initial Setup of Systems Based on SAP NetWeaver ABAP
on SAP Service Marketplace.

Embedded Search

You perform con guration tasks to automate Embedded Search con guration and administration.

For more information, see Automatic Con guration Using Task Manager Task Lists.

For more information about using the ABAP task manager, call one of the following transactions and choose the Online Help
pushbutton:

Transaction Description

STC01 ABAP task manager for lifecycle management automation

STC02 Task list run monitor

Related Information

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 39/115
1/22/2020
ABAP Technical Con guration
Automated Initial Setup of ABAP-Based Systems
Con guration Using Task Lists
Standard Roles and Permissions
Assigning Roles
Executing Task Lists with the ABAP Task Manager for Lifecycle Management Automation
Displaying Task List Documentation
Displaying Log Information for Task List Runs

Standard Roles and Permissions

The table below shows the standard roles and permissions that are used for automated technical con guration activities.

Role Description Permissions

SAP_BC_STC_DISPLAY Role for displaying task lists.

Display task lists (transaction
This role allows task lists and corresponding STC01)
objects (task list runs and task list variants)
used for technical con guration to be Display task list variants
displayed. (transaction STC01)

Display task list runs (transaction

STC02)

SAP_BC_STC_USER Role for a con guration user.

Display task lists (transaction
This role re ects the typical usage of the STC01)
ABAP task manager for lifecycle
management automation. Execute task lists (transaction
STC01)

De ne task list variants (transaction

STC01)

Display task list variants

(transaction STC01)

Display task list runs (transaction

STC02)

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 40/115
1/22/2020

Role Description Permissions

SAP_BC_STC_AUTHOR Role for authoring task lists.

Create task lists (transaction
This role allows task lists used for technical STC01)
con guration to be authored.
Copy task lists (transaction STC01)

Change existing task lists

(transaction STC01)

Delete task lists (transaction

STC01)

Display task lists (transaction

STC01)

Display task list variants

(transaction STC01)

Display task list runs (transaction

STC02)

SAP_BC_STC_REORG Role for cleaning up runtime data.

Display task lists (transaction
This role allows task list runs executed STC01)
during technical con guration to be cleaned
up. Display task list variants
(transaction STC01)

Display task list runs (transaction

STC02)

Delete task list runs (transaction

STC02)

SAP_BC_STC_REMOTE Role for remote access. To perform particular actions, further

authorizations are necessary. See other
This role contains the authorizations which
SAP_BC_STC_* roles.
are necessary to operate on technical
con guration task lists remotely.

SAP_BC_STC_CUST Role for customizing task lists or task list

Display task lists (transaction
variants.
STC01)
This role contains the authorization for
transporting task list variants between Display task list runs (transaction
systems. STC02)

Create task list variants (transaction

STC01

De ne task list variants (transaction

STC01)

Transport task list variants

(transaction STC01)

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 41/115
1/22/2020

Role Description Permissions

SAP_BC_STC_ADMIN Role contains all permissions of the

Display task lists (transaction
following roles:
STC01)
SAP_BC_STC_DISPLAY
Display task list variants
SAP_BC_STC_USER (transaction STC01)

SAP_BC_STC_AUTHOR Display task list runs (transaction

STC02)
SAP_BC_STC_REORG
Execute task lists (transaction
SAP_BC_STC_REMOTE STC01)

SAP_BC_STC_CUST De ne task list variants (transaction

STC01)

Create task lists (transaction

STC01)

Create task list variants (transaction

STC01

Copy task lists (transaction STC01)

Change existing task lists

(transaction STC01)

Delete task lists (transaction

STC01)

Delete task list runs (transaction

STC02)

Related Information
Assigning Roles
Con guration using ABAP Task Manager for Lifecycle Management Automation

Assigning Roles
To execute automated technical con guration activities, you must assign the corresponding SAP_BC_STC roles to the
administrator (dialog user) responsible for ABAP technical con gruation activities and to the technical users that are using
remote access.

Procedure
1. Log on to your ABAP system.

2. Call transaction PFCG.

3. Assign the role SAP_BC_STC_USER to the dialog user and the technical user.

4. Assign the role SAP_BC_STC_REMOTE to the technical user.

Related Information
Standard Roles and Permissions
Con guration using ABAP Task Manager for Lifecycle Management Automation

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 42/115
1/22/2020

Executing Task Lists with the ABAP Task

Manager for Lifecycle Management
Automation
This section describes how to execute task lists with the ABAP task manager for lifecycle management automation.

Prerequisites
You have the required permissions to execute task lists.

For more information, see Standard Roles and Permissions.

Procedure
1. Log on to your ABAP system with logon language English.

2. Call transaction STC01.

3. Enter <Task list name> in the Task List eld.

4. Choose or With Variant.

The ABAP task manager for lifecycle management automation assigns a name to the task list run automatically and
displays a list of the tasks that are de ned for the con guration scenario in the order of their execution. Mandatory and
necessary tasks are preselected for execution.

5. Some tasks require your input. Choose or in the Parameter column of each task, if applicable. If you do not de ne
mandatory parameters, the ABAP task manager for lifecycle management automation uses default settings, if any, or
stops and prompts you for your input. After you have made your settings, save them and go back to the task list.

6. Choose .

 Note
For the following task lists, choose Start/Resume Task List Run in Dialog:

SAP_ABAP2ABAP_SSO_CONFIG

SAP_ABAP2ABAP_TRUST_SERVER_CFG

SAP_SAP2GATEWAY_TRUSTED_CONFIG

7. To get the current status of the task list run, choose .

Next Steps
Displaying Log Information for Task List Runs

Related Information
Con guration using ABAP Task Manager for Lifecycle Management Automation

Displaying Task List Documentation

This section describes how to display the complete documentation of a task list with a detailed task description.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 43/115
1/22/2020

Procedure
1. Log on to your ABAP system with logon language English.

2. Call transaction STC01.

3. Enter the name of the task list.

4. Choose .

5. Choose Goto Documentation Display with Task Docu .

Results
The system displays the documentation of the task list with a detailed task description.

Related Information
Con guration using ABAP Task Manager for Lifecycle Management Automation

Displaying Log Information for Task List Runs

You view detailed log information about a task list run.

Prerequisites
You have executed a task list or task list variant.

Procedure
1. Log on to your ABAP system with logon language English.

2. Call transaction STC02.

3. Search for the task list run you want to view.

4. Choose Task List Run Display Log .

Results
The system displays the following:

Task list run header information

Task list information

Task overview

Task details

Next Steps
To download a ZIP le with the log information, choose .

Related Information
Con guration using ABAP Task Manager for Lifecycle Management Automation

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 44/115
1/22/2020

Con guration Wizard

Use
Once you have installed an SAP NetWeaver system and applied the latest kernel and Support Packages, the con guration wizard
supports you in performing con guration tasks in an automated way and thus simpli es the setup of your systems. It guides you
through the con guration process and offers a uniform user interface for all steps. It enables you to execute con guration tasks
across multiple components.

 Caution
You can run the con guration wizard only once and only directly after installing and patching your SAP system.

You cannot use the con guration wizard after:

Upgrade

Add-In installation

Enabling additional usage types

System copy

In these cases, you need to manually perform the corresponding con guration steps.

This does not apply to the con guration task for BI Java. You can run it several times and after all use cases.

For more information about con guration templates, manual con guration steps, and connectivity con guration templates,
see the con guration structure of your implementation project in SAP Solution Manager.

Prerequisites
Before you start the con guration wizard, you must have applied the latest kernel and all ABAP and Java Support Packages and
patches to your system. The required sequence is as follows:

1. Install your system.

2. Install the latest Support Packages and patches (if available).

3. Run the con guration wizard.

For more information, see Applying the Latest Kernel and Support Packages in the installation guide of your product at
http://service.sap.com/instguides .

 Note
You can nd the latest LMTOOLS patch at http://service.sap.com/swdc Support Packages and Patches Search for Support
Packages and Patches . Search for LMTOOLS*P. Download and save the SCA le. Apply the patch using the JSPM.

 Example

1. You install an SAP NetWeaver SR3 (SPS14) system.

2. To update the system to SPS15, you search for LMTOOLS15P to nd the latest available patch for this stack.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 45/115
1/22/2020
3. You update the system.

4. You run the con guration wizard.

Integration
You make the technical settings with the con guration wizard after installing and patching an SAP NetWeaver system.

The con guration wizard is part of the SAP NetWeaver Administrator. The SAP NetWeaver installation guide contains
detailed information about which con guration tasks to choose.

You use the con guration wizard for the technical con guration. The SAP NetWeaver installation guide contains detailed
information about the con guration tasks.

Features
The con guration wizard makes the technical settings (technical con guration) in an automated way. It allows you to enter the
same data centrally, once only, for example, connectivity, service users, and so on. The system distributes this data automatically
in the SAP NetWeaver system.

Additional Tool Features

Different Con guration Views

All Con guration Tasks

This view lists all con guration tasks available for your SAP NetWeaver system.

Initial Con guration

This view includes the con guration steps for all usage types you installed.

Interrupted Con guration Tasks

If you canceled a con guration and want to resume it later, choose the con guration task and then Resume .

Running Con guration Tasks

To reconnect to a session that is running but which was lost due to a browser crash or by accidentally closing the browser,
choose the con guration task that is currently running and then Take Over Session or Cancel Process .

History of Executed Con guration Tasks

This view lists all con guration tasks that have been executed previously.

Status Messages

Status Message De nition

Initial Con guration task not executed

Currently executing Con guration task is currently executed

Finished with skipped steps Con guration task was executed and nished. One or several steps were skipped.
Script may be restarted or followed up.

Canceled Con guration task was canceled by the user.

Finished successfully Con guration task was nished without any errors or warnings.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 46/115
1/22/2020
Error Handling

You can view error messages that occurred during the automated con guration process by choosing Protocol . Clicking on a step
that failed to be executed opens a more detailed view, listing the status of the con guration step, links to further documentation,
and further technical information.

If errors occur during the execution of the con guration steps, you can perform them manually. For more information, see the
con guration structure of your implementation project in SAP Solution Manager.

Select Con guration Steps To Be Skipped

You can select single con guration steps that you do not want to be carried out automatically. To do so, at the bottom of the page,
choose Details . You can now select the steps to be skipped.

Activities
1. Call the SAP NetWeaver Administrator in a browser using the path http://<host>:<httpport>/nwa , and log on to
the SAP NetWeaver Administrator with the appropriate administrator user.

2. In the SAP NetWeaver Administrator, choose Deploy and Change Con guration Wizard .

3. Select the task in the list, and choose Start .

4. Follow the screens.

The system makes the necessary settings.

The system reports any con guration errors. Error message long texts are written to the protocol.

More Information
For more information about the con guration wizard and the con guration documentation, see the con guration structure of your
implementation project in SAP Solution Manager.

See Also

SAP Note 923359 Collective Note: Con guration Wizard - Template Installer

SAP Note 1178800 Collective Note: Business Suite Connectivity

Java Functional Unit Con guration

Use
Use the functional unit con guration tool to perform the initial setup of Java functional units.

 Caution
Do not use the automation tools after:

Upgrade

Update

System copy

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 47/115
1/22/2020
If you need to change con guration of already enabled functional units, carry out the con guration steps manually.

Features
The functional unit con guration tool makes the technical settings (technical con guration) for Java functional units in an
automated way. While selecting a functional unit for con guration, the tool accounts for dependencies between functional units
and selects the additionally required functional units automatically. The tool allows you to enter the data required for all selected
con guration tasks centrally and only once. The system distributes this data automatically in the SAP NetWeaver system.

Additional Tool Features

Different Functional Unit Views

Show installed Functional Units only

This view is displayed when you rst enter the Functional Units screen. It lists the functional units for which implementing
software components are currently installed.

Show all Functional Units

This view lists all functional units available for your SAP NetWeaver system.

Con guration Tasks

The Con guration Task column indicates if an automated con guration task is available for a functional unit.

Status Messages

Status Message De nition

Running Con guration task is currently executed.

Enabled Con guration task was nished and the functional unit is ready to
use.

Disabled Con guration task is not executed.

Execution of Con guration Tasks

Enable Automatically

This starts an automated con guration process that combines the technical con guration of all functional units selected.

Enable Manually

This marks the selected functional units as enabled, that is, con gured and ready to use. Only use Enable Manually if you
have already performed the required con guration steps manually.

Disable

This marks the selected functional units as not enabled, that is, not con gured, without resetting the con guration. Use
Disable before you rerun or resume a con guration task with status Enabled or Running .

Error Message Handling

For detailed information about errors that occurred during the execution of con guration tasks, select the relevant functional unit,
and on the General tab page, choose Con guration Log . This log collectively displays information about all selected functional
units.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 48/115
1/22/2020

Activities
1. Call the functional unit con guration tool in a browser using the path http://<host>:<httpport>/sld/fun , and
log on with the appropriate administrator user.

2. From the list of installed functional units, select those you want to con gure. If the con guration of a functional unit
requires additional functional units, the tool selects them automatically. You can select multiple functional units by
pressing Ctrl or Shift .

3. To start the con guration, proceed in one of the following ways:

Automated con guration

a. If at least one automated con guration task is available in your selection of functional units, choose Enable
Automatically .

b. Follow the con guration wizard screens.

The tool makes the necessary settings and sets the con guration task to enabled after it has nished
successfully.

Manual con guration

a. If no automated con guration task is available, perform the required con guration steps manually. For more
information about manual con guration of Java functional units, see the con guration documentation in
your implementation project in SAP Solution Manager.

b. Choose Enable Manually .

More Information
For more information about con guration documentation in SAP Solution Manager, see the SAP Library at
http://help.sap.com SAP Solution Manager SAP Enhancement Package 1 for SAP Solution Manager 7.0
English Implementing and Upgrading SAP Solutions Projects Project Administration Create/Change Project .

Customizing
Use
With Customizing settings enable you to adapt the non-company speci c and industry-speci c functions shipped to the speci c
business requirements of your enterprise.

Customizing supports you in the following situations:

Implementing the SAP System

Enhancing the SAP System

in release and system upgrades

Integration
Customizing controls the behavior of SAP applications. You only work with many SAP applications once you have made the
necessary settings in Customizing, for example, setting the currencies and purchasing groups in Customizing that are used in your
company.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 49/115
1/22/2020
To be able to transport the Customizing settings to other systems, for example, your test system, you need the transport system.

Features
Tools for System Settings and their documentation ( Logging Customizing Changes )

Recommendations for system settings

Customizing projects as a means for controlling the management, editing and analysis processes of the implementation
and upgrade projects

Support for transferring the system settings from the test system into the production system

Support when transporting system settings between different systems using Business Con guration Sets , for example for
a business rollout.

Comparison of Customizing Between Different Systems

Tools for system upgrades and release upgrades

Constraints
Customizing does not help you to modify the standard SAP functions.

Starting and Stopping SAP Systems Based

on SAP NetWeaver
When you start an SAP system based on SAP NetWeaver, you start the system database, the application servers, and the
respective processes of which the system consists.

 Note
In general, the database starts rst, and then the instance. When you start the central instance, the database starts
automatically. However, the database does not stop when you stop the primary application server instance.

The following sections describe how you start and stop SAP systems and instances based on SAP NetWeaver.

Related Information
Starting Systems and Instances with the SAP Management Console
Stopping Systems and Instances with the SAP Management Console
Starting and Stopping SAP Systems and Instances with the SAP MMC (Windows)
Starting and Stopping SAP Systems Using SAPControl
Starting and Stopping SAP Systems and Instances on IBM i

Starting Systems and Instances with the

SAP Management Console
You can use the SAP Management Console (SAP MC) to start and restart systems and instances.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 50/115
1/22/2020

Prerequisites
UNIX only: Make sure that the host names de ned in the DNS server match the names of the SAP system instance hosts.
In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP system instance hosts
are in upper case, but the same host names are de ned in the DNS server in lower case, starting and stopping the system
does not work.

If you want to start or restart remote systems or instances, make sure that you have registered them in the SAP
Management Console (SAP MC).

You do not need to register SAP systems or instances installed on the local host, because the SAP MC displays them
automatically.

You have started the SAP MC.

Context
As of SAP MC version 7200, 313, 20, 42101 you can also start databases of SAP systems on all operating system platforms using
the SAP MC.

Procedure
1. In the navigation pane of the SAP MC, open the tree structure and navigate to the system node that you want to start.

2. Select the system node and then choose Start from the context menu.

The Start SAP System(s) dialog box displays.

3. In the Start SAP System(s) dialog box, select the SAP system instances to be started and choose OK.

4. The SAP MC prompts you for user credentials that are required to start the SAP system or instances.

 Note
If the database of the SAP system is not yet running, you might be also prompted for additional credentials of a user
that is authorized to start the database.

Results
The SAP MC starts the requested SAP system or instances.

Next Steps
The SAP MC automatically displays the instances installed on the local host. If you need to monitor and administer remote
systems or instances, you have to register them in the SAP MC. For more information, see Registering Systems and
Instances.

The nodes for instances are displayed in different colors depending on their state. For more information, see Layout of the
SAP Management Console.

Related Information
Starting the SAP Management Console
Registering Systems and Instances in the SAP Management Console
Layout of the SAP Management Console
SAP Management Console

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 51/115
1/22/2020

Stopping Systems and Instances with the

SAP Management Console
You can use the SAP Management Console (SAP MC) to stop systems and instances.

Prerequisites
UNIX only: Make sure that the host names de ned in the DNS server match the names of the SAP system instance hosts.
In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP system instance hosts
are in upper case, but the same host names are de ned in the DNS server in lower case, starting and stopping the system
does not work.

If you want to stop remote systems or instances, make sure that you have registered them in the SAP MC.

You do not need to register SAP systems or instances installed on the local host, because the SAP MC displays them
automatically.

You have started the SAP MC.

Procedure
1. In the navigation pane of the SAP MC, open the tree structure and navigate to the system node that you want to stop.

2. In the navigation pane of the SAP MC, select the system you want to stop and choose Stop from the context menu.

3. In the Stop SAP System(s) dialog box, select the SAP system instances to be stopped and choose OK.

 Note
If you also want to stop the database, mark the Include Database checkbox.

4. The SAP MC prompts you for user credentials that are required to stop the SAP system or instances.

 Note
You might be also prompted for additional credentials of a user that is authorized to stop the database.

Results
The SAP MC stops the requested SAP system or instances.

Related Information
Starting Systems and Instances with the SAP Management Console
SAP Management Console

Starting and Stopping SAP Systems and

Instances with the SAP MMC (Windows)
Prerequisites
The user who wants to start and stop the SAP system with the SAP MMC, must be a member of the local administrators group.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 52/115
1/22/2020

Context
You can start and stop an SAP system or installed SAP instances locally on the host that you are logged on to with the SAP
Microsoft Management Console (MMC). If the SAP MMC is con gured for central system administration, you can start or stop the
entire system from a single host.

Procedure
1. Start the SAP MMC on the SAP system host.

2. Right-click the SAP system node and choose Start or Stop.

All instances listed under the system node start or stop in the correct order.

 Note
The database is not stopped automatically when you stop your SAP system. To stop the database, see your database-
speci c documentation.

3. If the SAP system is installed on multiple hosts (distributed or high-availability system), you have the following options to
start or stop your system:

You start or stop the SAP instances using the SAP MMC on each host.

You add the remote instances to the SAP MMC con guration to start or stop all instances from a single SAP MMC.
For more information, see the SAP MMC documentation.

Starting and Stopping SAP Systems Using

SAPControl
You can use SAPControl to start or stop an SAP system from the command line.

Prerequisites
You are logged on to the SAP system host as user <sapsid>adm.

Context

 Note
The startsap and stopsap commands are deprecated. SAP recommends that you do not use them any longer. For more
information, see SAP Notes 1763593 and 809477 .

This section only lists the basic commands how to start or stop an SAP system. You can nd a detailed list of all SAPControl
options and features in the command line help, which you can call as follows:

UNIX: /usr/sap/hostctrl/exe/sapcontrol --help

Windows: %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe --
help

Procedure
Starting an SAP System or Instance
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 53/115
1/22/2020
Starting an SAP System:

You can start an SAP system by executing the following commands from the command line
(<Instance_Number> can be the number of any instance of the SAP system):

UNIX /usr/sap/hostctrl/exe/sapcontrol -nr

<instance_number> -function StartSystem

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe
-nr <instance_number> -function StartSystem

Starting an SAP System Instance

You can start an SAP system instance by executing the following commands from the command line:

UNIX /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function

Start

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe -nr <instance_number>

-function Start

For remote instances, the syntax is slightly different, because you also have to apply the -host and -user
parameters:

UNIX /usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote

host> –user <sapsid>adm <password> -function Start

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe –nr <instance_number>

-host <remote host> –user <sapsid>adm <password> -function Start

Stopping an SAP System or Instance

Stopping an SAP System

You can stop an SAP system by executing the following commands from the command line
(<Instance_Number> can be the number of any instance of the SAP system):

UNIX /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function

StopSystem

Windows %ProgramFiles%\Program Files\SAP\hostctrl\exe\sapcontrol.exe -nr

<instance_number> -function StopSystem

Stopping an SAP System Instance

You can stop an SAP system instance by executing the following commands from the command line:

UNIX /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function Stop

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe -nr <instance_number>

-function Stop

For remote instances, the syntax is slightly different, because you also have to apply the -host and -user
parameters:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 54/115
1/22/2020
UNIX /usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote
host> –user <sapsid>adm <password> -function Stop

Windows %ProgramFiles%:\Program Files\SAP\hostctrl\exe\sapcontrol.exe –nr

<instance_number> -host <remote host> –user <sapsid>adm <password> -
function Stop

 Note
The database is not stopped by these commands. You have to stop the database using database-speci c tools
or commands.

Checking System Instance and Processes

With the following command you get a list of system instances, their status, and the ports used by them
(<Instance_Number> can be the number of any instance of the SAP system):

UNIX /usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote

host> –user <sapsid>adm <password> -function GetSystemInstanceList

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe –nr <instance_number>

-host <remote host> –user <sapsid>adm <password> -function
GetSystemInstanceList

With the following command you get a list of instance processes and their status:

UNIX /usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote

host> –user <sapsid>adm <password> -function GetProcessList

Windows %ProgramFiles%\SAP\hostctrl\exe\sapcontrol.exe –nr <instance_number>

-host <remote host> –user <sapsid>adm <password> -function
GetProcessList

Troubleshooting

If you get an error like "FAIL: NIECONN_REFUSED", execute sapcontrol -nr <Instance_Number> -
function StartService <SAPSID> to ensure that sapstartsrv is running. Then execute again the start or stop
command.

Related Information
Starting Systems and Instances with the SAP Management Console
Stopping Systems and Instances with the SAP Management Console

Starting and Stopping SAP Systems and

Instances on IBM i
Procedure
To start and stop an SAP system or instance on IBM i, proceed as follows:

Starting

1. Log on to the host of your central system as < SID > ADM.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 55/115
1/22/2020
2. To start an SAP system or instance, enter the command STARTSAP INSTANCE(*ALL).

The instances and all other processes for your system are started on this host.

Stopping

1. Log on to the host of your central system as < SID > ADM.

2. To stop an SAP system or instance, enter the command STOPSAP INSTANCE(*ALL).

 Note
To start or stop SAP instances, you can also log on as QSECOFR or another user with sufficient authority to operate on
the SAP system. To set up the library list and environment variables, enter CALL PGM(R3< SID >400/R3INLPGM )
before using the commands STARTSAP or STOPSAP.

Connecting a Technical System to SAP

Solution Manager
Use
SAP Solution Manager gives you central access to tools, methods, and precon gured content that you can use to evaluate and
implement your solutions. When your implementation is running, you can use SAP Solution Manager to manage, monitor, and
update systems and business processes in your solution landscape, and also to set up and operate your own solution support.

Integration
A technical system is connected to SAP Solution Manager by the following steps:

1. On the technical systems of your landscape, data suppliers are implemented, for example, with transaction RZ70 for
Application Server ABAP and with Visual Administrator for Application Server Java.

For more information, see: Register Technical Systems Automatically by Data Suppliers at at
http://help.sap.com/solutionmanager71 under Application Help select SP and language SAP Solution Manager
Operations Managing System Landscape Information Manage Technical System Information .

2. The data suppliers send information about the hardware and installed software to a central System Landscape Directory
(SLD). Updates are sent to the SLD as well.

For more information, see the Planning Guide - System Landscape Directory in the SAP Community Network at
http://scn.sap.com/docs/DOC-8042 .

3. From the SLD, this information is regularly synchronized with SAP Solution Manager where it is managed in the Landscape
Management Database (LMDB).

For more information, see: Connect LMDB to System Landscape Directory (SLD) at
http://help.sap.com/solutionmanager71 under Application Help select SP and language SAP Solution Manager
Operations Managing System Landscape Information .

4. In the LMDB, you complete the information from the SLD, manually.

For more information, see Manage Technical System Information and Manage Product System Information at
http://help.sap.com/solutionmanager71 under Application Help select SP and language SAP Solution Manager
Operations Managing System Landscape Information .

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 56/115
1/22/2020

More Information
For more information, see the following pages in the SAP Community Network:

System Landscape Directory (SLD) at http://scn.sap.com/docs/DOC-8042

Documentation for System Landscape Management - LMDB at http://scn.sap.com/docs/DOC-29495

Solution Monitoring
Use
The monitoring features in IT landscapes monitor IT components and processes that run across multiple components. The
monitoring results are displayed in a central system. Any problems are displayed as alerts. You can use the relevant analysis
methods to go to an appropriate transaction or tool to evaluate the problem.

The following monitoring types are available:

System Monitoring with CCMS

This system monitor enables you to check the status and performance of the various system components. For example,
you can monitor the availability of a system.

Process Monitoring with PMI (Process Monitoring Infrastructure)

The PMI monitors the whole of a process that involves multiple components. Here, the individual steps of the process are
important, not the status of the components. You can see the process ow of the steps across multiple systems, even for
asynchronous processes with several transactions. In this way, you can detect any errors and drops in performance at an
early stage.

System Copy
Use
In different situations during the life-cycle of your SAP solution, it may be appropriate for you to perform a system copy or a
migration.

If you want to change your operating system, your database, or both, you must perform a system copy. We also recommend that
you perform a system copy if you are planning to set up a test system, demo system, or training system.

As of SAP NetWeaver 7.0, you can copy a mixed ABAP Stack and Java Stack system in a single operation, not just standalone
ABAP or Java systems.

 Note
When you perform a system copy, all usage types in the source system are copied to the target system. This means that you
cannot leave out any usage types in the source system or copy selectively to a target system.

De nition of Terms

You perform a homogeneous system copy if your target system is on the same operating system and database system as
your source system. The database contents are copied from the source system to the target system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 57/115
1/22/2020
You perform a heterogeneous system copy if you want to change the operating system or database system. Migration is
another term for a heterogeneous system copy.

More Information
For more information about the system copy, see SAP Service Marketplace at http://service.sap.com/systemcopy .

For a detailed description of the system copy procedure, see the current system copy guide on SAP Service Marketplace at
http://service.sap.com/instguides SAP NetWeaver <your release> Installation .

Backup and Recovery

You need to regularly back up your operating system and database to restore the SAP system, if required.

To use an appropriate back up and restore method is one of the most important tasks of the system and database administrator.
However, there is no general recommendation for such a method, since it depends on several factors, such as:

Disaster recovery concept

Maximum permissable downtime during restore

Amount of data loss that is tolerable

Available budget

Operating System-speci c Backup and Recovery Procedures

For information on operating system-speci c backup and recovery procedures, see one of the following sections:

Backing Up and Restoring your SAP System on Windows

Backing Up and Restoring your SAP System on UNIX

Backing Up and Restoring your SAP System on IBM i

Database-speci c Backup and Recovery Procedures

For information on database-speci c backup and recovery procedures, see the database administration guides available in the
Database Administration section:

Database Administration for SAP HANA

Database Administration for SAP MaxDB

Database Administration for IBM DB2 for i

Database Administration for IBM DB2 for Linux, UNIX, and Windows

Database Administration for DB2 for z/OS

Database Administration for Microsoft SQL Server

Database Administration for Oracle

Database Administration for SAP Sybase ASE

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 58/115
1/22/2020

Backing Up and Restoring Your SAP System

on Windows
Prerequisites
You are logged on as user <sapsid>adm.

Context
This procedure describes how to back up and restore an SAP system on Windows Server 2008 (R2) and higher.

On Windows, a lot of information created during the SAP system installation and operation is stored in databases like the Windows
system registry, the user registry, or the Active Directory, when installing in a Windows domain.

Therefore, we recommend that you always back up and restore the complete computer, including the operating system to avoid
data or system inconsistency. In addition, the overhead of a full backup of the computer (backup of operating system disk, non-
operating system disks, database data les) compared to a database online backup is negligible. During backup, the SAP system
can be online.

To be able to back up and restore your SAP system properly in case of emergency, we strongly recommend that you test the
backup and restore procedure on a regular basis, to avoid system downtime and data loss.

Procedure
Backing Up your SAP system

1. Back up the operating system disk.

2. Back up non-operating system disks (excluding disks that contain database data les only).

3. Back up the database data les.

For more information, see your database-speci c documentation.

The Microsoft tool available for creating a backup on Windows Server 2008 (R2) and higher, is called Windows Server
Backup (WSB), which replaces the former backup tool NTBackup of Windows Server 2003. You have to activate the WSB
feature before you can use it. With WSB you can no longer back up single les or directories, but only complete disk
volumes. There is an NTBackup version available, which is running on Windows Server 2008 (R2 and higher, and which you
can download from the Microsoft web page. This version, however, only allows you to restore les that were backed up on
Windows Server 2003. You cannot use this version to create backup savesets.

After you have activated the WSB feature, you can invoke it with Start Administrative Tools Windows Server Backup .

For more information about the Windows Server 2008 (R2) and higher backup and recovery procedures, see the F1 help or
the Help and Support documentation, which you nd in the Windows Start menu under Start Help and Support / Server
Fundamentals / Backup and Recovery .

Restoring Your SAP system

Since the SAP system is very complex, we strongly recommend that you restore complete system backups only.

Restoring partial backups might lead to con guration inconsistencies and is only possible on the computer where the
backup was created, and which has the same (unique) Computer Security Identi er (SID), which is generated during the
installation of the Windows operating system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 59/115
1/22/2020
Restoring the directory structure \usr\sap including the database data les on another computer leads to a complete
loss of the system- and computer-speci c environment on the target computer. You cannot start the system or the
database on this computer for the following reasons:

Con guration information is also stored in the Windows system registry and this cannot be restored on a different
computer.

Security settings on Directory and Files use unique SIDs, which cannot be translated on a different computer.

If, for any reason, you must restore a backup on a different computer, you have to perform a homogeneous system copy
with the backup/restore procedure. For more information, see the System Copy Guide for your SAP product.

To restore your SAP system, proceed as follows:

1. Restore the operating system disk.

For more information, see the Windows Help and Support documentation, which you can nd in the Windows Start
menu under Start Help and Support / Server Fundamentals / Backup and Recovery / Windows Recovery
Environment Overview .

As of Windows Server 2008 R2, you can also use PowerShell commands for the backup. For more information, start
Windows PowerShell and enter the following command: get-help Start-WBBackup -online

2. If not already done in the previous step, restore the non-operating system disks with WSB.

3. Restore the database.

For more information, see your database-speci c documentation.

Backing Up and Restoring your SAP System

on UNIX
This procedure describes how to perform a full offline backup of an SAP system and how to use the backup data for a restore.

Prerequisites
The SAP system and database are stopped. For more information, see Starting and Stopping SAP Systems Based on SAP
NetWeaver.

Procedure
Backing Up Your SAP System

1. Perform a full database backup.

2. Back up the home directories of the following operating system users:

<sapsid> adm

Database-speci c operating system user(s)

3. Back up the following le systems of your SAP system:

/usr/sap/ <SAPSID>

/usr/sap/trans

/ <sapmnt>/ <SAPSID>

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 60/115
1/22/2020

 Note
For more information about the SAP system directories available under these le systems, see SAP System
Directories on UNIX.

4. Proceed as follows to perform the backup:

 Note
The UNIX commands used in this procedure work on all hardware platforms. For more information about
operating system-speci c backup tools, see your operating system documentation.

a. Log on as user root.

b. Manually create a compressed tar archive that contains all installed les:

Saving to tape:

tar -cf - <file_system | compress -c> <tape_device>

Saving to the le system:

tar -cf - <file_system | compress -c> ARCHIVENAME.tar.Z

 Note
On Linux, you can also execute the following command to manually create a compressed GNU tar
archive that contains all installed les and save it to the le system:

tar -czf <ARCHIVENAME>.tgz <file_system>

5. Back up the operating system using operating system tools.

This saves the structure of the system and all con guration les, such as le system size, con guration of the
logical volume manager, and database con guration data.

Restoring the Backup

If required, you can restore the data that you previously backed up.

 Caution
Check for modi cations in the existing parameter les before you overwrite them when restoring the backup.

1. Log on as user root.

2. Go to the location in your le system where you want to restore the backup image.

3. Proceed as follows to restore the backup:

 Note
The UNIX commands used in this procedure work on all hardware platforms. For more information about
operating system-speci c backup tools, see your operating system documentation.

Execute the following command to restore the data from tape:

cat <tape_device>| compress -cd | tar -xf -

Execute the following command to restore the data from the le system:

cat ARCHIVENAME.tar.Z | compress -cd | tar -xf -

 Note

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 61/115
1/22/2020
If you want to restore the data from a GNU tar archive on Linux, you have to execute the following command:

tar -xzf <ARCHIVENAME>.tgz

4. Restore your database backup.

For more information, see the database backup documentation for your database in the Database Administration
section of this documentation.

Related Information
SAP System Directories on UNIX

SAP System Directories on UNIX

Here you can nd information about the directory structure of an SAP system.

SAP System Directory Types

An SAP system contains the following types of directories:

Physically shared directories, which reside on the global host and are shared by Network File System (NFS)

Logically shared directories, which reside on the local host with symbolic links to the global host

Local directories, which reside on the local host

The gures below assume that you have set up one le system for the SAP system mount directory /<sapmnt> and one le
system for the /usr/sap directory.

Standard System Directories for an SAP ABAP System

An ABAP system can be Unicode or non-Unicode.

SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.0:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 62/115
1/22/2020

Figure 3: SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.0. For more information, see section SAP System
Directories in Detail

SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.1 and higher:

 Note
SAP ABAP systems based on SAP NetWeaver 7.5 and higher are only Unicode.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 63/115
1/22/2020

Figure 4: SAP ABAP System (Unicode or Non-Unicode) based on SAP NetWeaver 7.1 and higher

Standard System Directories for an SAP Dual-Stack (ABAP+Java) System

A dual-stack system can be Unicode or non-Unicode. That is, the ABAP system can be Unicode or non-Unicode, whereas the Java
system can only be Unicode.

Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.0:

SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP Unicode) based on SAP NetWeaver 7.0:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 64/115
1/22/2020

Figure 5: Standard SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP Unicode) based on SAP NetWeaver 7.0

SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP non-Unicode) based on SAP NetWeaver 7.0:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 65/115
1/22/2020

Figure 6: Standard SAP Directories for a Dual-Stack (ABAP+Java) System (ABAP non-Unicode) based on SAP NetWeaver 7.0

Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4:

 Note
In SAP systems based on SAP NetWeaver 7.5 or higher, dual stack (ABAP+Java) is no longer supported.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 66/115
1/22/2020

Figure 7: Standard SAP Directories for a Dual-Stack (ABAP+Java) System based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4

Standard System Directories for an SAP Java System (Unicode)

A Java system can only be a Unicode system.

Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.0:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 67/115
1/22/2020

Figure 8: Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.0

Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.1 and higher

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 68/115
1/22/2020

Figure 9: Standard SAP Directories for a Java System (Unicode) based on SAP NetWeaver 7.1 and higher

SAP System Directories in Detail

System Directories of an SAP System based on SAP NetWeaver 7.0:

Directory Description

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 69/115
1/22/2020

Directory Description

/<sapmnt>/<SAPSID> Software and data for one SAP system

This directory and its subdirectories need to be physically shared using Network File System
(NFS) and mounted for all hosts belonging to the same SAP system. It contains the following
subdirectories:

1. exe

This directory contains executable kernel programs. In an SAP system with

distributed instances, this directory must be shared for all hosts with the same
operating system.

 Note
dual-stack (ABAP (Non-Unicode) + Java) system only: exe contains a folder uc
with a platform-speci c subfolder:
<sapmnt>/<SAPSID>/exe/uc/<platform>.

2. global

This directory contains log les. In an SAP system with distributed instances, this
directory must be shared for all hosts with the same operating system.

3. profile

This directory contains the start and operations pro les of all instances. In an SAP
system with distributed instances, this directory must be shared for all hosts with
the same operating system.

/usr/sap/<SAPSID> Instance-speci c data, symbolic links to the data for one system

This directory contains les for the operation of a local instance.

Whenever a local instance is started, the sapcpe program checks the executables against
those in the logically shared directories and, if necessary, replicates them to the local
instance.

There is a subdirectory for each instance. Each instance directory has the name of
the related instance.

The instance name (instance ID) of the ABAP central instance is

DVEBMGS<Instance_Number>, and the instance name of an ABAP dialog
instance is D<Instance_Number>. In a high-availability system, there is
also an ABAP Central Services instance called ASCS<Instance_Number>.

 Example
The le system structure might look as follows: On a central instance
with SAP system ID C11 and instance name DVEBMGS00, the ABAP dialog
instance has the instance name D01.

The instance name (instance ID) of the dual-stack (ABAP+Java) central

instance is DVEBMGS<Instance_Number>, the instance name of the Java
central services instance is SCS<Instance_Number>, and the instance
name of a dual-stack (ABAP+Java) dialog instance is
D<Instance_Number>. In a high-availability system, there is also an ABAP
Central Services instance called ASCS<Instance_Number>

 Example
The le system structure might look as follows:
On a central instance with SAP system ID C11 and instance name
DVEBMGS00, the J2EE Engine is installed in

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 70/115
1/22/2020

Directory Description

/usr/sap/C11/DVEBMGS00/j2ee, and the corresponding Software

Delivery Manager (SDM) is installed in /usr/sap/C11/JC00/SDM

On a dialog instance with instance name D01, the J2EE Engine is installed
in /usr/sap/C11/D01/j2ee. No SDM is installed.

The instance name (instance ID) of the Java central instance is

JC<Instance_Number>, the instance name of a Java dialog instance is
J<Instance_Number>, and the instance name of the Java central services
instance is SCS<Instance_Number>. The instance name (instance ID) of
the central instance is JC<Instance_Number>, the instance name of a
Java dialog instance is J<Instance_Number>, and the instance name of
the Java central services instance is SCS<Instance_Number>.

 Example
The le system structure might look as follows:

On a central instance with SAP system ID C11 and instance name JC00,
the J2EE Engine is installed in /usr/sap/C11/JC00/j2ee, and the
corresponding SDM is installed in /usr/sap/C11/JC00/SDM.

On a dialog instance with instance name J01, the J2EE Engine is installed
in /usr/sap/C11/J01/j2ee. No SDM is installed.

The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate

directories in /<sapmnt>/<SAPSID>/ for storing data used by several instances.
SYS is logically shared and available on each host of the SAP system. Its
subdirectories contain symbolic links to the corresponding subdirectories of
/<sapmnt>/<SAPSID> on the SAP global host, as shown in the gures above.

For more information about sapcpe, see The sapcpe Program documentation. Executables
located in /usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe
subdirectory of the instance directories.

/usr/sap/trans Global transport directory for all SAP systems

The global transport directory is used by the Change and Transport System (CTS). The CTS
helps you to organize development projects in the ABAP Workbench and in Customizing, and
then transport the changes between the SAP systems in your system landscape. For more
information, see the Change and Transport System documentation.

System Directories of an SAP System based on SAP NetWeaver 7.1 and higher:

Directory Description

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 71/115
1/22/2020

Directory Description

/<sapmnt>/<SAPSID> Software and data for one SAP system

This directory and its subdirectories need to be physically shared using Network File System
(NFS) and mounted for all hosts belonging to the same SAP system. It contains the following
subdirectories:

exe

This directory contains executable kernel programs. In an SAP system with distributed
instances, this directory must be shared for all hosts with the same operating system.

 Note
Dual-stack (ABAP+Java) system only (based on SAP NetWeaver 7.1 to SAP NetWeaver
7.4): exe contains a folder uc and a folder nuc, each with a platform-speci c sub folder:
/<sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems.
Executable kernel programs are replicated from this directory to the exe directories of
each Unicode system instance. /<sapmnt>/<SAPSID>/exe/nuc/<platform> is
used in non-Unicode systems (see below). Executable kernel programs are replicated
from this directory to the exe directories of each non-Unicode system instance (see
below).

global

This directory contains log les. In an SAP system with distributed instances, this
directory must be shared for all hosts with the same operating system.

profile

This directory contains the start and operations pro les of all instances. In an SAP system
with distributed instances, this directory must be shared for all hosts with the same
operating system.

/usr/sap/<SAPSID> Instance-speci c data, symbolic links to the data for one system

This directory contains les for the operation of a local instance.

There is a subdirectory for each instance. Each instance directory has the name of the
related instance:

The instance names (instance IDs) of an ABAP system are as follows:

Primary application server instance: DVEBMGS<Instance_Number>

 Note
As of SAP NetWeaver 7.5 the instance name is always
D<Instance_Number> for all application server instances. This
means that in SAP systems based on SAP NetWeaver 7.5 and higher
the instance name for the primary application server instance is
D<Instance_Number> like the instance name of the
additional application server instances.

Additional application server instance: D<Instance_Number>

ABAP Central Services instance (ASCS instance):

ASCS<Instance_Number>

Enqueue replication server instance (ERS instance):

ERS<Instance_Number>

The enqueue replication server instance is only mandatory in a high-

availability system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 72/115
1/22/2020

Directory Description

 Example
For an SAP ABAP system based on SAP NetWeaver 7.1 to SAP NetWeaver 7.4
with SAP system ID C11, the instances might look as follows:

Primary application server instance: DVEBMGS00

Additional application server instance: D01

ABAP Central Services instance (ASCS instance): ASCS02

Enqueue replication server instance (ERS instance): ERS03

 Example
For an SAP ABAP system based onSAP NetWeaver 7.5 or higher with SAP
system ID C11, the instances might look as follows:

Primary application server instance: D00

Additional application server instance: D01

ABAP Central Services instance (ASCS instance): ASCS02

Enqueue replication server instance (ERS instance): ERS03

The instance names (instance IDs) of a dual stack (ABAP+Java) system based on
SAP NetWeaver 7.1 to SAP NetWeaver 7.4 are as follows:

 Note
In SAP systems based on to SAP NetWeaver 7.5 or higher, dual stack
(ABAP+Java) is no longer supported.

Primary application server instance: DVEBMGS<Instance_Number>

Additional application server instance: D<Instance_Number>

ABAP Central Services instance (ASCS instance):

ASCS<Instance_Number>

Central Services instance (SCS instance): SCS<Instance_Number>

Enqueue replication server instances (one for the ASCS and one for the
SCS instance): ERS<Instance_Number>

The enqueue replication server instances are only mandatory in a high-

availability system.

 Example
For an SAP ABAP+Java system based on SAP NetWeaver 7.1 to SAP NetWeaver
7.4 with SAP system ID C11, the instances might look as follows:

Primary application server instance: DVEBMGS00 (the Java EE Engine

is installed in /usr/sap/C11/DVEBMGS00/j2ee)

Additional application server instance: D01 (the Java EE Engine is

installed in /usr/sap/C11/D01/j2ee)

ABAP Central Services instance (ASCS instance): ASCS02

Enqueue replication server instance (ERS instance) for the ASCS

instance: ERS03

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 73/115
1/22/2020

Directory Description

Central services instance for Java (SCS): SCS04

Enqueue replication server instance (ERS) for the SCS: ERS05

On a primary application server instance with SAP system ID C11 and

instance name DVEBMGS00, the Java EE Engine is installed in
/usr/sap/C11/DVEBMGS00/j2ee.

The instance names (instance IDs) of a Java system are as follows:

Application server instance: J<Instance_Number>

Central services instance for Java (SCS): SCS<Instance_Number>

Enqueue replication server instance: ERS<Instance_Number>

The enqueue replication server instance is only mandatory in a high-

availability system.

 Example
For an SAP Java system with SAP system ID C11, the instances might look as
follows:

(Primary) application server instance: J00 (the Java EE Engine is

installed in /usr/sap/C11/J00/j2ee)

(Additional) application server instance: J01 (the Java EE Engine is

installed in /usr/sap/C11/J01/j2ee)

Central services instance for Java (SCS): SCS02

Enqueue replication server instance (ERS) for the SCS: ERS03.

The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate directories in

/<sapmnt>/<SAPSID>/ for storing data used by several instances.

SYS is logically shared and available on each host of the SAP system. Its subdirectories
contain symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on
the SAP global host, as shown in the gures above.

Whenever a local instance is started, the sapcpe program checks the executables against those in
the logically shared directories and, if necessary, replicates them to the local instance. For more
information about sapcpe, see The sapcpe Program documentation. Executables located in
/usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe subdirectory of the
instance directories.

/usr/sap/trans Global transport directory for all SAP systems

The global transport directory is used by the Change and Transport System (CTS). The CTS helps
you to organize development projects in the ABAP Workbench and in Customizing, and then
transport the changes between the SAP systems in your system landscape. For more information,
see the Change and Transport System documentation.

Backing Up and Restoring your SAP System

on IBM i
Use
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 74/115
1/22/2020
This procedure describes how to perform a full system backup including all SAP instances in offline mode and how to restore the
data. For information about backing up partial data, see section Backup and Recovery in the SAP Database Guide: IBM DB2 for i.

Prerequisites
Backing Up the Entire System

All users have logged off and all SAP systems have been stopped.

This is important because the IBM i shuts down all subsystems before starting this type of backup.

You are working at the console, and you are logged on as QSECOFR or as a user with *SAVSYS rights and authorization to
start and end subsystems.

You have enough storage media (that is tapes) available and initialized to contain the complete backup of your system.

Restoring the Entire System

A console screen is available and connected to your IBM i server.

Backup media with SAVSYS information, IBM libraries and user data from the most recent backup is available.

A CD-ROM with the licensed internal code (LIC) is available. It is required if you are restoring the licensed internal code
from a device that is not connected to the system bus (bus 1).

You are aware of your disk con guration, that is you know which auxiliary storage pools (ASPs) were con gured before the
start of the recovery.

Procedure
Backing Up the Entire System

1. Enter command GO SAVE.

The Save menu appears.

2. Select option 21 ( Entire system).

 Note
This ends all active subsystems, saves all system and user data, and starts the controlling subsystem. When starting
the controlling subsystem, the automatic startup program that is speci ed in system value QSTRUPPGM is executed
automatically and all other subsystems are started again.

3. To verify that the backup is complete, enter command DSPJOBLOG to look for error messages that might have occurred
during the backup.

 Note
If errors occurred, your backup might not be complete. Therefore, it might be unusable for recovery.

4. If your SAP systems are not started automatically by the system startup program, start your SAP systems now.

Restoring the Entire System

1. If your system is partitioned, shut down the partition using the command PWRDWNSYS, the Dedicated Service Toole (DST),
or the Hardware Management Console (HMC). If the system is not partitioned, shut down the system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 75/115
1/22/2020
2. Place the system or partition in manual mode and choose IPL source D (IPL from tape or optical media). It depends on your
system con guration whether you perform these steps through the control panel, the option Work with system partitions
in the System Service Tools (SST), the Dedicated Service Tools (DST), or the Hardware Management Console (HMC).

3. Load the SAVSYS media to the alternate IPL device (usually a tape unit) and the LIC CD to your CD drive.

4. Start the system or partition.

5. After a while, the Install Licensed Internal Code (LIC) screen appears with the following options:

1. Restore Licensed Internal Code

2. Install Licensed Internal Code and Initialize System

3. Install Licensed Internal Code and Recover Con guration

4. Install Licensed Internal Code and Restore Disk Unit Data

5. Install Licensed Internal Code and Upgrade Load Source

Choose option 3 Install Licensed Internal Code and Recover Con guration.

6. Enter F10 on the Install LIC and Initialize System - Con rmation screen.

7. If you are installing the licensed internal code on the primary partition of a partitioned system, you receive the following
error report after the LIC has been loaded:

Unit has incorrect logical partition configuration

8. To recover your LPAR con guration, start the Dedicated Service Tools (DST) and choose option 11 Work with system
partitions, and then option 4 Recover partition data and option 1 Recover primary partition con guration data.

 Note
You also receive the following error report after the LIC has been loaded:

Missing disk configuration

9. To recover your disk con guration and the journal receivers in your user ASP, start the Dedicated Service Tools (DST).

10. Choose option 4 Work with disk units, and then option 2 Work with disk unit recovery and option 5 Recover disk
con guration.

 Note
The system displays a Problem Report with two problems:

Load source has been re-built and ASPs will be cleared.

You can ignore these reports.

11. To continue, enter F10.

 Note
You must verify your disk con guration at the end of the procedure.

12. Return to the menu IPL or Install the System and choose option 2 Install the operating system.

13. Con rm the installation of the operating system when requested to do so.

14. Complete the requested information during the installation as needed, such as the language feature selection or install
option.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 76/115
1/22/2020
15. Choose 1 Take defaults for the install option.

16. When the installation is completed, the system automatically performs an IPL and displays an IPL Sign On screen.

17. Sign on with user pro le QSECOFR.

 Note
The system requires no password at this time. The system displays the Change Password display. The system sets the
QSECOFR user pro le to *EXPIRED, and the password to QSECOFR. When the IPL completes, the QSECOFR password
is the password associated with the SAVSYS media you used.

18. Enter command GO RESTORE.

The Restore menu appears.

19. Select option 21 ( System and user data).

 Note
This ends all active subsystems, restores user pro les, con guration data, libraries, documents, folders, objects in
directories and authorities, and starts the controlling subsystem. When starting the controlling subsystem, the
automatic startup program that is speci ed in system value QSTRUPPGM is executed automatically and all other
subsystems are started again.

20. To verify that the restore is complete, enter command DSPJOBLOG to look for error messages that might have occurred
during the restore. If errors occurred during the restore, your system might not be complete. Therefore, the system might
be unusable.

21. If the restore was started as a result of an unplanned system outage, or if your backup contains partial transactions, you
must perform data recovery. Recover all changes since the last backup until the time shortly before the error as described
in section Recovering Changes to the SAP System Since the Last Backup in SAP Database Guide: IBM DB2 for i.

22. If your SAP systems are not started automatically by the system startup program, start your SAP systems now.

More Information
For more information about system backup and restore, see the IBM documentation iSeries Backup and Recovery (document
number SC41-5304).

Statistics
Use
Statistics give you an overview of the performance of your system. You can use the statistics to display the workload. There are the
following important statistics displays:

Workload Monitor

The workload monitor displays statistical data from the local ABAP system. The workload overview enables you to analyze
the performance of a system. You can also display the total values for all instances, and compare the performance of
particular instances over a period of time. A wide range of analysis views and data helps you to nd the source of
performance problems quickly and easily.

Global Workload Monitor

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 77/115
1/22/2020
The global workload monitor displays statistics for entire landscapes, including statistics for the non-ABAP components
J2EE Engine, BC, and ITS. For example, in this monitor you can display the load data created when external components
are started.

Analyzing Individual ABAP Statistics Records

Use ABAP statistics records to nd out which activities are running in your system. This is a log of system activities that is
implemented in the ABAP kernel. Every dialog step is logged and recorded with technical information, such as response
time, transaction code, or CPU time. Unlike the workload monitor, the individual records, not the aggregates, are displayed.

Functional Trace

Whereas the global workload monitor shows only aggregated data, you can use the functional trace to display raw
statistical data (single records) from both ABAP systems and the non-ABAP systems J2EE Engine, BC, and ITS in complex
system landscapes. The functional trace uses RFC (or agents in non-ABAP systems) to get the raw data, which means that
the information has a higher level of detail. For example, you can use the functional trace to trace actions that belong to a
business process across system boundaries. You can also display traces such as the SQL trace or DSR trace from the
functional trace.

Functional Trace
Purpose
You can display raw statistical data (individual records) and traces from ABAP and non-ABAP systems from complex system
landscapes using the functional trace. The statistics and trace data of remote ABAP systems is accessed by RFC. For remote non-
ABAP systems, the data is read using NetWeaver Management Agents.

The raw statistics data can originate from ABAP statistics records or Distributed Statistics Records (DSRs). While ABAP statistics
records can only trace actions that are processed by ABAP components, with DSRs, you can trace actions that are processed
using non-ABAP components. This works for both types of statistics records across component boundaries. Components that
write statistics records send data from the statistics record with their communication with other components (their "passport"),
meaning that the originator of an action or a data ow of a business process can be traced even beyond component boundaries.

The statistics records and traces are rst stored locally on the relevant component and then read using RFC or the agent. The data
is transferred to the monitoring system and displayed directly in the functional trace there.

Integration
The functional trace extends the following two transactions:

The functional trace is an extension of the data selection transaction STAD that can only display raw statistics data for the
local ABAP system, and not for multiple ABAP systems and different DSR components, like the functional trace.

The functional trace is also an extension of the Global Workload Monitor (transaction ST03G). The Global Workload
Monitor can only display aggregated statistical data that has been collected by a special collector.

The functional trace, on the other hand, receives raw statistics data directly using RFC, or, in the case of non-ABAP
systems, from an agent. It provides a ner resolution of information. For example, you can use the functional trace to trace
actions that belong to a business process across system boundaries. You can also display traces in the functional trace. For
more information, see Difference Between Functional Trace and Global Workload Monitor.

Features
The functional trace provides the following functions:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 78/115
1/22/2020
You can use system selection to choose the systems for which you want to analyze statistics records and traces. You can
restrict the analysis to the local system or extend it to include systems in a system landscape or a Business Process. You
can create system lists.

You can de ne a period for reading the statistics records in the data selection. The raw statistics records are read for this
period for the components speci ed in the system selection.

You can also specify parameters in the data selection with which you can also lter the raw statistics records, such as by
the initial user and the initial system. The system displays the ltered statistics records in the analysis view.

If errors occur, you can display the application logs of the function trace to nd the cause of the error.

You have various options for displaying and analyzing the raw data. For example, you can display the statistics records
sorted chronologically in a call hierarchy or in a list.

In the analysis view, you can display traces for ABAP systems (SQL trace and runtime analysis) and DSR traces in addition
to the raw statistics records. You can activate SQL traces directly from the functional trace.

More information:

Operating the Functional Trace

Difference Between Functional Trace and

Global Workload Monitor
The difference between the functional trace and the Global Workload Monitor is the type of data displayed and the way in which
the data is displayed.

While the Global Workload Monitor displays aggregated data, the functional trace provides a more detailed view, since it displays
raw statistical data and can therefore, for example, trace the actions that belong to a business process across system boundaries.
The functional trace also displays traces from ABAP systems (SQL trace and runtime analysis) and from non-ABAP systems (DSR
traces).

The gure below shows the way in which the statistics records for the J2EE Engine are displayed in the two statistics display
transactions Global Workload Monitor (ST03G) and functional trace (STATTRACE):

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 79/115
1/22/2020

Since the J2EE Engine is a non-SAP R/3 System, the agent exports the statistics records. Depending on the type of display, the
agent either passes the data to the DSR collector to be aggregated (display variants a and b in the Global Workload Monitor) or
directly in the display transaction (display variant c in the functional trace). There are the following display variants:

1. Display Collector Aggregates After Hourly Collector Run

The collector aggregates the data during the transfer. The statistics records collected by the hourly collector run are stored
in the database and displayed in the Global Workload monitor (transaction ST03G).

2. Display Collector Aggregates Between Hourly Collector Runs

So that you do not have to wait until the hourly collector run to display aggregated statistics les, the Global Workload
Monitor (transaction ST03G) provides the Last Minutes' Load function, which allows you to aggregate and display
statistical data during runtime without storing it in the database.

3. Display Raw Data as Single Records

With single record display (c), the raw statistical data is displayed in the functional trace (transaction STATTRACE). The
data is read directly by the functional trace from the statistics les for each analysis using the agent. This means that the
granularity of the information in the functional trace is ner than that of the data in the Global Workload Monitor. If traces
were activated, the trace data is also transferred to the monitoring system.

See also:

Operating the Functional Trace

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 80/115
1/22/2020

Operating the Functional Trace

Use
This section provides an overview of the functions of the functional trace and contains links to additional information.

Features
The functional trace (transaction STATTRACE) is divided into a navigation area in the left subwindow, which you can show and hide
by choosing Full Screen On/Off and an analysis area in the right subwindow.

Functions

The following functions are available to you in the navigation area:

Function Description

Data You can use Data Selection to select the data to be analyzed. You can lter which individual statistics records (raw records) and,
selection if appropriate, trace data are to be displayed.

You can lter the data records by the following criteria:

Start date

Start time

Read period

Initial system

Initial user

Initial action

Transaction ID

The system displays the ltered statistics records in the analysis view. The data selection function interacts with the system
selection function. In the system selection, you de ne the systems from which statistics records are read. In the data selection,
you de ne a period for reading the statistics records. The raw statistics records are read for this period for the components
speci ed in the system selection. If you do not specify a speci c period, the system uses the default ltering, that is it lters to
the rst ten minutes after starting the transaction.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 81/115
1/22/2020

Function Description

Settings The following settings and log functions are available:

& log
System selection

Use this function to de ne the components from which you want to display raw statistical data.

Display and Analysis Options

You can use this function to select the display variant. You can specify whether statistics records are displayed hierarchically or
in a list. You can also specify the time zone and the RFC wait time.

Activating/Deactivating the Trace

You can use this function to activate the SQL, enqueue, RFC, or buffer trace for ABAP systems that you have selected in the
system selection, as in the performance analysis (transaction ST05).

Application Log

If an error occurred in the functional trace, you can use this function to nd the cause of the error.

General Data

If you have performed an analysis and the desired statistics record, the system displays the following general information at the
top of the output area:

Period analyzed (date, time)

Components analyzed

Components that do not deliver data

Time zone

The date and time of the rst and last statistics record of the period being considered are also shown.

ALV Tree Control

After a successful analysis, the raw statistics data is displayed as a call hierarchy in an ALV Tree Control.

ALV Grid Control

As there is no sort function for the call hierarchy, you can display the statistics records as a list. The list display uses an ALV Grid
Control, with which you can extensively adjust the selected view to your requirements. Using the standard functions of the ALV
Grid Control, you can

Show and hide columns

Sort rows by the contents of a column

Set and delete lters

Perform summations

Export tables as a le type of your choice

Display tables as graphics

Save sort orders, lters, and selected columns as your layout

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 82/115
1/22/2020

See also:

System Selection

System Selection
Use
Use this function to de ne the components for which you want to display raw statistical data and, if appropriate, traces. The
creation of the raw statistical data and the writing of the traces is independent of this system selection. The system selection is
used primarily to display data for speci c systems so that the interface is structured in as clear a way as possible.

The following functions are also available to you:

You can check which components are entered in the CCMS System Component Repository (SCR).

You can save and recall a total of ve different sets, each of which contains a set of monitored systems.

Integration
In the system selection, you de ne the systems from which statistics records are read. In addition to system selection, you use
data selection to de ne a time period for reading the statistics records. The raw statistics records are read for this period for the
systems speci ed in the system selection.

You can also specify parameters in the data selection with which you can also lter the raw statistics records, such as by initial
user and initial system. The system displays the ltered statistics records in the analysis view.

With system selection, you can also access the systems that are known to the Solution Manager and, in this way you can, for
example, monitor all systems that are assigned a particular business process. However, for this it is necessary that you specify the
RFC destination and the name of the data model of the Solution Manager. Choose SolMan to do this. The utilized data model is
CBP Data Model.

Prerequisites
Before you can analyze statistical and trace data from remote components with the functional trace, system data (such as
the RFC destination) must be known. You can enter this data in the table manually, or call it up using Systems.

To be able to analyze individual statistics records from ABAP systems, the function group SAPWL_GLOB_STAT must exist
in the corresponding system. The function group SAPWL_GLOB_STAT is available as of SAP Basis 4.0B.

To be able to display traces from ABAP systems, the function group SAPWL_GLOB_TRACE must exist in the corresponding
system. The function group SAPWL_GLOB_STAT is available as of SAP Basis 4.6B.

Activities
To select and analyze systems, proceed as follows:

1. Start the functional trace by choosing Administration → CCMS → Control/Monitoring → Performance → Workload →
STATTRACE - Statistics Records (All) and Traces or with transaction STATTRACE.

2. Choose System Selection.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 83/115
1/22/2020
The system displays the current system list. To display another system list, choose an entry in the Systems menu. The
Features section below contains detailed information about this menu and the structure of system lists.

3. Make changes to the displayed list if required. You can, for example, (de)activate systems or add new systems. You can also
create a new list and save it as a set.

4. To start an analysis for the selected systems of a list, choose Apply.

The system rst performs a consistency check of the destination to the monitoring system. If the consistency check fails
for an entry, this entry is deactivated and a message is created for the application log. The raw statistics data is ltered in
accordance with the analysis data entered using data selection.

Features
To obtain a selection of components that can be monitored, choose the Systems menu. The menu has the following entries:

Entry Meaning

Local Includes the local ABAP system and all components for which statistical data is collected in this ABAP system. DSR statistical
data is collected in the system with which the NetWeaver management agent that is responsible for the transfer is registered.

All Lists all components that are registered in the SCR. This is both ABAP systems and non-ABAP systems (DSR components).

Solution Shows all components that are known to the Solution Manager. The system rst displays a table with the available Solutions.
Manager Choose the desired Solution. The associated systems are then displayed.

You can also select systems that belong to a particular business process. To do this, choose Business Processes.. Choose the
desired process and the desired system.

Set No. 1 Lists the components that you have previously saved as one of the ve possible sets.
-5

Current Contains those components that were active when the system selection was called.
List

The following data is displayed for the selected components:

Column Meaning

Activated Indicator with which you can activate and deactivate the analysis of the component

Component Component name (from the SCR) and, for ABAP systems, the name of the system
Name

Comp. type Name of the component type (from the SCR) and, for ABAP Systems, the entry SAP R/3

Mon.Sys Monitoring system in which the statistical data of the component is collected; for ABAP systems, the system itself

Mon. Sys. RFC destination of the monitoring system; this entry is empty if the monitoring system is the local ABAP system
Dest.

Indirect RFC destination of an ABAP system (for example, the system of the Solution Manager) in which the destination of the
Dest. monitoring system is known; access to the statistical data of the monitoring system is then performed indirectly through this
intermediate system

Release Release of the SAP Web Application Servers; the system makes this entry automatically

 Note
The speci cations for component name, component type, and the name of monitoring system are mandatory.

An empty eld for a destination and the entry NONE are equivalent.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 84/115
1/22/2020
Ensure that you use the correct notation for all elds of the table (upper- and lower-case).

You can change the speci ed data in the table. To save the table contents to the database, choose the Save menu and one of the
ve sets available.

See also:

System Selection Example

Selecting Data for the Functional Trace

Example: System Selection with Indirect

Destination

The indirect destination is the RFC destination of an SAP System (such as the Solution Manager system), in which the destination
of the monitoring system (monitored system) is known. The statistical data for the monitored system is then accessed indirectly
using this intermediary system.

For example, you have three ABAP systems: A, B, and C, and you want to monitor systems B and C from system A. The RFC
destination of system C is, however, only known to system B. In this case, the destination of system A to system B is the indirect
destination. To create a system list in the system selection for this example, follow the procedure below:

1. Open the functional trace using transaction STATTRACE.

2. Choose System Selection → Systems and then any free set.

3. Insert three rows by choosing Insert Rows; one for each system. The columns of the rows mean the following:

Column Description

Activated Indicator with which you can activate and deactivate the analysis of the component

Component Component name (from the SCR) and, for ABAP systems, the name of the system

Comp. Type Name of the component type (from the SCR) and, for ABAP Systems, the entry SAP R/3

Mon.Sys Monitoring system in which the statistical data of the component is collected; for ABAP systems, the system itself

Dest. RFC destination of the monitoring system; this entry is empty if the monitoring system is the local ABAP system
MonSys

Indirect RFC destination of an ABAP system (for example, the system of the Solution Manager) in which the destination of the
Dest. monitored system is known; access to the statistical data of the monitored system is then performed indirectly through this
intermediate system

Release Release of the SAP Web Application Servers; the system makes this entry automatically

 Note

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 85/115
1/22/2020
1. Enter A, B, and C as component names.

2. Enter the component type, in this case SAP R/3.

3. Specify the system in which the statistics records are collected as the monitoring system for the system.

For ABAP systems, this is always the system itself, that is, for system A, enter A as the monitoring system, entering the
monitoring system B for system B, and so on.

4. The elds RFC Destination to the monitoring system (Dest.MonSys) and Indirect Destination for the Monitoring System
(Ind. Dest.) remain empty in the row for system A, because it is the local system.

5. In the row for system B, enter the RFC destination from system A to system B in the Dest. MonSys eld. Ind. Dest remains
empty, since you are not using an indirect destination in this case.

6. In the row for system C, enter the RFC destination from system A to system B as the Ind. Dest and the RFC destination
from B to C as Dest. MonSys

7. Finally, activate all systems in the Activated column and save the set.

See also:

System Selection

Selecting Data for the Functional Trace

Selecting Data for the Functional Trace

Use
You can use data selection to select the data to be analyzed. With this function, you lter which statistics records (raw records) are
to be displayed in the analysis view of the functional trace (transaction STATTRACE).

Prerequisites
You have de ned the systems from which statistics records are to be analyzed in the system selection.

Procedure
Follow the procedure below to select data for the functional trace:

1. Start the functional trace (transaction STATTRACE).

2. Choose Data Selection in the left subwindow of the initial screen.

You can show and hide the left subwindow by choosing Full Screen On/Off.

3. To determine the analysis interval, specify start date, start time, and the read period(in minutes).

4. You can optionally restrict the individual records to be displayed using the following speci cations:

Initial system

Initial user

Initial action

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 86/115
1/22/2020
Transaction ID

With these input parameters, the system lters using the passport, which contains values for these parameters. If statistics
records are written beyond component boundaries, the passport is sent together with the communication between the
components. You can use the passport to determine which steps belong to an action, even if they were performed on
different components.

The initial system is the starting system of an action that runs over multiple components. The action that is started in this
system is the initial action that is started by an initial user and for which the transaction ID is assigned. The transaction ID
is the GUID from the passport that identi es all dialog steps.

5. If desired, you can choose the options Read Additional Records and No ADM Records:

If you determine that the delivered data is not sufficient for your requirements and want to ll out a new time
window, activate Read Additional Records, so that the newly collected statistics records are added to the statistics
records that have already been collected. If you do not activate this option, the previously read statistics records are
deleted, and the system displays only the statistics from the new query.

The No ADM records option is activated by default; that is, the ADM statistics records are hidden. This is useful,
since there is a large number of ADM statistics records and this can therefore affect the performance.

6. Con rm your selection.

Result
The system displays the statistics records with their general information. You have the following options for a new data selection:

Fill out a new time window using New Selection

Choose 1 Time Unit Previously to display the statistics records that were written one time unit earlier, where the time unit
corresponds to the read period that you used for the previous data selection

Choose 1/2 Time Unit Previously to display the statistics records that were written half a time unit earlier

Choose 1/2 Time Unit Later to display the statistics records that were written half a time unit later

Choose 1 Time Unit Later to display the statistics records that were written one time unit later

For more information about individual statistics records, choose the relevant record to display the corresponding statistics record
in the Detail View.

See also:

Analysis View

Analysis View
De nition
The analysis view of the functional trace (transaction STATTRACE) displays the raw statistical data that has been ltered in
accordance with the system selection and the data selection.

You can also for ABAP systems (SQL traces and runtime analyses) and display traces for non-ABAP systems.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 87/115
1/22/2020

Displaying the Raw Statistical Data

A data record contains the most important basic data, such as:

Action performed

User

Service

Subrecords for DSRs, where the following abbreviations are used among others:

RS for RFC server

RC for RFC client

CL for client

AD for ADM message

TB for table records

HC for HTTP Client Records

CS for call subrecords (a DSR component calls an external component)

Response, DB, DBP, and CPU time

Call, wait, load, and generation times

Process and thread IDs

Memory usage

You can use the usual layout functions to add columns, such as the GUID from the passport or the component name.

The analyzed ( ltered) raw statistical data is displayed in one of the following display types, depending on your settings in
the display and analysis options:

Hierarchy Display:

In the hierarchy display, the system rst displays a list of initial systems; that is, systems in which an action was started. When an
action was also processed in other components or instances, the system indicates this with >>>. The system displays a complete
statistics record next to an initial system. This contains the totals of the values of all statistics records that are involved in the
action triggered by the initial system.

If you want to display what this complete statistics record consists of, the call hierarchy that was used, expand the tree for the
corresponding initial system. The system displays all components that the action ran through and the associated raw statistics
records.

 Note
An administrator determines that a particular background job repeatedly lasts too long. To determine exactly how the time was
spent, the administrator enters the time period to be investigated in data selection and speci es the background job as the
initial action. A list of systems from which the background job was initially started then appears. The administrator can expand
the tree for an initial system whose action lasted a long time and display the call hierarchy. This means that the administrator
can see the individual stations that the action ran through. The statistics records for the individual stations are always
displayed in chronological order.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 88/115
1/22/2020

List Display

In the list display, the individual records are grouped and listed by transaction ID with color coding. The list display uses an ALV
Grid Control, with which you can extensively adjust the selected view to your requirements. You can use the standard functions of
the ALV Grid Control to

Show and hide columns

Sort rows by the contents of a column

Set and delete lters

Perform summations

Export tables as a le type of your choice

Display tables as graphics

Save sort orders, lters, and selected columns as your layout

You can switch between the Hierarchy and List displays by selecting the appropriate entry in the Displaytree in the lower left
subwindow.

You can show and hide the left subwindow by choosing Full Screen On/Off.

By double clicking a raw statistics record, you can switch to the detail view, which provides more detailed information.

See also:

Display and Analysis Options

Trace Display
As of SAP Web Application Server 6.40, you can also display the raw statistical data traces of ABAP systems and non-ABAP
systems, as long as the traces were previously activated.

 Note
You can activate and deactivate SQL traces and RFC, Enqueue, and buffer traces directly in the functional trace using the
option Activate and Deactivate Trace in (De)Activate Settings & Log.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 89/115
1/22/2020
You can display the traces in the analysis view using TRACE Data. You can select the following traces in the hierarchical display:

SQL Trace

Runtime Analysis

DSR Trace

DSR Trace and Statistics Records

Only the rst three options listed above are available in list display.

Detail View
Use
If you have performed an analysis, the system displays the basic information for the raw statistics records in the analysis view. You
can view more detailed information in the detail view.

Activities
Follow the procedure below to display detail views:

1. Choose a statistics record in the analysis view.

The Detail Analysis of Selected Statistics Record screen appears, in which you can display detail information in list form.
The detail information is displayed using different detail views. There are detail views, among others, for the times,
databases, data quantities transferred, and so on.

2. If you require a different detail view, open the Detail Viewdropdown menu.

You can select a detail view in this menu. The following detail views are especially important:

Detail View Description

Client Info The Client Info detail view corresponds to the client info record (certi cate subrecord) of the passport.

With distributed statistics records (DSRs), the passport is sent with the communication so that it is possible to trace, for
example, the initiator of an action or the data ow of a business process even beyond component boundaries.

The Client Info detail view contains the following information:

Name and type of the initial components, such as component ECA of type SAP R/3

Service type, such as background

Initial user

Initial action performed, such as a background job

Action type

Name of the calling component, such as BCE

This means that component ECA starts a background job in BCE.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 90/115
1/22/2020
RFC This RFC detail view and the following RFC detail views provide detailed information about the actions of the DSR
Dest.Records components.
Client
The components that call other components (destinations) are called clients.

This detail view shows which components the client has called. The following details are displayed, among others:

Local destination

Remote destination

Number of calls

Call time

Received data (in bytes)

RFC Single The individual data records for the client's calls are displayed in this view.
Records
This detail view provides the following information in addition to that provided by RFC Dest. Records Client:
Client
Program name

Name of the executed function

The system always displays the statistics records that had the highest performance demands. The system displays up to
ve statistics records.

RFC Like RFC Dest.Records Client with the difference that the component is functioning as a server here. The components that
DEST.Records are called by other components (destinations) are called servers.
Server
This detail view shows which components called this server.

RFC Single Like RFC Single Records Client with the difference that the individual data records displayed here are for the calls of the
Records server.
Server

See also:

Analysis View

Display and Analysis Options

Display and Analysis Options

Use
You have the following options through the Display and Analysis Options function:

· You can change the display variant of the analysis view (default setting: hierarchy). The statistics records are sorted
chronologically, as far as possible, in the functional trace. Using the display and analysis options, you can choose whether
the records in the analysis view are to be displayed in a call hierarchy or in a list. You can choose between list display and a
hierarchy after an analysis has been performed. The options are displayed in the lower left subwindow.

· You can change the timeout with RFC Wait Time, that is, the period that the system waits for a remote system to
deliver data (default setting: 2 minutes).

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 91/115
1/22/2020
· You can also select a different time zone (default setting: CET).

Application Log

Use
You can determine the cause of an error in the function trace using the application log function.

Activities
1. Select the application log function.

The Display Log screen appears. The system displays the current log and, if appropriate, the associated message list in the
upper half of the screen.

The following message types exist:

Termination

Error

Warning

Information

1. The message texts are displayed in the lower half of the window.

See also:

Operating the Functional Trace

Distributed Statistics Records (DSRs)

De nition
Statistics records are created to enable you to monitor the performance of an SAP System and its components. These statistics
records provide information about the workload generated and the resources used in the system by actions. This provides you
with a very exact picture of the quality of a system. The extension of this concept for non-ABAP components uses Distributed
Statistics Records (DSRs). With DSRs, as with the statistics records for ABAP systems, you can trace actions that are processed
over several components.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 92/115
1/22/2020
For this reason, there is a passport that is sent together with every communication. Among other things, the passport contains a
GUID that is generated with a new Logical Unit of Work (LUW) and which is used when calling other components within the LUW.
By evaluating the DSRs globally, you can collect and analyze all of the data for a LUW.

Structure
A DSR (= an action) consists of a main record and the subrecords connected to it:

Main record

The main record contains performance and administration information about the action of a component.

Certi cate Subrecord (Cert Subrecord)

The certi cate subrecord speci es the source of the LUW. The data contained in this subrecord forms the passport,
together with the GUID. There is a maximum of one certi cate subrecord for each main record.

Call Subrecord

The call subrecord contains information about the called component. There can be any number of call subrecords for each
main record.

Integration
You can display the DSR in the monitoring SAP System using the Global Workload Monitor and the functional trace:

The raw statistical data (single record analysis) is displayed in the functional trace (transaction STATTRACE).

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 93/115
1/22/2020
The data is displayed in the Global Workload Monitor (transaction ST03G) after the collector aggregates it. You can display
the aggregated data from different points of view, such as workload overview or time pro le.

For more information, see Difference Between Functional Trace and Global Workload Monitor.

Passport
De nition
If the system is generating Distributed Statistics Records (DSRs), that is, of statistical records of the instrumented non-ABAP
systems, the passport is sent during communication between the components. Among other things, the passport contains a GUID
that is generated with a new Logical Unit of Work (LUW) and which is used when calling other components within the LUW. By
evaluating the DSRs globally, you can collect and analyze all of the data for a LUW. The passport contains a trace ag with which
performance trace information can be written for every component involved in a LUW for exactly this LUW.

Structure
The passport corresponds to the certi cate subrecord (cert subrecord) of the DSR and contains the following elds:

TransID/GUID

TraceFlag to the set the trace ag

Initial SysID/ComponentID with the ID of the initial system or initial component

Initial ServiceType with the initial service type

Initial Action with the initial action

Initial ActionType with the initial action type

Initial UserID with the initial user ID.

These elds are only lled when the passport is created. All subsequent components leave these elds unchanged.

PreSysID/PreComponentID with the ID of the previous system or previous component

 Note
The ID of the previous system or previous component is always lled with a system or component's own ID before the passport
is sent. This means that the direct predecessor can be identi ed when the passport is received.

Integration
The functional trace (transaction STATTRACE) can lter raw statistics records using the data of the certi cate subrecord
(also known as client info record). To do this, you must enter the appropriate values in the data selection input parameters.

The gure below shows how the passport is forwarded and linked to the relevant statistics records:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 94/115
1/22/2020

1. The passport is created in the component in which a LUW is initiated. In this example, this is the J2EE Engine. The J2EE
Engine sends the passport to the ABAP system and writes a call subrecord.

2. The ABAP system receives the passport and stores its data as a certi cate subrecord. It calls another component, for
which a call subrecord is written.

3. The passport is transferred to another component during the RFC call and the certi cate subrecord is written in turn into
the statistics there.

4. The complete statistics records are transferred to the central monitoring system (CEN) and displayed.

Troubleshooting
Use
You can nd troubleshooting information (problem analysis scenarios) for speci c installable software units in the relevant
documentation sections.

A central entry point for all issues is the SAP Technology Troubleshooting Guide on http://wiki.sdn.sap.com/wiki/display/TechTSG
.

Integration Tests for ABAP Applications

Use
It is necessary to test the functions and performance of your solution during the entire life cycle of a SAP solution. SAP Test
Workbench provides you with an environment for all test phases, which you can use for testing in the following cases:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 95/115
1/22/2020
Implementation of SAP solutions

Integration of new components and business scenarios

Customer developments

Function tests

Integration tests with other components

Upgrades, regression tests

Importing support packages

Integration
The SAP test tools Test Workbench and Extended Computer-Aided Test Tool are part of SAP Web Application Server.

Features
Test Preparation

Creation of manual and automated test cases

Management of manual and automated test cases

Creation of test plans

De nition and management of tests

Perform Test

Execution of mass tests using Extended Computer-Aided Test Tool and Computer Aided Test Tool

Integration of test cases and test scripts of non-SAP providers

Assignment of worklists (test packages) to individual testers

Test Evaluation

Permanent overview of test progress and test results

Complete documentation of test processes in the test plans (test cases, test case descriptions, test results, test case
notes, error messages)

Detailed tabular and graphical evaluation of all test plans

Export test results to office applications

Message processing

Setting Up Service Connections for SAP

Remote Support
Use

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 96/115
1/22/2020
If you want to use SAP remote services (for example, SAP EarlyWatch or Remote Consulting), or if you would like to permit an SAP
support consultant to work directly in your system to make a more precise problem diagnosis, then you need to set up a remote
service connection. Remote access has the major advantage that these operations are then immediately available to you.

Before you can open such a connection, a remote network connection to SAP must have been set up and the Service Connector
must be installed on your PC. Once the network connection is set up and the Service Connector is installed, you can create
different types of service connections that permit SAP employees access to your system.

For more information and detailed documentation on setting up remote service connections to SAP, see the SAP Support Portal at
http://service.sap.com/access-support .

You have to set up a remote service connection for each system. There are different connection types available to make it possible
for SAP employees to access your system. These differ based on the type of SAP system that is to be accessed and the type of
connection that you require. In the following table you will nd the most important connection types, along with the related
components where you can open customer service messages if you have any problems or questions:

Connection Type Details Set Up Information Message Component

Connection to SAP Service connection runs on the responsible SAP SAP Note 962516 XX-SER-NET-HTL
Solution Manager Solution Manager of the affected system.

R/3 Support The "classic" R/3 support connection from ABAP SAP Note 812732 SV-SMG-SVC
systems using SAProuter without WebDynpro.

HTTP Connection For a service session you require an HTTP connection to SAP Note 592085 XX-SER-NET-HTL
your systems to a speci c URL; Use this connection
type for Java systems and ABAP systems using
WebDynpro.

 Note
You can nd a complete list of the connection types in SAP Support Portal under http://service.sap.com/access-support .
Select the entry Connection Types Available in the navigation area to the left of the screen.

There are also roles for read-only access for remote support. These roles are available in the STPI plug-in and are generated when
a managed system is connected to SAP Solution Manager. These roles are:

SAP_RCA_SAT_DISP for ABAP

SAP_JAVA_SUPPORT for Java

 Note
You can only generate the role SAP_JAVA_SUPPORT using SAP Solution Manager. If you are not operating SAP
Solution Manager, use the role NWA_READONLY instead.

For more information, see Root Cause Analysis User Administration Guide . This document is in SAP Support Portal at
http://service.sap.com/solutionmanager SAP Solution Manager in Detail End-to-End Root Cause Analysis Media Library .

Composition Environment
Use
This section covers components that are used for building composite applications with the Composition Environment (SAP CE).
The following components are relevant for SAP CE as well, but are not part of this section as they are also relevant for other use

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 97/115
1/22/2020
cases of SAP NetWeaver:

Application Server Java

Using the Development and Production Infrastructure

Enterprise Services Repository & Registry

Portal

Universal Worklist

Con guring Adobe Document Services for Form Processing (Java)

Security

Composition Environment Platform

Use
The Composition Environment Platform is required as a prerequisite for Business Process Management and Business Rules
Management. It contains the Portal, Visual Composer, and the ECM Infrastructure.

Compatibility and Removed Usage Types

Use
Compatibility Usage Types

Compatibility usage types have been discontinued and are therefore not part of the standard SAP NetWeaver installation. If you
upgrade from a previous release, these usage types will of course still exist in your systems if they have been present in the source
release system.

In the area of Composition Environment there are the following compatibility usage types:

Guided Procedures

NWDS Update Site

Demo Applications

Removed Usage Type

With SAP NetWeaver 7.4 the following usage type has been removed: Composition Voice (CE-Voice). This usage type is not
available anymore from SAP NetWeaver 7.4 onwards. If you upgrade from a previous release to SAP NetWeaver 7.4 or higher, the
CE-Voice usage type will be removed.

Process Integration
Purpose
SAP PI facilitates the integration of business processes that span different departments, organizations, or companies.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 98/115
1/22/2020
SAP PI is based on general standards so as to enable 3rd-party systems to be integrated. At the center of SAP PI is an XML-based
communication that uses HTTP (Hyper Text Transfer Protocol). Irrespective of the scenario used, the application-speci c contents
are transferred in messages in user-de ned XML eXtensible Markup Language) from the sender to the receiver either via the
Integration Server, or directly between the systems involved.

Enterprise Services Repository & Registry

Purpose
The Enterprise Services Repository and Registry combines the advantages of language-independent modeling and speci cation of
applications in the Enterprise Services Repository with the option of publishing application services in the Services Registry and to
classify them there also. The Enterprise Services Repository and Registry therefore contribute greatly to the development of
applications according to an Enterprise Service-Oriented Architecture (SOA).

Features
Enterprise Services Repository (ES Repository)

Access ES Repository content using the Enterprise Services Builder (ES Builder). Some of the most important ES Builders editors
are:

A modeling environment for the model-driven development of applications.

WSDL-based editors for specifying governed service interfaces, message types, and data types.

Editors for design objects to utilize the Integration Server's integration logic (for example, editors for mappings and
integration processes).

More information: Enterprise Services Repository

Services Registry

Some of the most important properties of the Service Registry are:

It meets UDDI 3.0 (UDDI: Universal Description, Discovery, and Integration).

It provides a classi cation system and search tools. In this way it is easier to nd services that were published in the
Services Registry.

It contains all information in WSDL that are required for calling a service on the consumer side.

More information: Finding Services in the Services Registry

Conversion Agent
Use
SAP no longer resells the SAP Conversion Agent by Informatica as of enhancement package 1 for SAP NetWeaver 7.3.

Documentation for older releases is provided in SAP Developer Network (SDN): http://sdn.sap.com , SOA Middleware Service
Bus .

Choose Mediation, Transport and Reliability in the Knowledge Center area. A new page opens.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e10000000… 99/115
1/22/2020
Click on the SAP Conversion Agent by Informatica link and further down on the page again click on the SAP Conversion Agent by
Informatica link.

Mobile
Use
SAP NetWeaver Mobile is a technology solution of SAP NetWeaver on which mobile solutions for SAP Business Suite are
developed. Using the platform you can also mobilize non-SAP data.

SAP NetWeaver Mobile provides tools to develop, deploy, and operate mobile scenarios for occasionally connected and always
connected mobile devices.

In the occasionally connected scenario, a mobile device connects occasionally to a mobile middleware. A mobile client is
installed locally on a mobile device and is equipped with a Web server, a database layer, and its own business logic. Staff
working remotely can therefore work offline and do not have to wait for a network connection to complete time-critical
business applications. SAP NetWeaver Mobile client offers tools for synchronization and data replication that make the
data of the mobile device consistent with that of the back end.

SAP NetWeaver Mobile is also equipped with a Java virtual machine and offers an open programming model with which
mobile applications can be developed. This open system architecture makes the platform independent of both the mobile
devices and the network and supports mobile devices such as Personal Digital Assistants (PDAs), laptops and smart
phones.

In the always-connected scenario, a mobile device remains connected to a mobile middleware for business operations.
Mobile applications are available on a server, and devices have to connect to this server for accessing the business
operations. SAP NetWeaver Mobile provides you an environment for creating mobile applications for this scenario. You
have to develop the applications only once and deploy to the server. The server renders the application UIs according to
different devices.

Overview Diagram

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 100/115
1/22/2020

SAP NetWeaver Mobile is the middleware for enterprise mobility, and it provides the following functionality:

Messaging and Network Monitoring

Device Management

Data distribution

Enterprise Identity

Security

As shown in the diagram above, you can access SAP data on mobile devices in either of the following ways:

Mobile clients shipped by SAP.

Customers can develop their applications using SAP NetWeaver Developer Studio and deploy them on SAP mobile clients.

Custom clients integrated with SAP

For devices that are not supported by SAP, customers can create mobile applications using technologies supported by the
device and integrate with the mobile middleware.

Partner-endorsed solutions such as CRM Sales for Blackberry

Documentation

Topic Description

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 101/115
1/22/2020

Topic Description

Master Guide at SAP Service Marketplace The Master Guide provides you with a central starting point for the
https://websmp106.sap- technical implementation of SAP NetWeaver Mobile
ag.de/~sapidb/011000358700001267942011E.pdf

Con guring SAP NetWeaver Mobile After installing the SAP NetWeaver AS for the Mobile capability,
administrators must con gure the DOE.

Additionally, in this section you also nd information to set up the SAP

NetWeaver Developer Studio and the mobile clients.

Administering SAP NetWeaver Mobile You can use the SAP NetWeaver Mobile Administrator to centrally
manage your mobile landscape

Developing Mobile Applications You develop mobile applications using the Data Orchestration
Workbench, and the SAP NetWeaver Developer Studio

Using the Mobile Client for Handhelds Handheld users must use the mobile client for accessing the mobile
applications. The client exchanges information with the DOE.

Using Mobile Client for Laptops Laptop users must use the mobile client for accessing the mobile
applications. The client exchanges information with the DOE.

Using the Mobile Client for Handhelds (MDK-based Applications) If you have mobile applications that are built on SAP NetWeaver MI 7.0,
you must install and use this mobile client.

Additional Information

Reference Description

SDN You can access essential information on SAP NetWeaver Mobile in SDN, information in the form of How To guides, eLearning,
articles, and so on. Additionally, you can also use the Mobile forum to exchange information with the community.

https://www.sdn.sap.com/irj/sdn/nw-mobile

Enterprise Portal
Use
This area provides industry-leading portal technology that delivers uni ed, personalized, and role-based user access to
information in your heterogeneous IT environment. It enables you to integrate SAP solutions, third-party applications, legacy
systems, databases, unstructured documents, internal and external Web content, and collaboration tools, thereby unifying key
information and applications to provide end users with a single view that spans IT divisions and organizational boundaries.

Features
This area is comprised of the following capabilities:

Area Description

Portal Provides a single point of access to SAP and non-SAP information sources, enterprise applications, information
repositories, databases, and services within and outside of your organization-all integrated into a single Web-based user
experience.

Knowledge Provides a central, role-speci c point of entry in the portal to unstructured information from various data sources.
Management Knowledge Management supports you in structuring information and making it available to the correct target audience.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 102/115
1/22/2020

Area Description

Collaboration Allows you to bring together members of project groups regardless of time and of their geographic location. Portal users
can use virtual rooms for common access and organization of documents, applications, and ideas.

Web Page Facilitates the creation and management of portal pages by authorized business users in an intuitive work environment
Composer that is fully based on standard portal capabilities. These pages can combine business applications with user-generated
Web content and static content.

Universal Provides centralized task management from which business users using the portal can manage, respond to, and delegate
Worklist daily work items.

SAP Business Warehouse

Purpose
Reporting, analysis and interpretation of business data are crucial to preserve and enhance the competitive edge of companies by
optimizing processes and enabling them to react quickly and in line with market needs. SAP Business Warehouse (SAP BW)
provides tools and functions that enable companies to attain these goals. In SAP BW, you can integrate, transform, and
consolidate relevant business information from productive SAP applications and external data sources. SAP BW provides you with
a high-performance infrastructure that helps you evaluate and interpret data. Decision makers can make well-founded decisions
and identify target-orientated activities on the basis of the analyzed data.

Integration
Integration with In-Memory Technologies

By using in-memory technologies, you can enhance the performance of SAP BW. In particular, they make it possible to efficiently
process demanding scenarios with unpredictable query types, high data volumes, high query frequency and complicated
calculations.

If you use a database to persist data, you can make it possible to access the data for a BW object faster by storing this data as an
index in SAP Business Warehouse Accelerator. More information: Creating and Managing BWA Indexes in the BW System.

Besides the performance bene ts, the SAP HANA database for data persistence offers further bene ts when executing analysis
and planning scenarios. In particular, you do not need a SAP BW Accelerator to improve performance. More information: Using the
SAP HANA Database.

Integration with BI Content Add-On

With BI Content, SAP delivers precon gured role and task-based information models and reporting and analysis scenarios for SAP
BW that are based on consistent metadata. BI Content provides selected roles in a company with the information that they need
to perform their tasks. The information models delivered cover all business areas and integrate content from almost all SAP
applications, as well as selected external applications. For more information, see the SAP Help Portal:
http://help.sap.com/bicontent.

Integration with SAP Business Explorer

SAP Business Explorer (SAP BEx) - the SAP NetWeaver Business Intelligence Suite - provides exible reporting and analysis tools
for strategic analyses, operational reporting, and decision-making support within a business. More information: SAP Business
Explorer.

Integration with SAP BusinessObjects Business-Intelligence-Solutions

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 103/115
1/22/2020
You can evaluate SAP BW data by using the SAP BusinessObjects products. More information: Integration with SAP
BusinessObjects.

SAP BusinessObjects tools allow you to make efficient and effective use of interfaces in the analytic engine. More information:
Integration with SAP BusinessObjects.

Integration with SAP Enterprise Information Management

In the Data Warehouse, integration with SAP Data Services and SAP Information Steward provides extra possibilities for using SAP
BW. More information: Integration with SAP Enterprise Information Management.

Features
Function Areas of SAP BW and SAP BEx

Area Description

Data Data warehousing in SAP BW enables the integration, transformation, consolidation, cleanup, and storage of data. It also
Warehousing incorporates the extraction of data for analysis and interpretation. The data warehousing process includes data modeling,
data extraction, further processing of data, and the administration of the data warehouse management processes. The
central tool for data warehousing tasks in SAP BW is the Data Warehousing Workbench.

Analytic The Analytic Engine provides OLAP functions and services, as well as services for BW Integrated Planning and analysis
Engine process design.

SAP These SAP Business Explorer tools include query, reporting, and analysis functions. As an employee with access
Business authorization, you can evaluate past or current data on various levels of detail and from different perspectives on both the
Explorer Web and in Microsoft Excel.

You can also use the Business Explorer tools to create planning applications, and for planning and data entry in BW
Integrated Planning.

You can use BEx Information Broadcasting to distribute content from business intelligence by e-mail, for example, as
precalculated documents with historical data, or as links with live data. You can also publish the information to the portal.

Generic Various tools and services support you in developing SAP BW objects and processes, supplying data in the system
Tools and landscape, performing tests and traces, as well as monitoring SAP BW in your system landscape.
Services

Interfaces SAP BW provides an open architecture in many areas: You can extract data from various systems into a SAP BW system
and evaluate this data for your reporting using various front-end tools.

Using the Using SAP HANA as the database for SAP BW enables highly efficient processing of queries and Data Warehouse load
SAP HANA processes. As well as replacing the old database, SAP HANA also replaces the SAP BW Accelerator, thus simplifying
Database administration and the infrastructure.

Database Administration
Use
Here you can nd more information on routine administration for databases supported by SAP.

Database Administration for IBM DB2 for i

Use

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 104/115
1/22/2020
You need to perform various tasks to administer your IBM DB2 for i database in an SAP environment.

Getting Started

If you are new to IBM DB2 for i, see the SAP Database Guide: IBM DB2 for i.

Tools

You can use the following SAP and IBM tools for the administration of IBM DB2 for i:

CCMS for IBM DB2 for i

Backup Recovery and Media Services. For more information, see the IBM documentation.

Tasks on Demand

The table below shows tasks that you need to perform when required:

Reason Task More Information

Database recovery Backup and Recovery SAP Note 825473

after data loss

Analysis of space None

Finding Database Storage Problems (IBM
consumption by
DB2 for i)
database objects
Perform Deleted Records Analysis (IBM
DB2 for i)

Inconsistencies Consistency Check (IBM DB2 for i) None

between ABAP
Dictionary and
database

Database Database Monitor (IBM DB2 for i) For more information about database performance analysis,
performance see the IBM documentation.
analysis

Maintain access to None

For information about how to connect
other systems, such
from an IBM i, Windows and Linux PPC to
as a BW source
an IBM DB2 for i database, see SAP Note
system
146624 .

For information about how to connect

from an IBM i with a BW system to a non-
SAP database on IBM i, see SAP Note
523381 .

New database Database upgrade For more information, see the IBM documentation.
release

Install software xes For more information, see the IBM documentation.
Order, load and apply program temporary
xes (PTF's) for IBM i

Download qxdaedrs.dll for Windows: SAP

Note 751451

Update JDBC drivers: SAP Note 654800

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 105/115
1/22/2020

Reason Task More Information

System copy System copy

For more information, see SAP Service Marketplace at
required
http://service.sap.com/instguides SAP
NetWeaver <Product/Release> Installation section
"System Copy".

SAP Note 585277

Password change On IBM i, sign on as QSECOFR and use command For more information about authority concept for SAP on IBM
required CHGUSRPRF for all instance users ( SID<nn>) on i, see SAP Note 173579.
all servers.

For more information on changing passwords on

a Windows operating system, see SAP Note
705886 .

Periodic Tasks

The table below shows tasks that you need to perform periodically:

Frequency Task Recommended Tool

Daily / weekly Run database backup SAP System Save Strategies

Daily / weekly Verify database backup Backup Overview (IBM DB2 for i)

Daily Check disk space State on Disk (IBM DB2 for i)

Database Administration for IBM DB2 for

Linux, UNIX, and Windows
Get an overview of the relevant tools for database administration of IBM DB2 for Linux, UNIX, and Windows and the relevant
documentation.

You need to perform various tasks to administer your database in an SAP environment. To do so, you can use either DB2 tools or
SAP system tools such as the DBA Cockpit.

 Recommendation
Where possible, use the tools provided by SAP to perform these tasks.

Tasks on Demand
The following table shows tasks that you need to perform when required:

Task Description

Database recovery In the case of a database failure with data loss, recover the database by DB2 means as described in Database
Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows.

Space management Check the growth of tablespaces and, if required, maintain the storage settings according to your requirements
using the DBA Cockpit.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 106/115
1/22/2020

Task Description

System Using the DBA Cockpit, check, for example, the following:
performance
Lock waits and deadlocks
monitoring
Performance snapshots of your database

Expensive SQL statements, database cache, and access plans of these SQL statements using the EXPLAIN
function

Database con guration

Database upgrade If required, upgrade your database to the latest version as described in the appropriate database upgrade guide.

System copy If required, perform a system copy using the installer as described in the appropriate system copy guide for your
SAP NetWeaver release.

Periodic Tasks
The following list shows tasks that you need to perform periodically:

 Note
Where possible, use the DBA Cockpit for these tasks.

Schedule regular backups of the database using the DBA Planning Calendar.

Check the alert message log.

Check the database growth.

Perform troubleshooting by checking the database logs, that is, the database diagnostic log and database noti cation log.

More Information
For more information, see the following documents:

Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows

Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows

Installation Guide: IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms

Upgrade to Version <no> of IBM DB2 for Linux, UNIX, and Windows

System Copy for SAP Systems Based on SAP NetWeaver <Release>

Installation: Systems Based on SAP NetWeaver <Release>

To nd the guide relevant for you, use the SAP NetWeaver guide nder.

Database Administration for IBM DB2 for

z/OS
You need to perform various tasks to set up administration for IBM DB2 for z/OS in an SAP environment.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 107/115
1/22/2020
Here you can nd a list of guides that provide information about database administration for SAP on IBM DB2 for z/OS:

Database Administration Guides

http://service.sap.com/instguidesnw under <Your SAP NetWeaver release> Operations Database-Speci c

Guides SAP DBA Guide: DB2 for z/OS (Vx) , where x stands for the number of the version

Security Guide

http://service.sap.com/instguidesnw under <Your SAP NetWeaver release> Operations Database-Speci c

Guides SAP Security Guide: DB2 for z/OS

Planning Guide

http://service.sap.com/instguidesnw under <Your SAP NetWeaver release> Operations Database-Speci c

Guides SAP Planning Guide: DB2 for z/OS

Installation Guides

http://service.sap.com/instguidesnw under <Your SAP NetWeaver release> Installation

For an overview of major enhancements and new features relating to monitoring and administration tools for SAP on System z, see
the SAP on DB2 for z/OS - Monitoring and Administration: News and Improvements area on the SAP Community Network at:
http://scn.sap.com/docs/DOC-8197 .

The SAP Community Network homepage (http://scn.sap.com/community/db2-for-z-os ) offers best practices, presentations,
blogs and more.

Database Administration for Microsoft SQL

Server
Use
You need to perform various tasks to administer your MS SQL Server database in an SAP environment.

Tools

You can use the following tools for the MS SQL Server database administration:

SQL Server Con guration Manager

SQL Server Management Studio

DBA Cockpit

Tasks on Demand

You need to perform the following tasks:

Start or stop the SQL Server database.

Restore the Database

Perform a system copy.

For more information, see http://service.sap.com/instguides SAP NetWeaver <Release> <Installation> <SAP
System> Homogeneous and Heterogeneous System Copy

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 108/115
1/22/2020
Periodic Tasks

You need to perform the following tasks periodically or daily:

 Note
Whenever possible, use the Planning Calendar for these tasks.

Backups

For more information, see the DBA Planning Calendar.

Monitor the MS SQL Server database

For more information, see the Database Performance Overview.

Database Server Checks

More Information
SAP / MS SQL Server DBA in CCMS

Database Administration for Oracle

Use
You need to perform various tasks to administer your Oracle database in an SAP environment.

Getting Started

If you are new to the Oracle database, see Getting Started with Oracle and the SAP System.

For information on the concepts behind Oracle database administration (DBA), see Approach to Oracle DBA.

Tools

You can use the following SAP tools for Oracle DBA:

BR*Tools for Oracle DBA (outside the SAP system)

Other Tools for Oracle DBA (outside the SAP system)

CCMS: Oracle (in the SAP system), including the DBA Planning Calendar.

Tasks on Demand

The table below shows tasks that you need to perform when required:

 Example
If you see a space management alert (see below in Periodic Tasks), indicating that your tablespaces are running out of space,
you perform space management to correct the problem.

Reason Task More Information

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 109/115
1/22/2020

Reason Task More Information

Database start or stop Instance Management with Instance Management

BR*Tools

Database failure with data Restore and Recovery with Restore and Recovery
loss BR*Tools

Tablespace or data le Space Management with Space Management

management BR*Tools

Table or index management Segment Management with Segment Management

BR*Tools

Performance problem Maintain Database None

Parameters

New database version Database upgrade http://service.sap.com/instguides Other Documentation Database

Upgrades Oracle

System copy required Database copy http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver
<Product> 7.1 Installation

Periodic Tasks

The table below shows tasks that you need to perform periodically:

 Note
Whenever possible, use the DBA Planning Calendar for these tasks.

You can choose from a range of prede ned action patterns that include the tasks listed here.

Frequency Task Recommended Tool

Daily DBA Planning Calendar with a prede ned action

Run database system check
pattern
Run database backup

Monitor the Oracle database and check for

alerts:

Space Management Alerts

Database Performance Alerts

Database Backup and Restore Alerts

Database Consistency Alerts

Database Health Alerts

Displaying the Status of a Day's Actions

Run update statistics

- daily task with Oracle 10g or later

Troubleshooting

The following problems are the most common in an Oracle environment:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 110/115
1/22/2020
Archiver stuck- for more information, see Backup and Database Copy with BR*Tools

Online backup crashed - for more information, see Fixing an Online Backup Crash

Tablespace full - for more information, see Extending a Tablespace with BR*Tools

More Information
You can nd full information on all aspects of Oracle DBA at:

SAP Database Guide: Oracle

For more information about Oracle DBA, see:

www.sdn.sap.com/irj/sdn/ora

For more information about advanced Oracle DBA, see:

Advanced Backup and Recovery

Oracle Real Application Cluster

SAP/Oracle Database Monitor for advanced Oracle database monitoring, also suitable to monitor an Oracle Real
Application Cluster (RAC)

Database Administration for SAP HANA

Use
Below you can nd information about routine administration tasks for SAP HANA:

DBA Cockpit for SAP HANA

SAP HANA Appliance Software documentation on SAP Help Portal:

http://help.sap.com/hana_appliance

Guides for SAP HANA:

SAP HANA Administration Guide

How to con gure, manage, maintain, optimize your SAP HANA installation, including backup and recovery.

http://help.sap.com/hana/hana_admin_en.pdf (PDF)

SAP HANA Security Guide (including SAP HANA Database Security)

Guide to enable security for SAP HANA appliance software, including the SAP HANA database.

http://help.sap.com/hana/hana_sec_en.pdf (PDF)

Database Administration for SAP MaxDB

Use
This section gives you an overview of the most important administration tasks that you need to perform for your SAP MaxDB
database.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 111/115
1/22/2020

 Note
The documentation for the SAP MaxDB database system also generally applies to SAP liveCache databases. Differences are
indicated in the documentation where necessary. For more information about the administration of SAP liveCache databases,
see Database Administration in CCMS: SAP liveCache Technology.

Technical System Landscape

More information: Concepts of the Database System, Technical System Landscape

Tools

You can choose one of the following tools to manage and monitor your SAP MaxDB database:

General SAP administration tools, for example DBA Cockpit, CCMS, Database Assistant and Alert Monitor

More information: DBA Cockpit: SAP MaxDB, Database Administration in CCMS: SAP MaxDB

Standalone SAP MaxDB administration tools, for example Database Studio (graphical user interface), Database Manager
CLI, Database Analyzer and XCONS (command line tools)

More information: Concepts of the Database System, Database Tools

Tasks on Demand

Perform the tasks in the table below when the corresponding event occurs.

Event Task Tool More Information

Database OFFLINE Start the database (ONLINE operational state) DBA Cockpit Operational State

Database Studio

Database failure with loss of data Restoring the Database Database Studio Restoring Databases

Damaged index Restoring the damaged index Database Studio Restoring Databases

Performance problems Analyzing Slow-Running Transactions Database Analyzing Database

Assistant Performance

DBA Cockpit

Database
Analyzer

Database Studio

Database connection to another system Creating a Connection Database Database Connection

required Assistant

Database Studio

New database version available Upgrading the database SAPInst Installation

Installation
Manager

System copy required Creating a database copy (prerequisite for a SAPInst Database Copy
system copy)
Database Studio

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 112/115
1/22/2020

Event Task Tool More Information

Other errors Analyzing the problem Database Troubleshooting

Assistant

Database Studio

XCONS

Periodic Tasks

Regularly perform the tasks listed in the table below. In SAP systems, use the DBA Planning Calendar for these tasks whenever
possible. Outside of SAP systems, use the Database Studio tool.

Occurrence Task Tools More

Information

Daily Monitor the database and Alert Monitor Monitoring

check if there are any alerts: Databases
DBA Planning
Monitoring the Data Calendar
Area
Database
Monitoring the Log Studio
Area

Caches (hit rate)

Activities Overview
(I/O, locking, logging)

User Tasks (database

sessions)

Performance

Backup/Recovery

Monitoring CPU usage Operating system commands Processes

Scheduling a Complete Data Backup DBA Planning Calendar Backing Up

Data
If you cannot or do not want to perform a complete data backup every day, Database Studio
then you should perform at least an incremental data backup on each
productive day.

The more current the last data backup is, the fewer log entries have to be
imported again if you need to restore the database.

Weekly Archiving Backup Files Operating Archiving

(archiving log backups) system Backup
commands Files
Only necessary for log
backups on data carriers of Database
the File type Manager CLI

Scheduling an Interactive Log Backup DBA Planning Calendar Backing Up

Log Entries
Only necessary if automatic log backup is switched off Database Studio

Scheduling a Database Structure Check DBA Planning Calendar Checking

Database
We recommend that you check the database structures at times when the Database Studio
Structures
database load is low, or using a system copy.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 113/115
1/22/2020

Occurrence Task Tools More

Information

Scheduling Updates of the SQL Optimizer Statistics DBA Planning Calendar SQL
Optimizer
Database Studio
Statistics

SAP Note
927882

More Information

Database Administration

Concepts of the Database System

Glossary

Database Administration for SAP ASE

Use
You need to perform various tasks to administer SAP Adaptive Server Enterprise (SAP ASE) in an SAP environment.

If you are new to SAP ASE, see the following guides:

Installation Guides

http://service.sap.com/instguidesnw SAP NetWeaver <Release>- Installation

Database Administration Guide

http://service.sap.com/instguidesnw SAP NetWeaver <Release> Operations Database-Speci c Guides

Component-based documentation for all functions and processes that are supported by SAP ASE:
http://help.sap.com/adaptive-server-enterprise

The SAP Community Network homepage (http://scn.sap.com/community/ase ) offers best practices, presentations, blogs and
more.

Security
The infrastructure of SAP NetWeaver technology platform supports you by delivering comprehensive security features for
heterogeneous environments.

In today's world of collaborative business processes and open system environments, security no longer means just adding a
rewall and using passwords to log on. It requires a complete approach that not only applies to your own IT landscape, but also to
issues that arise beyond your own borders, in which even simple organizational measures can have a signi cant impact. This
section describes the security functions and features available with SAP NetWeaver technology platform.

For information about our security recommendations, see the SAP NetWeaver Security Guide.

Related Information
User Authentication and Single Sign-On

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 114/115
1/22/2020
Identity Management
Network and Transport Layer Security
Recommended WS Security Scenarios
System Security
Digital Signatures and Encryption
Digital Signature (CA-DSG)
Security Developer Documentation

Security Developer Documentation

This section provides information about security that is relevant for developers. See the following table:

Section Description

Secure This section provides information about developing secure applications. It describes common security errors and
Programming weaknesses to watch out for as well as approved procedures so that your application functions securely.

Integrating Security This section describes how to use the available security functions when developing programs with the SAP
Functions NetWeaver Developer Studio.

Developing This section provides developer information regarding authentication and single sign-on.
Authentication
Enhancements

Related Information
Integrating Security Functions
Secure Programming
Developing Authentication Enhancements

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20285418&topics=48ba1bacca960611e1000000… 115/115