Transporting Read Access Logging Data

Prerequisites

Transports for the client must be enabled (transaction Start of the navigation path

SCC4

Changes and Transports for Client-Specific Objects End of the navigation path

Context

You can transport the following data from Read Access Logging:

Logging purposes
Log domains
Configurations of Read Access Logging for Web services
Configurations of Read Access Logging for Dynpro and Web Dynpro
Configurations of Read Access Logging for RFC
Dynpro and Web Dynpro recordings
Enabling in client setting*
User exclusion list*

Each entry in the user exclusion list. A user exclusion list entry always consists of a user for whom Read Access Logging is disabled.
Logging parameters

The parameter CLI_SWITCH that controls whether Read Access Logging is enabled in a client.

* These settings can be changed in production clients without the changes needing to be saved in a transport request. For this, the following settings in SCC4 are required:

Client role: Production
Changes and transports for Client-Specific Objects: Changes without automatic recording or Changes without automatic recording, no transports allowed

Note

Automatic transports are also possible. This means that when saving configuration changes in RAL, a transport popup appears. You must enable the Automatic recording of changes setting in transaction SCC4.

Procedure

Open Read Access Logging Manager (transaction code SRALMANAGER).
Go to the page in which the configuration you want to transport is located. For example, Recordings.
Select the configuration(s) you want to transport.
Choose the button.
Select an existing transport request or create a new one.
Choose OK.

Results

Your transport is created and can be viewed and released in SE09.

Note Only the configuration objects that you select are transported. For example, if you transport a Web Dynpro configuration, any associated recordings are not transported—you must transport these separately.