BC305_EN_46B

8/11/2019 BC305_EN_46B

http://slidepdf.com/reader/full/bc305en46b 1/221

© SAP AG 1999

R/3 System

Release 4.6C

April 2000

Material Number 5003 43 09

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 ii

© SAP AG 1999

Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®,

Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft

Corporation.

Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.

Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.

ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken

Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.

TouchSend Index ® is a registered trademark of TouchSend Corporation.

Visio ® is a registered trademark of Visio Corporation.

IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.

Indeo ® is a registered trademark of Intel Corporation.

Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc.

OSF/Motif ® is a registered trademark of Open Software Foundation.

ORACLE ® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.

UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.

ADABAS ® is a registered trademark of Software AG

The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP

(Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch,

SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or

brand names included herein are also trademarks or registered trademarks of SAP AG.

Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective

owners.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 iii

© SAP AG 1999

3 daysAdvanced R/3System Administration

2 daysR/3-TechnicalImplementation andOperation Management

Technical CoreCompetence

5 days

3 days

Software Logistics

3 days

Workload Analysis

3 days

Database AdministrationDB2 UDB

5 daysDatabase AdministrationDB2/390

3 daysDatabaseAdministration Oracle

Database

Administration Informix

5 days

DatabaseAdministration SAP DB

2 days

3 daysDatabase AdministrationMS SQL Server

3 days

TCC Workplace

2 days

LiveCache Administration

3 daysDatabase AdministrationDB2/400

Workplace

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 iv

© SAP AG 1999

© SAPAG1999filename(author) / 2

Database Administration

SAPDB

2 days

3 days

Advanced R/3SystemAdministration

Technical CoreCompetenceVersions

BC310Windows NT / Oracle

BC314Windows NT MSSQL ServerBC317(WindowsNT /UNIX)/DB2BC360UNIX/ OracleBC 362 U N IX/SAP D B

2 daysR/3-TechnicalImplementation andOperationManagement

Technical CoreCompetence

5 days

3 daysDatabase AdministrationORACLE

3 days

Software Logistics

3 daysDatabase AdministrationMS SQL Server

3 daysDatabase AdministrationDB2 UDB

© SAPAG KTMmySAP.comfor Techn. Impl., IT Cons., Sys. IntegrationUH / 7

( SD ) 2 d ay s

( SD ) 2 d ay s

( SD ) 2 d ay s

( SD ) 2 d ay s

( SD ) 1 da y

( SD ) 1 da y

( SD ) 1 da y

( P P) 2 da ys

(SD /PP) 2days

( PP ) 2 da ys

( C O) 2 d ay s

(PP/C O)2days

(S D) 2 d ay s

(SD /PP) 2days

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 v

Course Overview...................... ........................................................... ........................................................... ....... 1

Course Prerequisites - Audience - Duration........................................................ .............................................. 2

Course Objectives ........................................................ .......................................................... ........................... 3Course Contents ........................................................... .......................................................... ........................... 4

Graphical User Interfaces for R/3 ....................................................... ........................................................... ....... 5

Graphical User Interfaces for R/3 ................................................... ........................................................... ....... 6

Frontend Administration ....................................................... ........................................................... ................. 7

GUI Strategy: Overview........................................................ ........................................................... ................. 8SAP GUI: Overview........................................................................ ........................................................... ....... 9

SAP GUI: Installation Options................. ........................................................... ............................................ 10

SAP GUI: Installation Procedures................................ .......................................................... ......................... 11

SAP GUI: Dialog-Free Installation and Maintenance............................................................ ......................... 12

SAP GUI: Accessing the SAP Library......................... .......................................................... ......................... 13

SAP Library: Overriding the Standard Settings .................................................. ............................................ 14

SAPLOGON: Logon and Trace ...................................................... ........................................................... ..... 15

SAPLOGON: Configuration ........................................................... ........................................................... ..... 16

SAPLOGON Configuration Files ................................................... ........................................................... ..... 17

SAP GUI Connection String ........................................................... ........................................................... ..... 18

Logon Groups..................................................... ........................................................... .................................. 19

Logon Load Balancing: Mechanism ......................................................... ...................................................... 20

Logon Load Balancing: Advanced Features ....................................................... ............................................ 21SAP GUI for HTML .................................................... .......................................................... ......................... 22

SAP GUI for Java......................................................... .......................................................... ......................... 23

Frontend in a WAN Environment ................................................... ........................................................... ..... 24

Unit Summary .................................................... ........................................................... .................................. 25

Further Documentation ......................................................... ........................................................... ............... 26

Computer Aided Test Tool................. ........................................................... ...................................................... 27

Computer Aided Test Tool....................... ........................................................... ............................................ 28

CATT: Introduction............................................................... ........................................................... ............... 29

CATT: Uses ....................................................... ........................................................... .................................. 30

CATT: Other Uses ....................................................... .......................................................... ......................... 31

Processes Less Suited for CATT.... ........................................................... ...................................................... 32

CATT: Initial Screen.................................................... .......................................................... ......................... 33CATT: Recording Transactions ...................................................... ........................................................... ..... 34

CATT: Creating a Test Case ........................................................... ........................................................... ..... 35

CATT: Maintaining the Test Case Functions............... .......................................................... ......................... 36

CATT: Maintaining the Function Details.................................................. ...................................................... 37

CATT: Maintaining the Input Values........................................................ ...................................................... 38

Test Case Processing Modes ........................................................... ........................................................... ..... 39

Test Case Logs ................................................... ........................................................... .................................. 40

Variants .................................................... ........................................................... ............................................ 41

Defining Variants ......................................................... .......................................................... ......................... 42

External Variants........................... ........................................................... ...................................................... 43

External Variants: File Format ....................................................... ........................................................... ..... 44

CATT: TIPS....................................................... ........................................................... .................................. 45

Authorization................................................................ .......................................................... ......................... 46User Master Records .................................................... .......................................................... ......................... 47

System Requirements........... ........................................................... ........................................................... ..... 48

Unit Summary .................................................... ........................................................... .................................. 49

Unit Actions ....................................................... ........................................................... .................................. 50

Computer Aided Test Tool: Exercises ...................................................... ...................................................... 51

Computer Aided Test Tool: Solutions............................................. ........................................................... ..... 52

R/3 Security........................................ ........................................................... ...................................................... 54

R/3 Security.................................... ........................................................... ...................................................... 55

Security in Client/Server Architecture ...................................................... ...................................................... 56Central User Administration: Introduction................... .......................................................... ......................... 57

User Administration Before R/3 Release 4.5 ...................................................... ............................................ 58

Central User Administration (1)...................................................... ........................................................... ..... 59

Central User Administration (2)...................................................... ........................................................... ..... 60

What Data Can Be Distributed? ...................................................... ........................................................... ..... 61

Profiles and Activity Groups........................................................... ........................................................... ..... 62

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 vi

Locking Users ................................................... ........................................................... ................................... 63

Setup of Central User Administration (1) .......................................................... ............................................. 64



Global User Manager .................................................. ........................................................... ......................... 67

Initial Setup of Users using Client Copy.................................................. ....................................................... 68

Maintenance and Distribution of User Data ....................................................... ............................................. 69

Using Central User Administration: Transporting Considerations (Option 1)... ............................................. 70Using Central User Administration: Transporting Considerations (Option 2)... ............................................. 71

Transporting Considerations When Central User Administration is Not Used (Option 1) ............................. 72

Transporting Considerations When Central User Administration is Not Used (Option 2) ............................. 73Basis Security Audit....................... .......................................................... ....................................................... 74

Security Audit: Profile Parameters.......... ........................................................... ............................................. 75

Audit Configuration: Selection Criteria ................................................... ....................................................... 76Reading the Security Audit Log...................................................... .......................................................... ...... 77

SAProuter: Overview.................................................. ........................................................... ......................... 78

SAProuter: Implementation................................................... ........................................................... ............... 79

SAProuter: Route Strings ...................................................... ........................................................... ............... 80

SAProuter: Route Permission Table (saprouttab) ........................................................ ................................... 81

SAProuter: Testing Basic Functions with NIPING......................... .......................................................... ...... 82SAProuter: Trace File and Other Options .......................................................... ............................................. 83

SAProuter: Communication Partners and .......................................................... ............................................. 84

Additional Security Measures: SAP GUI Reconnect ................................................... ................................... 85

Additional Security Measures: Authorization Groups ........................................................... ......................... 86Additional Security Measures: Trusted Relationships Between R/3 Systems................................................. 87

Unit Summary ................................................... ........................................................... ................................... 88

Further Documentation ......................................................... ........................................................... ............... 89

Unit Actions ...................................................... ........................................................... ................................... 90

R/3 Security: Exercises ......................................................... ........................................................... ............... 91

R/3 Security: Solutions................................................ ........................................................... ......................... 94

Advanced Background Processing...................................................... .......................................................... .... 101Advanced Background Processing.................................................. .......................................................... .... 102

External Commands: Definition........................ ........................................................... ................................. 103

Running External Commands ......................................................... .......................................................... .... 104

Running External Commands in Dialog................................................... ..................................................... 105

Running External Commands in the Background ........................................................ ................................. 106Parallel Processing Using Asynchronous RFC .................................................. ........................................... 107RFC Groups: Definition ........................................................ ........................................................... ............. 108

Background Scheduling: Standard vs. API ........................................................ ........................................... 109

Using the API in an ABAP Program............................................... .......................................................... .... 110

Open Interfaces ........................................................... ........................................................... ....................... 111

XMI: Logging External Access....................................................... .......................................................... .... 112Monitoring External Interfaces ....................................................... .......................................................... .... 113

Maintaining Background Jobs: XBP Interface............ ........................................................... ....................... 114

Authorizations for Background Processing................. ........................................................... ....................... 115

Authorization Objects (1)...................................................... ........................................................... ............. 116

Authorization Objects (2)...................................................... ........................................................... ............. 117

Checking Background Jobs................................................... ........................................................... ............. 118

Background Load Balancing........................................................... .......................................................... .... 119Unit Summary ................................................... ........................................................... ................................. 120

Further Documentation ......................................................... ........................................................... ............. 121

Unit Actions ...................................................... ........................................................... ................................. 122

Advanced Background Processing: Exercises.......................................... ..................................................... 123

Advanced Background Processing: Solutions.................................................... ........................................... 124

Output Management................. ........................................................... .......................................................... .... 125

Output Management............. ........................................................... .......................................................... .... 126

R/3 Spool System Review.............. .......................................................... ..................................................... 127

Spool Administration: Extended and Full Menus ........................................................ ................................. 128

Availability of Output Devices: Device Pools ................................................... ........................................... 129

Definition of Device Pools .................................................... ........................................................... ............. 130

Spool Server Load Balancing...................................... ........................................................... ....................... 131

Spool Server Load Balancing: Remote Printers ........................................................... ................................. 132

Status Query for Print Requests ...................................................... .......................................................... .... 133

Monitoring Critical Printers Using CCMS.................. ........................................................... ....................... 134

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 vii

Non-Standard Printers in R/3 .......................................................... .......................................................... .... 135

Copying a Device Type........ ........................................................... .......................................................... .... 136

Copying and Assigning a Character Set................................................... ..................................................... 137

Modifying Format Actions............. .......................................................... ..................................................... 138

Modifying Print Controls ...................................................... ........................................................... ............. 139

Non-Standard Device: Problem Analysis (1) ..................................................... ........................................... 140

Non-Standard Device: Problem Analysis (2) ..................................................... ........................................... 141

SAPconnect....................................................... ........................................................... ................................. 142SAPconnect: R/3 to External Systems ..................................................... ..................................................... 143

Example: Sending a FAX between R/3 Systems....................................................................................... .... 144

Connecting Components for SAPconnect .......................................................... ........................................... 145SAPconnect: R/3-R/3 Communication......................................................................... ................................. 146

SAPconnect: Creating a Node Using the Wizard......................................................... ................................. 147

SAPconnect Node: User for RFC connection .................................................... ........................................... 148SAPconnect Node: Address Areas.................................................. .......................................................... .... 149

Address Management............................................................ ........................................................... ............. 150

SAPconnect Status View................................... ........................................................... ................................. 151

Administration of External Transmissions......................................................... ........................................... 152

SAPconnect: Trouble Shooting....................................................... .......................................................... .... 153

Unit Summary ................................................... ........................................................... ................................. 154Unit Actions ...................................................... ........................................................... ................................. 155

Output Management: Exercises................................................................ ..................................................... 156

Output Management: Solutions............... ........................................................... ........................................... 159

CCMS Monitoring Architecture................................................ ........................................................... ............. 167

CCMS Monitoring Architecture............................................ ........................................................... ............. 168Review: The Alert Monitor ................................................... ........................................................... ............. 169

Customizing the Monitor: Thresholds......................... ........................................................... ....................... 170

Attribute Groups................................................ ........................................................... ................................. 171

Working with Attribute Groups ...................................................... .......................................................... .... 172

Methods.......................................... .......................................................... ..................................................... 173

Data Collection Method ........................................................ ........................................................... ............. 174Auto-Reaction Method.......................................................... ........................................................... ............. 175

Defining Auto-Reaction Methods: Example ...................................................... ........................................... 176

Analysis Method ......................................................... ........................................................... ....................... 177

Defining Analysis Methods: Example................................................................ ........................................... 178

Customizing the Monitor: Assigning Methods .................................................. ........................................... 179MTE Classes ..................................................... ........................................................... ................................. 180MTE Classes: Assigning Properties ......................................................... ..................................................... 181

MTE Classes: Assigning Methods .................................................. .......................................................... .... 182

Working with the Alert Monitor ..................................................... .......................................................... .... 183

Defining Monitors ....................................................... ........................................................... ....................... 184

Static Monitor: Example ....................................................... ........................................................... ............. 185Rule-Based MTE Selection................................................... ........................................................... ............. 186

Rule-Based Monitor: Example........................................................ .......................................................... .... 187

Global Monitor Settings: Properties Variants .................................................... ........................................... 188

Working with Properties Variants............................................................ ..................................................... 189

Monitor Variants ......................................................... ........................................................... ....................... 190

Multi System Monitoring ...................................................... ........................................................... ............. 191

Transport of Properties Variants ..................................................... .......................................................... .... 192Troubleshooting: Background Processing................................................ ..................................................... 193

Troubleshooting: Output Management......................................................................... ................................. 194

Troubleshooting: SAPconnect..................................... ........................................................... ....................... 195

Troubleshooting: CCMS Self Monitoring......... ........................................................... ................................. 196

Unit Summary ................................................... ........................................................... ................................. 197Unit Actions ...................................................... ........................................................... ................................. 198

CCMS Monitoring Architecture: Exercises ....................................................... ........................................... 199

CCMS Monitoring Architecture: Solutions.............................................. ..................................................... 202

Conclusion................................................................................. ........................................................... ............. 209

Conclusion............................................................................. ........................................................... ............. 210

Further Documentation ......................................................... ........................................................... ............. 211

Frequently Used Menu Paths .......................................................... .......................................................... .... 212

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 1

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 2

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 3

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 4

© SAP AG 1999

Unit 4

Unit 5

Unit 6

Unit 1

Unit 2

Unit 3

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 5

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 6

© SAP AG 1999

At the end of this unit, you will be able to:

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 7

© SAP AG 1999

Requirement analysis:Compare actual and the required

infrastructure

SAP R/3 frontend requirements→ SAP Note 26417

End user requirements

Administrator requirements:- Ease of installation- Ease of distribution

GUI technology: Windows, Java, and HTML

GUI components: Such as standard, networkgraphics, EXCEL List Viewer, and download

When considering your frontend requirements, you must consider the PCs from the administration

and from the user perspective.

For the end user, it is important to have all the components on the desktop that are needed for day-to-

day work with R/3.

For the system administrator, frontend computer administration must be organized so that it remains

as simple as possible, especially when the system includes a large number of frontends. As the

system administrator, you must also consider:

• Frontend PCs are not all technically the same throughout the company. Also, users do not all

need the same GUI components installed.

• For an existing desktop infrastructure, which includes PCs, workstations, networks, and printers,

you should assess your overall end user requirements and your R/3 frontend software

requirements.

• Using the results of this requirements assessment, construct a matrix summarizing and grouping

together the different user requirements relating to GUI technology and the GUI components.

• By standardizing the GUI technology or GUI components for the different groups, the system

administrator can then design suitable scenarios for distributing and maintaining the frontend

software.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 8

© SAP AG 1999

There are three categories of R/3 frontends:

, which offers various frontend components and interfaces. SAP GUI can

be installed as a frontend server or in a local installation. Since R/3 Release 4.5B, SAP GUI is also

available for Windows Terminal Server (WTS). For more information, see SAP Note 138869.

, which is available –as of R/3 Release 4.6B – as a local installation for all

Java-supported platforms.

, which is a browser-based frontend of SAP´s Internet Transaction Server

(ITS). Apart from the browser, no local installation on the frontend computer is required.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 9

© SAP AG 1999

In the following section, we will focus on the SAP GUI and its components:

• Installation options for the SAP GUI and distribution of the applicable frontend files

• Access to the SAP Library from Frontend PCs

• Configuration of SAPLOGON and SAPLGPAD

- SAPLOGON and SAPLGPAD use the same configuration files. The only difference is that

SAPLGPAD does not provide push buttons to change its configuration files.

• Logon load balancing

Note: This unit discusses SAPLOGON only.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 10

© SAP AG 1999

•

•

•

•

•

•

Option 1: Local installation from CD

This option is used when only a few PC frontends have to be installed. Apart from OS configuration

files, such as hosts and services, the system administrator must adapt and distribute at least thefollowing configuration files:

• saplogon.ini (access list needed only for the SAPLOGON program)

• sapmsg.ini (list of message servers needed only for the SAPLOGON program)

• saproute.ini (list of routers needed only for the SAPLOGON program)

• sapdoccd.ini (access list to online documentation needed only to override standard settings)

Option 2: Installation from the installation server

(a)

This option is mostly used for PCs in a LAN. SAP configuration files can reside on a central server

and updated as required by the system administrator. The installation process and the update of theSAP GUI frontend software can be performed automatically, by means of logon scripts.

(b)

This option can be used for all frontend computers in a LAN or for notebooks that are sometimes

connected to a LAN. The advantage of this installation option is that the network traffic between the

installation server and the frontend is minimized, therefore more free local hard disk space is

required. The services file and SAPLOGON configuration files must be distributed as shown in

Option 1.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 11

© SAP AG 1999

To install the SAP GUI, you can proceed as follows:

• Test a local SAP GUI installation from the installation CD to a sample PC. Create templates for

the SAP GUI configuration files and the services file.

• Install an installation server using program SETUP.EXE.

• Define installation packages for different user groups using program SAPADMIN.EXE.

• If you use Windows NT as one of your frontend platforms, configure the NetInstall Service and

the Service Installation Service (SIS). This ensures that the Windows NT frontend users do not

require local administration authorization to perform an automated or manual installation.

• Log on to a PC where the frontend components are to be installed. Use a user account –without

local administrator rights– and start the installation using program NETSETUP.EXE from the

installation server.

• If installation is successful, distribute the packages needed, using logon scripts of the user PCs.

Include the distribution of SAPLOGON configuration files, and adapt the services file if

necessary.

The SAP GUI installation procedure is described in detail in the guide (Material number 51006773).

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 12

© SAP AG 1999

•

•

The installation program NETSETUP calls program SAPSETUP and enables a dialog-free

installation.

Installation packages can be distributed with the MS Systems Management Server (SMS) or using

logon scripts.

Before starting NETSETUP on the end users PC, you must ensure:

• Sufficient free disk space is available

• The correct network authorizations have been granted

• SIS is installed the frontend PC is using Windows NT

When installing the frontend components using logon scripts there are several options you can use. If

no user interaction is desired during installation process, use the IntelliMode option of the

NETSETUP program. This option checks if there is already an up-to-date SAP GUI installation prior

to the actual installation. If there is an up-to-date SAP GUI already installed, the NETSETUP

program terminates without any action.

A detailed description of all NETSETUP parameters can be found in the guide

(Material number 51006773).

If there are any errors during the installation, check the log file .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 13

© SAP AG 1999

There are three methods to access the from frontend computers:

• converts documents to standard HTML format. It can be installed on all

frontend platforms and is displayed in the standard Web browser. PlainHtmlHttp can be used

with Windows 95 or 98, Windows NT 4.0, or when a Web server is available, such as for

Intranet.

• converts documents to standard HTML format. It can be installed on all frontend

platforms and is accessed using a file server, where the HTML documents are contained in a

directory, made available through a share and displayed in a standard Web browser.

PlainHtmlFile can be used with Windows 95 or 98, Windows NT 4.0, or when no Web server is

available.

• converts documents to compressed HTML format. It can be used only under

Windows 95 or 98, and Windows NT 4.0, and is displayed in an HTML browser. The amount of

memory required for the file server files when using HtmlHelpFile is 90% less than the memoryrequired for the uncompressed HTML format. The prerequisite for this type of online Help is a

Web browser installed on the frontend before the installation of the frontend software, since the

browser contains the HTML controls.

Once the files are downloaded on the file server and the language-specific directories are installed, a

number of profile parameters must be maintained, according to the R/3 Installation Guide.

For details of the installation, see the guide (Material

number 51007197).

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 14

© SAP AG 1999

To override standard settings for the Help type and the location of the Help files, change the SAP

GUI configuration file sapdoccd.ini on the frontend PC.

To do this, use the sections [HTMLHELP] and [SystemId-<SID>], for example:

[HtmlHelp]

HelpType=PlainHtmlHttp

PlainHtmlHttpServer=p99999.sap-ag.de:1080

PlainHtmlHttpPath-DE=PlainHtml/46A/DE

PlainHtmlHttpPath=PlainHtml/46A/EN

[SystemId-B20]

HelpType=HtmlHelpFile

HtmlHelpFilePath-DE=\\p16381\htmlhelp\46a\DE

HtmlHelpFilePath=\\p16381\htmlhelp\46a\EN

Error handling:

• For every access to the SAP Library, a log is written into the Windows directory in file

sapdoccd.log. This file contains relevant information about sapdoccd.ini and any problems with

the browser version.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 15

© SAP AG 1999

Displayentries

Read

Create SAP GUIconnection string

Write trace filesif activated

The program SAPLOGON.EXE is located in directory [drive letter]:\<target directory>\Sapgui, as

defined during the SAP GUI frontend software installation. To connect to R/3, SAPLOGON starts

the program SAPGUI.EXE, which starts program FRONT.EXE. To locate this file, click the upperleft corner of SAPLOGON and choose → .

When program SAPLOGON.EXE is started, the SAP GUI configuration files saplogon.ini,

sapmsg.ini, and saproute.ini are read. To locate these files, click the upper left corner of

SAPLOGON and choose . The file saplogon.ini is initially empty and contains a list of R/3

Systems and logon parameters selected by the user. This information is used for creating the SAP

GUI connection string at logon.

To prevent the saplogon.ini entries from being changed, set this file to for all frontend

computers. To switch off the edit function of SAPLOGON, click in the upper left corner of

SAPLOGON and choose → .

To trace the SAP GUI logon activities, click the upper left corner of SAPLOGON and choose → . The trace files are located in the work directory and their

names are:

DEV_xxxx.TDW (ASCII) and DEV_xxxx.LOG (binary)

To configure the edit and trace functions in the file saplogon.ini, set the following parameters:

= 1

= 0

= 3

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 16

© SAP AG 1999

sapmsg.ini saproute.ini

Read

Write

Read

Read Sort entriesand write

User selects messageserver or adds new message server in

SAPLOGON dialog box

User selects saprouterentry or adds new one

in SAPLOGON dialog box

The file saplogon.ini is maintained and sorted every time a new entry for an R/3 System is created or

changed using the button. If you have to change saplogon.ini manually (for example, if you

want to merge two different versions), see SAP Notes 99435 and 145385.

There are two more ini files that are maintained implicitly when editing in SAPLOGON:

• contains a list of message servers for R/3 Systems and logical service names. It is

read whenever a logon group is selected from within SAPLOGON.

• contains a list of saprouters that can be selected in SAPLOGON.

The frontend file services (in Windows NT under c:\windowsNT\system32\drivers\etc) cannot be

edited by SAPLOGON but entries are needed to connect to the R/3 Systems. Entries must be added

manually using an ASCII text editor. R/3-relevant entries for message servers are:

• sapms<System ID> <service number>/tcp

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 17

© SAP AG 1999

The SAPLOGON configuration files can be located in different locations independently from each

other.

For server installations, at least the files sapmsg.ini and saproute.ini should be placed in the central

sapgui directory. These files should only be maintained by the system administrator.

The saplogon.ini file can also be located centrally. However, you should ensure the file is

for the end users.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 18

© SAP AG 1999

Group logonsapgui.exe /M/tcc1/S/sapmsDEV/G/Public(sapmsDEV as defined in SERVICES)sapgui.exe /M/tcc1/S/3600/G/Public

Server logonsapgui.exe /H/tcc3/S/sapdp01(sapdp01 as defined in SERVICES)sapgui.exe /H/oss001/S/3201

Group logonMessage server on host

System number 01Service name sapmsDEV=3600Logon group

Server logonHost

Instance number

Service name sapdp01=3201

For users working only with one R/3 System, there only needs to be one SAP GUI icon on the user’s

PC desktop. Therefore, the system administrator must ensure that the correct SAP GUI connection

string is used.

When logging on to an R/3 System, the connection string must contain the access path and the

program SAPGUI.EXE. The connection string must be constructed in the same sequence in which

the connection progresses through all instances (saprouter instances, message server instance, or R/3

instance). The connection string must specify the following:

• For a

/M/<machine where message server is running>/S/<service number used by the message

server>/G/<case sensitive name of logon group to connect to>

• When using logical names for the machine where a message server is running, define the names

in the sapmsg.ini file of the frontend server. R/3 documentation often refers to system numbers

instead of service numbers. A system number 00 is the same as an entry in the services filesapms<R/3 System ID>=3600/tcp.

• For a

/H/<application server where R/3 instance is running>/S/<service number used by the

dispatcher>

• R/3 documentation often refers to instance numbers instead of service numbers. An instance

number 01 is the same as an entry in the services file sapdp01=3201/tcp.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 19

© SAP AG 1999

The logon group a user logs on to is determined at the frontend, it is not specified in an R/3 table.

Therefore, the system administrator must deliver the correct SAP GUI frontend configuration to

every R/3 user’s desktop environment.

When you create the SAP GUI frontend configuration, you can use:

• The SAPLOGON configuration files, or

• A shortcut, which consists of the SAP GUI program and the applicable connection string

Logon groups improve system performance because users are equally distributed across the available

application servers assigned to their group, based on the server with the best response time and

fewest users.

Note: R/3 users are NOT assigned to logon groups (it is the frontend PCs that are assigned to a logon

group). However, you can exclude R/3 users from specific R/3 instances through the user exit

SUSR0001, right after logon. However, this is an enhancement, which is not part of the SAPstandard. See also SAP Note 106388.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 20

© SAP AG 1999

3

2

1

A

B

C

3

2

1

B

A

C

At system startup, program SAPMSSY6 executes RSRZLLG0, which is a cyclical background

program for determining logon priority list. Program RSRZLLG0 then runs every 5 minutes and

after every fourth logon. Note: RFC users are checked after 5 minutes only, after the fourthlogon.

Program RSRZLLG0 reads performance data (average dialog response time, number of users) for all

instances and calculates weights ( and ) based on this data.

Based on the calculation, the higher the answer_weight, the better the response time (the same

applies for the user_weight).

An overall instance weight (instance_weight = (answer_weight * 5) + user_weight) is then calculated

for all instances.

The favorite server for a particular logon group is the server with the highest for

that group.

To display information for favorite logon servers, call Transaction and choose →

→ .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 21

© SAP AG 1999

To check whether users are evenly distributed across servers, access the . To do this,

call Transaction and choose → ( ).

To view load distribution across instances and configured logon groups, call Transaction and

choose →

To create logon groups, call Transaction and choose .

• In the field , enter the logon/server group to be assigned to a number of instances.

• In the field , specify the (numeric) IP address of the application server if the

application host belonging to the instance is addressed from the frontend using a different IP

address than that used for communication within the application host. This may be the case if,

for example, communication from application host to application host uses a different network

than the one used for communication from the frontend to the application host (multi-network

adapter card).

• See also the documentation on (Material Number 51006371)

and (Material Number 51006373).

When creating logon groups, you should configure load limits (fields and ). It is

better to let the system load balancing algorithm handle this. You can limit the number of users on a

certain R/3 instance by changing the R/3 instance profile parameter .

Logon groups can be changed dynamically during operation. A user currently logged on is not

affected by this. The change only takes effect the next time that user logs on.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 22

© SAP AG 1999

(28k or 56k modem will suffice)

The SAP GUI for HTML is mostly used for standard application transactions. A complete list of

standard transactions is available in SAPNet under →

The SAP GUI for HTML is based on Internet Transaction Server (ITS) technology. If you use Unix

application servers, at least one extra Windows NT server is required to run the ITS. In a Windows

NT environment, this extra server is recommended. The ITS extends the three-tier client/server

structure of the R/3 System to the Internet.

The R/3 System through SAP GUI can be used simultaneously with the ITS without any problems.

For more information about the ITS, see and the (Material number 51007160).

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 23

© SAP AG 1999

The SAP GUI for Java will be available as of R/3 Release 4.6B.

The SAP GUI for Java is a Java application that runs in a virtual machine (VM).

For detailed information about the hardware requirements and availability of the SAP GUI for Java,

see SAP Note 146505.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 24

© SAP AG 1999

When using SAP GUI Release 4.6 in a WAN environment, there are different methods to decrease

the network load. From SAPLogon, choose → →

For further details, see SAP Note 161053.

Local SAP GUI installations do not require loading program files over the network.

If you use the SAP Library, it must be accessed from a local CD drive or hard disk.

You should use the SAProuter for frontend access as it handles connection attempts to and broken

connections from the application server.

When developing Internet Application Components (IAC) for the Internet or intranet, developers

must consider the number of users accessing their HTML pages using slow WAN connections. ITS

enables you to have a number of different themes for these users, for example, with fewer graphical

elements and without sound effects. End users can also change settings on their browsers to keep a

longer history, and restrict the use of sounds and videos.

See also the documentation on (Material Number 51006371) and

(Material Number 51006373).

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 25

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 26

© SAP AG 1999

→ →

→

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 27

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 28

© SAP AG 1999


8/11/2019 BC305_EN_46B


(C) SAP AG BC305 29

© SAP AG 1999

The Computer Aided Test Tool (CATT) is part of the ABAP Workbench, and can be used for

administrative purposes.

You can use the CATT to run a stress test on your system. To improve the accuracy of the test, you

can build into the CATT.

After an R/3 upgrade, use the CATT to test application functions before your end users test the

system.

The CATT enables you to load data that cannot be loaded using .

For training purposes, the CATT can be used by:

• End users to see how transactions are entered, and to reinforce their learning by reviewing

transactions in foreground

• System administrators to load master data for training, such as customer master records and

material masters

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 30

© SAP AG 1999

are most useful for acceptance tests. are descriptions of tests,

which a tester must perform manually on the system.

are performed by the R/3 System without user dialog, and are most useful for

function tests. The result of an automatic test case are written to a detailed log. can considerably reduce the overall testing process.

Both manual and automatic test cases can test individual transactions or whole business transactions.

Test cases are constructed modularly, to minimize the creation and maintenance effort for business

transactions. Creating test modules is greatly simplified by the CATT recording function.

Test modules are test cases for transactions, and test procedures are test cases for processes.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 31

© SAP AG 1999

The success of automated testing depends on the quality of the test cases. Therefore, it is important

to plan the test steps and gather the information needed before creating the test cases.

When you plan your test, consider the following:

• What is to be tested?

• Which process chains are to be modeled with CATT?

• Which application areas are involved?

• Which test cases are needed?

• How do the test cases have to be structured so that they can be reused?

• Do the database changes have to be checked?

• Do the error messages have to be checked?

When you plan your test, you must also consider the following :

• Are the tests restricted by language-dependencies?

• Is the object country-specific?

• Does the test have to be performed in a specific sequence, or certain time of day?

• Do you have to consider the system environment, such as tablespaces or backups?

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 32

© SAP AG 1999

With CATT, you should not run a test procedure for the following:

• - it is easier to run the list or display than to create a test case

• is also easier to choose the help as opposed to using test case

• With these transaction contain the statement LEAVE TO TRANSACTION.

You cannot use the test case for transactions that contain the statement LEAVE TO

TRANSACTION.

• - it is easier for a user to enter a menu path or execute a transaction than it is to put

in a test case.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 33

© SAP AG 1999

To display the initial CATT screen, choose → → →

→ (or call Transaction ).

All customer created test cases begin with the letter or . When you create a test procedure or

module, give it a unique name of up to 30 characters.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 34

© SAP AG 1999

To create a test case, from the initial screen of CATT, choose → (or

press Ctrl + F1). In the dialog box displayed, enter the transaction code and choose .

Once you start recording, every keystroke is recorded in the CATT. Therefore, if you make a mistake

you should re-record your transaction.

After you save the transaction, choose in the dialog box displayed.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 35

© SAP AG 1999

When the recording is finished, you are prompted to your test case:

• Enter the description in the field

• Enter the name of person responsible for the test in the field

• Enter the and

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 36

© SAP AG 1999

To maintain a test case, choose from the initial CATT screen.

When you record your test case, the system records all the values that you specify.

The function on the above screen is TCD (test transaction).

Other possible functions you can specify are:

• REF: Refer to test case FUN: Use function module

• TXT: Enter comment CHEERR: Check system message

• CHETAB: Check table contents CHEVAR: Check variable contents

• SETTAB: Set customizing table RESTAB: Reset table

• DO n... (EXIT)... ENDDO: Loops

• EXIT: Conditional termination IF... ENDIF conditions: Use of conditions

• SETVAR: Assign values to variables and parameters

To learn more about the advanced features of CATT, enroll in course CA610.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 37

© SAP AG 1999

The screen displays the following entries, which you made during the recording of

your test case:

•

•

• (BDC_OKCODE)

•

If you made a mistake while recording, you must know the function details (program, screen

number, code, and field values) and update the mistake. Therefore, it is easier to re-record the

transaction.

To see the fields you entered during the recording, double-click the first program name or choose

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 38

© SAP AG 1999

To define your own parameters, enter an “&” in the and delete the rest of the

entry. When you execute your test case, you can then enter values to the the field.

If you define a new field, but enter no value, the system will default to the original value when the

test case was recorded.

If you do not want to change your original value that you entered during recording, do not change the

input field.

Note: You can only change the field contents that are active. That is, you can only change the fields

that you entered during recording.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 39

© SAP AG 1999

The processing mode only affects the execution of transactions in the test case where the function is

TCD or dialog function modules.

• The test case runs in dialog. You can correct field entries or influence the test by entering

BDC_OK codes. Display the next screen by choosing .

• The test case runs in the background. If your data is not valid, the processing is not interrupted:

An error message is written to the log file, and the processing continues with the next record. For

example, if you are processing 100 records and the 50th record has invalid data, an error

message is written to the log file, and the processing continues with the 51st record.

• The test case runs in the background until the first error or termination. It then switches to dialog

processing. Once it is in dialog, you can change any incorrect entries. When you confirm your

entries, the test case continues in the background until the next error.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 40

© SAP AG 1999

You can specify the log type for a test case when it is executed. There are two types of logs:

•

Contains all the test case function data. If an error occurs, a long log is automatically created,

beginning from the module where the error occurred, even if you chose the option in the

initial screen.

•

Contains only the information about the functions called by the test case and the parameter

contents.

The log files also contain the run times.

Note: If the job RSCATDEL is scheduled, logs are deleted after 14 days. To keep a log longer in the

system, change the expiry date manually. To do this, choose → in the log.

Enter an expiry date in the dialog box is displayed.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 41

© SAP AG 1999

you can create test case variants, you must have already created the test case import

parameters.

You can maintain variants in R/3 or locally on your hard-drive (explained later in this unit).

To enter variants in R/3, from the main CATT screen (Transaction ), enter the test case that

you want to add variants for. Then choose → →

You can decide which variant to use when you call a test case.

Use variants to broaden the range of tests.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 42

© SAP AG 1999

You can enter the test case values (variants) at runtime in import parameters that can, for example,

be put in transaction input fields. Thus making the use of test cases more flexible.

You can store sets of values, which you want to give to the import parameters at runtime, in variants.

You then only need to specify the variant name at the test case runtime.

When a test case runs, the system checks each import parameter to see if a value has been defined for

it in a variant.

If it has been defined, this value is given to the parameter at runtime.

If it has not been defined, the parameter default value is used. If there the default value was not

specified at the time of recording, the initial value is used.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 43

© SAP AG 1999

With the CATT, you can create variants for the test case import parameters in an external table

calculation program, such as Microsoft EXCEL. The variants that you create in the external file can

be uploaded during the execution of the test case.

The external data is stored in a text file, with the elements separated by tabs.

If you did not create any variants for the test case, you can create a text file containing all test case

parameters and their short texts and default values. To do this, choose → → . The dialog box is displayed.

The system default value for the external file name is . You can change the path

and file name but the extension.

Once you have edited the file (for example, in EXCEL), save the file as a with tab column

separators. Close the file in the external program.

Note: The file be closed to be imported into the R/3 System.

To import the edited file, you can either:

• Choose → → , from the test case , or

• During execution, from the section select choose , and enter

the path and file name.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 44

© SAP AG 1999

When you export a text file, it appears as follows:

• Column [Variant ID] Contains the variant ID

• Column [Variant text] Contains a short text about the variant

• Column &<parameter> Contains the test case import parameter.

The first row contains the column headers.

The second row contains the field name displayed in R/3.

The third row contains the default value.

The fourth row contains a comment that states changes to the default value are not considered.

You can define the new data in the fifth row and on.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 45

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 46

© SAP AG 1999

ABAP Workbench

(S_DEVELOP)

Development Class Create, Delete, Change Object

DEVCLASS

Not used for CATTP_GROUP

OBJTYPE

OBJNAME

ACTVT

SCAT Object Type

Test Case Name

01 Create or generate

02 Change

03 Display

06 Delete

07 Activate, generate

16 Execute

70 Administer

Authorization object S_DEVELOP has five fields, for which the following settings are checked:

• Development class (DEVCLASS). This authorization object is for the Change and Transport

Management System, and is checked when you create the test case, not at runtime.

• Authorization group ABAP program (P_GROUP). This authorization object is not checked.

• Development object type (OBJTYPE). This authorization object is checked for value “SCAT”

when this transaction is executed.

• Object name (OBJNAME). The test case name is checked.

• Activity (ACTVT). You can assign authorizations to individual test cases or groups of test cases.

The following values are checked:

- 01 Create or generate

- 02 Change

- 03 Display

- 06 Delete

- 07 Activate, generate

- 16 Execute

- 70 Administer

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 47

© SAP AG 1999

To activate the test status flag, you need the following authorizations:

• ABAP Development Workbench object (S_DEVELOP)

• Development class ID SCAT

• Activity 70 (Administer)

If the test status flag is activated for a user, the test status is set when the CATT processes start.

The test status is language-dependent and is stored depending on the process variant started.

A history of test status allocation is also kept.

The test status should only be set for final test cases.

Transports of the CATT processes are generally compiled in other systems because of the test status.

If the termination flag is set, the test case terminates upon the occurrence of the first error. Otherwiseit continues despite errors. If the termination flag is not set, the current TCD or REF is aborted.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 48

© SAP AG 1999

You can create client-independent test cases in any client, but you can only run them in one client.

This must not be a productive client, as settings are changed and test master data is

created, such as documents, which can lead to errors in the production system.

To allow test cases to run in a client, the client table T000 must be maintained in system

administration. To do this, choose → → →

.

In the view, set the flag from the section.

If the flag is set in table T000, correction windows may appear

during the customizing transactions. Do set this flag when creating test cases, otherwise the test

case procedure screen sequence for this customizing transaction may no longer be correct.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 49

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 50

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 51

1.1 Record a test case with the following specifications:

: ZBC305

: SU01.: Create user.

For the user ID, specify the following:

: CATT

: Mr. or Ms.

: CATT

: init

: Test Add User

: BC-CCM-USR

: $TMP

2.1 Define the following parameters in test case ZBC305:

User name (initial screen of Transaction SU01)

Last name (second screen of Transaction SU01)

Hints: Use "&" as the parameter names.

3.1 Execute test case ZBC305 with the following parameter values:

: CATTCOPY : CATTCOPY

Specify as the processing mode.

3.2 Check if the user CATTCOPY has been created.

4.1 Export the default parameters into a frontend file in order to create an externalvariant for your test case. Use the default values for the path and file name.Remember path and file name for the next step of the exercise.

4.2 Open the file using Notepad.

Note: You can start Notepad from within R/3 using the report ZEDIT.

4.3 Enter the following external variant:

AUTOCATT as the user ID

AUTOCATT as the last name

Note: Make your entries in the fifth (5th) line.

4.4 Execute the test case using the external variant from file.

4.5 Now import the file to R/3 to create a non-external variant.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 52

1.1 To record a test case, call Transaction and enter test case . Donot choose .

Choose → . Enter Transaction , andchoose .

The system runs Transaction .

Enter the user name and choose .

Enter the user’s title and the last name .

Select the tab, enter as the initial password, and repeat the

password, then choose .

In the dialog box displayed, select .

A message is displayed stating that the recording has ended.

Enter the test case title .In the field , enter .

Save the test case.

In the field , enter .

Choose to save the attributes.

To save the test case functions, go back.

2.1 To define parameters for a test case, call Transaction .

Enter the test case name .Select and choose

Double-click on TCD.

Then double-click on program SAPLSUU5 screen 0050. (first appearance ofthis program)

The first screen of Transaction is displayed. (If you backed out, enterthe procedure name again and double-click on TCD.)

Double-click on the user name field. In the field , enter an "&",and choose .

Choose and double-click the last name. In the field , enter an "&" and choose .

Go back until the folder appears, and choose .

3.1 From the main CATT screen, enter test case name and choose

(F8).

In the fields, enter for the and .

Note: If you do not enter a new value, the default values are used.

Under , select , and choose .

3.2 To check if the user has been created, call Transaction enter in the field , and choose .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 53

4.1 To export the default parameters into a frontend file, in the test case, select → → .

Note: The default file name is <the name of your test case>.txt. Do notchange the default values.

Remember path and file name for the next step of the exercise.

Choose . A file containing the parameter structure with short

texts and default values is created.

4.2 To open the file, call Transaction

In the field enter and choose

Choose → and select the file created in exercise 4.1.

4.3 On the fifth (5th) line, enter your external variants:

First, tab twice and enter (for )

Tab again, and enter (for )

and close the file.

4.4 To execute the test case using the external variant from file, from the initialCATT screen, enter the test case name and choose .

In the field , select and choose . Select thefile created in exercise 4.3. and choose . Under , select, and choose .

Note: When you use this method, the file must be imported each time the testcase is executed (file remains only on PC).

4.5 To import the file to R/3, call Transaction .

Enter the test case name and in the field , select .

Choose Then choose → →

Choose .

In the dialog box displayed, select the file created in exercise 4.3. and choose .

Select

Choose

Save your settings.

Go back.

To display the new variant, choose → → . Enter adescription. Save again.

Note: When you execute the test case using a non-external variant, you mustcall Transaction , enter the test case name and choose . In thefield , select and choose the already importedvariant.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 54

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 55

© SAP AG 1999


8/11/2019 BC305_EN_46B


(C) SAP AG BC305 56

© SAP AG 1999

•

•

•

•

•

•

•

•

•

•

•

Securing all the layers of the R/3 client-server architecture means ensuring confidentiality, integrity,

and access control at all times.

Confidentiality means that only authorized users have access to read or process R/3 data. Access for

non-authorized users is prohibited.

To ensure security, SAP has implemented the R/3 authorization concept, which is the security

mechanism inside R/3.

There are other areas you must consider, outside of the R/3 System, to ensure the security of all

components of your R/3 installation:

•

Do not allow users to sign on to the operating system. If they need to access a file, allow them

access to Transaction (this is the display access of the SAP directories).

• Change the default password for the database user and limit who can use this user ID.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 57

© SAP AG 1999

The Central User Administration is based on ALE technology and is used to distribute user master

records between systems.Note:You do not have to have a deep understanding of ALE in order to be

able to configure the Central User Administration. Therefore, this unit only describes theconfiguration activities, it does not cover detailed information about ALE.

With Central User Administration:

• The administration of a entire system landscape can be performed from one single central

system.

• You can display an overview of all user data in the entire system landscape.

• All the user data is stored in the standard R/3 tables (USR*), which contain the user master

record data.

You should use Central User Administration if:

• You have a complex system landscape with several clients in different systems

• The same user works in more than one system

• The same user ID should represent the same individual in all systems

• You want to synchronize the user data in all your systems easily

The setup of the Central User Administration consists of the basic ALE customizing and the

configuration of the fields of the user master records to be distributed.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 58

© SAP AG 1999

The procedure before R/3 Release 4.5 for maintaining users is:

• To log on to each client and perform the maintenance, or

• To initially maintain users in one client and copy all users to other clients or systems using the

client copy tool. This client copy cannot copy user master records selectively.

In the example above, the administrator would have to log on to six different clients to make an

update to the user master record. That is, if the administrator wanted to add a profile that allows a

report to be viewed in all six clients, the profile would have to be added to six different user master

records in six different clients.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 59

© SAP AG 1999

PRDCLNT100PRDCLNT200PRDCLNT300DEVCLNT100DEVCLNT200QASCLNT100

In this section, the term “central system” refers to the system where user master data is maintained.

• In this context, a central system is an R/3 System that keeps and controls user master data for an

entire system landscape.

• Outside of this context, a central system is usually a server running both a central R/3 instance

and a database.

In this section, the term “local system” refers to the system receiving data from the central system.

In this example, Central User Administration is performed in PRD system, client 300. The user

master records are distributed to the local systems using RFC connections. No local maintenance of

user master data is required.

ALE uses logical systems to identify clients in a multi-system landscapes. Logical systems are

defined in ALE Customizing and then assigned to a single client.

The definition of all logical systems in an ALE environment must exist in all participating R/3

Systems. This can be achieved by local maintenance or by using Customizing transport requests.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 60

© SAP AG 1999

With Central User Administration, parts of user master records be maintained locally. These

changes can then be redistributed back to the central system, which in turn redistributes the changed

records to the other local systems.

If you maintain parts of the user master records locally and want the changes redistributed to the

central system, RFC connections must exist from the local system to the central system.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 61

© SAP AG 1999

With Central User Administration, the following data can be distributed:

• User master data (for example address, logon data, defaults, parameters)

• Function assignment

- Profiles (system dependent)

- Activity groups (system dependent)

- Initial password

In principle, you can maintain all data in the central system for all systems.

If you do not want to maintain all data centrally, you can maintain the basic data (such as user master

records and passwords) in the central system, and let local administrators maintain the remaining

data (such as activity groups and profiles). The same activity groups and profiles should not be equal

in all systems. For example, the production system will have stricter profiles than in the developmentsystem.

To define what data will be distributed, set the attributes for each field.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 62

© SAP AG 1999

The assignment and maintenance of profiles and activity groups is very important.

Because their assignment is system-dependent, SAP recommends maintaining the assignments

centrally. With Central User Administration, you can assign the profiles as well as the system.

The advantage of using Central User Administration for assigning profiles and activity groups, is that

you do not have to logon on to each system to define the system-dependent assignments, you can do

it all in from one system.

The maintenance of profiles and activity groups are always performed on a local system.

Remember: A user might have different activity groups in different systems.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 63

© SAP AG 1999

Lock caused by incorrect logon x optional

Local administrator lock x optional

Global administrator lock optional x

With Central User Administration, you can:

• Handle locks globally.

• Specify whether users may be locally or globally locked and unlocked.

• Select option Everywhere for local or global unlocking.

• Specify where a user can be unlocked following an incorrect logon.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 64

© SAP AG 1999

DEVCLNT201QASCLNT202

In the Implementation Guide (Transaction ), choose →

→ → → . Choose →

Always ensure that assignment is unique. One client must always be assigned to onlyone logical system.

Next you must assign the logical system name to a client. To do this, choose →

→ → → . In the

, enter the name of the logical system you want to assign to the client.

To define RFC destinations choose → → → →

(or call Transaction ).

• The user you specify for logging on to the other system must have the authorization SAP_ALL.

The name for this user should be clearly recognizable. This name will appear under

in the central system.

• RFC connections should be defined in both directions (from the central system to the local

systems, and vice versa)

• : The name of the RFC connection should be identical to the name of the logical system

(target system), for example, PRDCLNT100. The RFC connection name is case-sensitive.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 65

© SAP AG 1999

To set up ALE distribution model, call Transaction and choose . Then

choose → → →

(or call Transaction ).

The distribution model is used to specify which applications communicate with each other in your

distributed systems. The distribution model contains all of your company’s cross-system message

flow information. The distribution model consists of several model views. In each model view, you

can define related message flows. Each model view is maintained in a central system and distributed

from there to the other systems.

For each model view, you can specify a descriptive short text, the validity period of the message

flows in the view, as well as the view maintenance system. When a model view is created, the

system in which the view is created is automatically specified as the maintenance system. If possible,

designate one system as the central maintenance system for all model views.

The names of the model views must be unique in the entire distributed environment within yourcompany. To define the names, choose → → , and enter a name and a short

description.

From same screen (Transaction ), distribute the system landscape be choosing →

→ Then choose → →

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 66

© SAP AG 1999

To set up the field selection, choose → →

→ → →

→ → (Transaction ).

When selecting , you can choose from the following options:

• - Data can only be maintained in the central system and is completely distributed.

• - A default value is maintained in the central system. This value is distributed when a

user is created and is then maintained locally.

• - Data is maintained both centrally and locally. Each time data is changed locally,

the change is redistributed to the central system, and then distributed to the other local systems.

• - Can only be maintained in the local system. Data changes are not distributed to

other systems.

• - Data is maintained both centrally and locally. However, data changes are not

redistributed to other systems.

To transfer users from a new system to the central system run Transaction SCUG. Position on

and choose .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 67

© SAP AG 1999

You can use the Global User Manager (Transaction ) to easily display and maintain users for

all logical systems participating in the ALE distribution model used for the central user

administration.

User data can be distributed immediately or by scheduling a background job using Transaction

.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 68

© SAP AG 1999

The authorization administrator uses the Profile Generator to create user master records,

authorizations, and activity groups in the development system. When new clients or systems are

created, the authorization administrator should work closely with the system administrator to decidewhat needs to be copied.

Note that users, activity groups, and authorizations are client-dependent.

The tool used to copy this data is the client copy. Client copy is not used for maintaining

changes to the data or to just copy a subset of the users of one client:

• To copy user master records, authorizations, authorization profiles and activity groups locally

between clients, use Transaction with the SAP_USER profile.

• To copy user master records, authorizations, authorization profiles and activity groups between

systems, use Transaction with the SAP_USER profile.

When you perform a client transport, all user master records, profiles, and authorizations in the targetsystem that have the same names as the objects to be imported are overwritten. If your target client

contains authorizations that you want to keep, you may need to manually transport authorizations.

You cannot manually transport individual user master records.

Remember, Transactions and must be run from the target client.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 69

© SAP AG 1999

Authorizationadministrator

Profileadministrator

Useradministrator

The SAP standard templates for activity groups enable a “distribution of power” among

administrators:

• SAP_ADM_AU: Authorization administrator (maintains authorizations)

• SAP_ADM_PR: Profile administrator (generates profiles)

• SAP_ADM_US: User administrator (maintains R/3 users)

Activity groups, profiles, and user templates should be generated in the development system (DEV).

The authorization concept is tested in the quality assurance system (QAS). In the production system

(PRD), the user administrator can generate new R/3 users by copying user templates.

An R/3 user with development authorizations can avoid the authorization check by using a modified

or self-generated report. The production system should therefore be configured in such a way as to

prevent any development from being performed there.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 70

© SAP AG 1999

When using Central User Administration you must consider the following transport issues:

• Activity groups must be transported using Transaction → You

can also perform a mass transport of activity groups using transaction → →

• Authorization profiles are normally transported along with the activity groups. After the import,

you need to perform a mass compare for all user master records and activity groups. To do this,

run Transaction choose → Enter the applicable activity

group in the field Choose and start the report

• When exporting activity groups, you can also transport user assignments. However, this should

not be done when using Central User Administration. You should protect the target system from

receiving these user assignments during a transport by inserting the line USER_REL_IMPORT

with the value NO in the customizing table PRGN_CUST.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 71

© SAP AG 1999

With Central User Administration you can also consider the following:



• You do not have to transport authorization profiles, but instead regenerate them from the activity

groups in the target system. To do this, run Transaction in the target system.

• To avoid exports of authorization profiles insert the line PROFILE_TRANSPORT with the value

NO in the customizing table PRGN_CUST.

• When exporting activity groups, you can also transport user assignments. However, this should

not be done when using Central User Administration. You should protect the target system from

receiving these user assignments during a transport by inserting the line USER_REL_IMPORT

with the value NO in the customizing table PRGN_CUST.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 72

© SAP AG 1999

If you do not use Central User Administration, you must consider the following transport issues:



• Authorization profiles are normally transported along with the activity groups. After the import,

you need to perform a mass compare for all user master records and activity groups. To do this,

run Transaction choose → Enter the applicable activity

group in the field Choose and start the report

• When exporting activity groups you can also transport user assignments.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 73

© SAP AG 1999

If you do not use Central User Administration, you can also consider the following:



• You do not have to transport authorization, but instead regenerate them from the activity groups

in the target system. To do this run Transaction in the target system.

• To avoid exports of authorization profiles insert the line PROFILE_TRANSPORT with the value

NO in the customizing table PRGN_CUST.

• When exporting activity groups, you can also transport user assignments.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 74

© SAP AG 1999

Failedlogons

The keeps a record of security-related activities in the R/3 System. This

information is recorded daily in an audit file on each application server.

You can specify the information you want to audit in the Security Audit Log. To specify or change

the selection criteria, you can choose to:

• Save the selection criteria permanently in the database.

• Change the selection criteria dynamically on one or more application servers.

If you save the selection criteria permanently in the database, then all of the application servers use

the identical selection criteria for saving audit events in the audit log. You only have to define the

criteria once for all application servers.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 75

© SAP AG 1999

rsau/enable Enable security audit 0 (not activated)1 (audit activated)

rsau/local/file Name of security audit file audit_++++++++

rsau/max_diskspace/local Maximum space for security <customer-defined>audit file

rsau/selection_slots Number of selection slots for 1-5 (default value 2)security audit

The Security Audit Log is only active if you used Transaction to maintain and activate the

profiles. Set the profile parameters as stated above.

In the profile parameter rsau/local/file, the eight + symbols represent the date, which is automatically

substituted with the current date by the system.

If parameter rsau/max_diskspace/per_file is used, parameter rsau/local/file is no longer valid and will

no longer be analyzed. Parameters DIR_AUDIT and FN_AUDIT are used instead.

Parameter rsau/max_diskspace/local specifies the maximum size of a security audit file If this size is

reached, then system logging of audit events is completed.

Parameter rsau/selection_slots specifies the number of selection units that are set using Transaction

and checked by the system during processing.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 76

© SAP AG 1999

To determine what you want to audit, create selection criteria, using →

→ → (or call Transaction ).

For each selection criteria that you want to define, select the , , , and .

The selection specifies the levels of events (audit messages) that you want to include

in the audit log. Messages with the chosen level and higher are included in the log. For example, if

you select , then all messages with a security level of low, average, and high are included in the

selection. If you select , then only high-level messages are included.

describe those events where a high-level security risk is involved (such as

unauthorized access attempts). All audit events are defined in the system log messages with the

prefix AU. You can view the respective assignments of the events to audit classes and security levels

with the system log message maintenance transaction (). You can also modify these definitions

for your own purposes. For the and entries, you can use ’*’ as a wildcard for all clients orall users. However, a partially generic entry such as 0* or ABC* is not possible. For each selection

criteria you want to apply to your audit, place a checkmark in the column. After

having specified the selection criteria, save the data. For the application server to use the profile at

the next server start, choose → . The name of the active profile appears in the

field.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 77

© SAP AG 1999

The Security Audit Log produces a report on the activities that have been recorded in the audit file.

You can analyze a local server, a remote server, or all of the servers in your R/3 System.

To display the initial screen, call Transaction . It is designed similar to the System Log

(Transaction ).

The following information is provided:

• Time

• Client

• User

• Tcode (transaction code)

• Text (describing event)

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 78

© SAP AG 1999

SAProuter is a program that serves as an intermediate station between R/3 Systems or programs.

SAProuter acts as an application level gateway (proxy) and can be implemented independently of an

R/3 System directly on a firewall. SAProuter enables you to completely control access to your R/3System(s).

The network interface (NI) is a separate, platform-independent, intermediate layer developed by

SAP. The NI layer forms the upper part of the transport layer in the OSI 7 layer model. SAProuter as

well as all R/3 CPI-C and RFC programs use this layer.

SAProuter uses a configurable a route permission table to allow or deny connections from other

systems.

You can use SAProuter to:

• Control and log the connections to your R/3 System

• Allow access from only the SAProuters you have selected

• Protect your connection and data from unauthorized access

• Only allow encrypted connection from a known partner (using the SNC layer)

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 79

© SAP AG 1999

During installation, SAProuter is normally located in directory /usr/sap/<SID>/SYS/exe/run (UNIX).

SAP recommends that you create the subdirectory in the directory /usr/sap, because the

/exe/run dir. will be overwritten by the new kernel functions during an R/3 Release upgrade, thusdestroying your SAProuter configuration.

Under Unix, you can start SAProuter from the script . Under Windows NT, it is

recommended to define the service.

SAP also recommends downloading the most recent version from any sapserv system.

SAP recommends that the route permission table be maintained in /usr/sap/saprouter/saprouttab

(UNIX). If you wish to place this table in another directory or under a name other than saprottab,

specify the location using the option .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 80

© SAP AG 1999

A route string describes the stations of a connection required between two hosts. Each route string

has a sub-string for each SAProuter in between, and for the target server.

The syntax for the sub-strings are:

• /H/ = indicates the host name.

• /S/ = an optional entry used for specifying the service port. The default value is 3299.

• /W/ = indicates the password for the connection. The default is “”, no password.

In the example shown here, the connection from the customer’s frontend PC to SAP’s

application server is set up in three steps:

1. sets up the connection to according to the first sub-string.

2. uses the route permission table to check whether the connection is allowed.

This sets up the connection between both SAProuters.3. checks whether the route from customer_saprouter to the application server is

allowed. The password is also checked. sap_saprouter then sets up the connection to the

application server .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 81

© SAP AG 1999

*

A route permission table (saprouttab) must be defined for each SAProuter. The route permission

table contains the host names, port numbers, and passwords of a source and destination host. Each

time an access is requested, R/3 looks for table saprouttab in the working directory of the SAProuter.If no route permission table is found, SAProuter terminates with an error message.

To create a route permission table, use a standard text editor.

The route permission table contains a maximum of five fields for each possible access:

• , , , and

When making entries in these fields, you can use “wildcards” (*). However, these should be used

with caution.

In the example shown here, all computers with IP addresses beginning with 123.45.67 do not need a

password to communicate with all of the services on target computers with host addresses (IP

address) beginning with 123.45. If the first field displays a D instead of a P, access to the specifiedcomputer and its services has been denied. If you leave the service and password blank, the defaults

are used. For service the default is 3299; if the field is blank, no password is required.

When checking accesses, SAProuter looks for the first appearance of a or a for one

specific computer. Once this is found, the rest of the route permission table is not checked for this

computer.

When you configure the route permission table, specify all deny entries before permits.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 82

© SAP AG 1999

Step 1: In Window 1 ( host 1) start SAProuter by entering command . This

command starts SAProuter without parameters. For a complete list of SAProuter commands, search

for in the

Step 2: In Window 2 (host 2), start the test program niping to emulate a server by entering command

.

Step 3: In Window 3 (host 3), start the test program niping to emulate a client, by entering command

. This command tests the connection without SAProuter, that is, it tests

the connection directly between host 2 and host 3.

Step 4: In Window 3, restart the test program niping by entering the command

. This command tests the connection with SAProuter. A host name is

interpreted as a route through one or more SAProuters to the server if the host name is preceded with

/H/.

In steps 3 and 4, several data packets are sent to the server and then returned by the server.

To stop all active niping servers and clients, enter command .

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 83

© SAP AG 1999

The main SAProuter commands are:

• displays a complete list of the SAProuter parameters (this includes all options and

examples of a route permission table).

• starts program SAProuter.

• stops program SAProuter.

The trace level can be set to 1 to 3 (1 being lowest detail and 3 being the highest). The default

destination for the trace file is dev_rout in the work dir. You can specify the trace to another file by

setting the option.

For logging connections, you can specify a log file when starting your SAProuter. To do this, use the

option , for example, . All important actions such as connection start,

run-time operations, are logged to the file:

• Connection from (client name / address)

• Connection to (partner name / address)

• Partner service

• Start time/end time

• Connection requests rejected by the route permission table

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 84

© SAP AG 1999

The communication between the following system components can be protected using SAProuter.

• R/3 application servers

• SAP GUI

• SAPlpd

• External RFC programs

• External CPIC programs

When communication on the NI layer should include a SAProuter the host name fields in R/3 can be

used to store the complete SAProuter string.

Examples:

• RFC connection between two R/3 Systems: In the calling R/3 system the RFC connection is

maintained using transaction SM59. In the field enter the SAProuter string

e.g. /H/twdfmx16/S/3299/H/twdfmx17 instead of twdfmx17 (without SAProuter)

• R/3 Server - SAPlpd: In transaction choose output devices select the

S and in the field enter the SAProuter connection string

instead of the host name. If the field is too small for this string, you can use Transaction to

define a short host name known in R/3 and assign a whole SAProuter string to it. For example:

/H/twdfmx16/S/3299/H/twdfmx17/S/515 instead of twdfmx17 (without SAProuter).

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 85

© SAP AG 1999

If the connection between the application server and SAP GUI fails, a dialog box is displayed,

allowing you to reconnect to the SAP GUI. To log on again, choose and enter your user ID and

password. Then choose → .

This triggers a reconnection, and (if no problems exist) all the sessions you had prior to the

connection failure will be reattached and you can carry on working with the sessions you had before.

The SAP GUI reconnection is always performed on the same application server where the sessions

were running. If you log on using the connection broken pop up, you will not have any problems re-

logging on. If you do not use the pop up, the reconnection mechanism only works if you directly re-

log on to the correct application server.

User sessions are only available for the period specified in parameter rdisp/keep_alive, which has a

default value of 1200 seconds.

If no entry is made in the R/3 System, the frontend is automatically logged off after the number of

seconds specified in parameter rdisp/gui_auto_logout. If the value is 0, the frontend does not

automatically log off..

Note: If you the value of rdisp/keep_alive is greater than 0 and you do not use the reconnection, there

may be locking issues.

If the value of rdisp/keep_alive is lower than the value of rdisp/gui_auto_logout, you will lose your

work because the buffer will no longer have your work. In this example, rdisp/keep_alive is only

useful for a reconnection if you lose the connection to the R/3 System. That is, if there is a network

failure and you reconnect within the rdisp/keep_alive time, you will have your work.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 86

© SAP AG 1999

SAP programs are supplied either with an authorization group that does not fit in with the customer’s

authorization system, or without an authorization group altogether.

Program RSCSAUTH allows you to maintain the authorization groups for such programs without the

need to change the program attributes. It also allows you to restore customer-specific authorization

groups following an upgrade.

Program RSCSAUTH generates a list of type 1 reports (column ), the authorization groups

as maintained by SAP (column ), and those maintained by the customer (column ).

Column is an input field where you can enter your own authorization groups.

When you choose , the customer-specific authorization groups for all reports are copied

to table TRDIR. This has the same effect as changing the authorization group in the program

attributes, since existing SAP authorization groups are overwritten. The authorization groups for

each program are also entered in table SREPOATH. This is to allow you to restore customer-specific

authorization groups following an upgrade by running program RSCSAUTH again.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 87

© SAP AG 1999

R/3 Systems can establish trusted relationships between each other.

If a calling (sending) R/3 System is known to the called (receiving) system as a trusted system, no

password must be supplied.

The calling (sending) R/3 System must be registered with the called (receiving) R/3 System as a

trusted system. The called (sending) system is called the trusting system.

Trusted relationships between R/3 Systems have the following advantages:

• Single sign on is possible beyond system boundaries

• No passwords are transmitted in the network

• Timeout mechanism protects against replay attacks

• User-specific logon data are checked in the trusting system

The trust relationship is not mutual, which means it applies to one direction only. To establish a

mutual trust relationship between two partner systems, you must define each of the two trusted

systems in its respective partner systems.

Therefore, access to Transaction should be restricted and the contents of table RFCDES

should be checked regularly.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 88

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 89

© SAP AG 1999

The R/3 Security Guide contains detailed information about:

• All topics in this unit are covered

• References

• Checklists

• Further recommendations by SAP regarding security

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 90

© SAP AG 1999

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 91

In these exercises the course participants are divided into two groups:

is the group that already worked in system DEV. This group will set up a thecentral user administration in system DEV client 201. That is, the user master data willbe maintained there and be distributed from there. In this client, the user is BC305-201. Group A will use client 202 of system QAS as the receiving client for user master

data. The user in this client is BC305-202. is the group that already worked in system QAS. This group will set up a thecentral user administration in system QAS client 201. That is, the user master data willbe maintained there and be distributed from there. In this client, the user is BC305-201. Group B will use client 202 of system DEV as the receiving client for user masterdata. The user in this client is BC305-202.

With this exercise you will set up two logical systems:

Client 201 in your R/3 System will be your Central User Administration system. In thefollowing exercise this system will be called the "central system".

Client 202 in your partner R/3 System will be the logical system receiving user masterrecords send from the central system. In the following exercise, this system will becalled the “local system”.

1.1 Set up two logical systems in DEV and in QAS (enter the logical systemname in uppercase):

:

In DEV and in QAS maintain the two logical systems:

DEVCLNT201 and QASCLNT202

:

In DEV and in QAS maintain the two logical systems:

QASCLNT201 and DEVCLNT202

Note: Only use the names stated above.

2.1 :

Assign the two logical systems:

In DEV, assign DEVCLNT201 to client 201.

In QAS, assign QASCLNT202 to client 202.

:

Assign the two logical systems:


In DEV, assign DEVCLNT202 to client 202

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 92

3.1 Enter an RFC destination for each client/system you would like to connect to.

:

Create RFC destinations:

In DEV, create QASCLNT202 (upper case) to client 202 of QAS (for thedistribution of user master records). Use user BC305-202 and its password.

In QAS, create DEVCLNT201 to client 201 of DEV (for the distribution ofuser master records). Use user BC305-201 and its password.

:

Create RFC destinations:

In QAS, create DEVCLNT202 to client 202 of DEV (for the distribution ofuser master records). Use user BC305-202 and its password.

In DEV, create QASCLNT201 (upper case) to client 201 of QAS (for thedistribution of user master records). Use user BC305-201 and its password.

3.2 Next, test whether your RFC connection has a user with the authorization tolog in to the target host

4.1 Now each group works in its central system (client 201) only.

Set up the ALE distribution model view <SID>USER, where <SID> is thesystem ID of your central system.

4.2 Define that in the created model view the users (object ) and the userscompany address (object ) should be always kept up to date(method ) from the central system to the dependant system.

Hint: Use the button in Transaction

5.1 On your central system (client 201) generate the for:

model <SID central system>USER

partner system <SID local system>CLNT202

6.1 Distribute the system landscape from the central system to the local system.

6.2 Generate the partner profile for model <SID central system> USER on thelocal system.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 93

7.1 Define that the field can be maintained locally and will beredistributed (RetVal).

Define that all remaining fields should be maintained globally (Global).

8.1 In the central system, create the user DISTRIBUTE with password initial for

both of your logical systems. Assign the authorization profile SAP_ALL forboth logical systems.

9.1 Change the first name of user DISTRIBUTE in the local system to HUGO.

9.2 Check the central system (client 201) to see if the first name HUGO of userDISTRIBUTE has been redistributed.

10.1 SAProuter is running on your server. Which connections are permittedaccording to the route permission table?

Note: You must use Transaction to display the file saprouttab in thetransport directory DIR_TRANS.

11.1 In your central system (client 201), create the RFC destination SECURE tothe local system (client 202) using the SAProuter connection and itspassword pass. Specify the following:

: EN

: 202

: BC305-02

: (Will be supplied by the instructor).

Perform a remote logon to make sure the connection works.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 94

In these exercises the course participants are divided into two groups:

is the group that already worked in system DEV. This group will set up a thecentral user administration in system DEV client 201. That is, the user master data willbe maintained there and be distributed from there. In this client, the user is BC305-201. Group A will use client 202 of system QAS as the receiving client for user master

data. The user in this client is BC305-202. is the group that already worked in system QAS. This group will set up a thecentral user administration in system QAS client 201. That is, the user master data willbe maintained there and be distributed from there. In this client, the user is BC305-201. Group B will use client 202 of system DEV as the receiving client for user masterdata. The user in this client is BC305-202.

With this exercise you will set up two logical systems:

Client 201 in your R/3 System will be your Central User Administration system. In thefollowing exercise this system will be called the "central system".

Client 202 in your partner R/3 System will be the logical system receiving user master

records send from the central system. In the following exercise, this system will becalled the “local system”.

1.1 To set up the logical systems, in the Implementation Guide (Transaction

), choose → →

→ → →

. Choose →

:Enter DEVCLNT201 and QASCLNT202 in DEV, and

Enter DEVCLNT201 and QASCLNT202 in QAS.

:

Enter QASCLNT201 and DEVCLNT202 in QAS, and

Enter QASCLNT201 and DEVCLNT202 in DEV.

Save your entries and create a transport request, if required.

2.1 To assign logical systems to clients, choose → →

→ →

In the , enter the name you defined in step 1.1 (remember touse uppercase).

:

In DEV, assign DEVCLNT201 to client 201.


:

In QAS, assign QASCLNT201 to client 201.In DEV, assign DEVCLNT202 to client 202.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 95

3.1 To create RFC destinations choose → →

→ → (Transaction SM59). Choose and fill in the fields displayed as follows:

In the central system (DEV client 201):

QASCLNT202

3 (R/3 connection

Connection for Central User Administration

Choose to display additional fields related to this connection type:

<HOST> (the target instance host, supplied by your instructor)

<target instance number> (supplied by your instructor)

No

EN 202

BC305-202

as given by the instructor.

In the local system (QAS client 202):

DEVCLNT201

3 (R/3 connection)




<target instance number> (supplied by your instructor

No

EN

201

BC305-201


Save the entry and then, from the menu, select Can aconnection be established? If so, you see a report detailing connectionspeed. If not, you see an error; ask the instructor for help.

In the central system (QAS client 201)

: DEVCLNT202

3 (R/3 connection)





8/11/2019 BC305_EN_46B


(C) SAP AG BC305 96

No

EN

202

BC305-202


In the local system (DEV client 202): QASCLNT201

3 (R/3 connection)



Target host: <HOST> (the target instance host, supplied by your instructor)


No

EN

201

: BC305-201


Save the entry and then, from the menu, select . Can aconnection be established? If so, you see a report detailing connectionspeed. If not, you see an error; ask the instructor for help.

3.2 To test whether your RFC connection has a user with the authorization to login to the target host, call Transaction and select the RFC destinationscreated in 3.1.

From the menu, select If the authorization fails, ask theinstructor for help.

4.1 Each group works in client 201.

To set up ALE distribution model, call Transaction and choose

. Then choose → →

→ (or call Transaction

Choose → . The defaultprocessing mode is displayed.

Choose Enter the description

and the technical name .

Save your entries.

4.2 To set up objects and methods in the created model view call Transaction and choose .

1. To define object USER, specify the following:

: DEVUSER

: DEVCLNT201

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 97

: QASCLNT202

: USER

: Clone

Save your settings.

2. To define object UserCompany, specify the following:

: DEVUSER

: DEVCLNT201 : QASCLNT202

UserCompany

: Clone

Save your settings.

1. To define object USER, specify the following:

: QASUSER

: QASCLNT201

: DEVCLNT202

: USER

: Clone

Save your settings.

2. To define object UserCompany, specify the following:

: QASUSER

: QASCLNT201

: DEVCLNT202

: UserCompany

: Clone

Save your settings.

5.1 To generate the partner profile on the central system, call Transaction

and choose → .

In the field enter <SID central system>USER.

In the field enter <SID local system>CLNT202.Use the default values for all other fields.

Choose

6.1 To distribute the system landscape from the central system to the localsystem, on the central system call Transaction and choose →

→ .

Select model view <SID central system>USER.Choose .

Note: If the names of the RFC connections are the same as the logical name

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 98

of the local system the right system is already marked.

Choose

6.2 To generate the partner profile for model <SID central system> USER on thelocal system, on the local system call Transaction . You should nowsee the model view created in the central system.

From the same screen (Transaction ), choose → .

In the field enter <SID central system>USER.

In the field enter <SID central system>CLNT201.

Choose

7.1 Work on the central system (client 201)

To set up the field selection, from the SAP Implementation Guide, choose → →

→ → →

→ → (Transaction ).

Choose the model view <SID central system>USER.

Choose

Choose →

To define that the field can be maintained locally and will beredistributed, in the tab select for this field.

By default, all other settings are defined as Global.

Save your settings.

Note: Even after saving the entries you will be warned that .Ignore this pop up, and leave the transaction.

8.1 To create the user DISTRIBUTE in the central system, start Transaction.

In the field , enter DISTRIBUTE.

Choose

In the tab , specify the following: : DISTRIBUTE.

: (Leave this field blank)

In the tab :

Enter and repeat as initial password INIT.

In the tab :

In the first line of column , enter <SID central system>CLNT201.

In the first line of column , enter SAP_ALL.

In the second line of column , enter <SID local system>CLNT202.

In the second line of column , enter SAP_ALL.

Save your settings, and confirm the following dialog boxes.

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 99

Now the user is automatically distributed to the local system.

9.1 To change the first name in the local system, log on to the local system(client 202) with user DISTRIBUTE and password INIT.

Start Transaction

In the field , enter DISTRIBUTE.Choose

In the tab , enter the name HUGO in the field

Note: The field is the only input field that is enabled.

Save your entries.

9.2 To check if the first name HUGO has been redistributed, on the centralsystem start Transaction .

In the field , enter DISTRIBUTE.

Choose .

The field now contains the name HUGO.

10.1 To check which connections are permitted according to the route permissiontable, call Transaction Double-click DIR_TRANS. Then double-clickthe file saprouttab. This file contains only one line:

P * * * pass

This means that all connections are permitted, but you need to provide thepassword .

11.1 To create the RFC destination, call Transaction in your central system(client 201).

Choose and fill in the fields displayed as follows:

In system DEV:

SECURE

3 (R/3 connection

Using SAProuter

Choose to display additional fields related to this connection type.

/H/<HOST1>/S/3299/W/pass/H/<HOST2>

Note: For HOST1 and HOST2, use the entries as supplied by your instructor.


No

EN

202

BC305-202

8/11/2019 BC305_EN_46B


(C) SAP AG BC305 100


Save your settings.

In system QAS:

SECURE

3 (R/3 connection

Using SAProuterChoose to display additional fields related to this connection type:

/H/<HOST2>/S/3299/W/pass/H/<HOST1>

Note: For HOST1 and HOST2, use the entries as supplied by your instructor.


No

EN

: 202

BC305-202


Save your settings.

To perform a remote logon, from the same screen choose .

8/11/2019 BC305_EN_46B



© SAP AG 1999

8/11/2019 BC305_EN_46B



© SAP AG 1999

An external command is an alias defined in the R/3 System that represents an operating system

command. For example, you can define the external command ZPING, which represents the

operating system command .

Both the maintenance and execution of external commands is protected with R/3 authorizations. You

can maintain and execute external commands online (from the CCMS) or in ABAP programs using

special function modules. External commands can also be executed as a step in a background job.

You can create, display, change, delete, rename, and copy external commands. SAP commands

cannot, however, be changed in customer systems. Command names beginning with “Y” or “Z” are

reserved for customer commands. To define external commands, choose → →

→ (or call Transaction ). External commands are uniquely

identified by a user-definable logical name and an operating system name. To ensure the program

can be found in the target system, enter the full path of the program in the field . If the external

program requires parameters or options, enter them in the field .

In the field , you can specify the name of an R/3 function module that is executed

before the external command. This module determines whether the specific command should be

executed or not. The interface to this check module must be the same as for the check module

delivered by SAP (SXPG_DUMMY_COMMAND_CHECK). SAP recommends that you use a

of' SXPG_DUMMY_COMMAND_CHECK.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The process of running an external program is initiated by the SAP Gateway and the R/3 executable

SAPXPG.

To run an external program, the following requirements must be met:

• The SAP Gateway must be active and able to set up a connection between the R/3 background

server and the target host, where the external program will be executed.

• You must either specify the full path of the external program, or the program must lie on the

search path of the operating system user of the SAP Gateway.

• The SAP Gateway must start the external program with the operating system user of the SAP

Gateway. This is < for Unix systems, and for Windows NT.

• The R/3 executables directory (usually directory /usr/sap/<sid>/SYS/exe/run) must lie on the

search path of the operating system user of the SAP Gateway.

• The external program is started using an R/3 control program that accepts the return code of the

external program.

If you have any problems running external commands, you should check the system requirements.

Ensure the target system is set up correctly for running external commands and programs. See the

Online Documentation .

8/11/2019 BC305_EN_46B



© SAP AG 1999

To start an external command in dialog, choose → → → (or

call Transaction ). Position the cursor on the line containing the command and choose .

The command is then displayed along with its parameters.

Before you execute the command, you can specify additional parameters, as well as the name of a

target server. The default entry for target server is the name of the application server (SY-HOST).

The execution of external commands is checked by the authorization object S_LOG_COM. This

object has three fields and , where the administrator can specify

which command can be executed for which operating system on which host. Administrators must

control who has authorization based on authorization object S_LOG_COM, since programs can be

accessed at the operating system level.

For the maintenance of external commands, you need an authorization based on the authorization

object S_RZL_ADM with activity “01 and 03”. Authorization S_LOGCOM_ALL, which enables

the execution of all external commands, is delivered with the standard profiles S_A.SYSTEM and

S_A.ADMIN. The authorization concept for background processing, with respect to the profile

generator, is covered at the end of the unit.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To start an external command in the background, choose → → → (or

call Transaction ). Choose and specify the name of the parameter (and any

additional parameters), the operation system name, and the target host.

Under , you can choose whether the command output and error messages are written to

the job log.

External commands and external programs can be started asynchronously. This means the

background work processes start the operating system program and then continue with the

background processing.

If any problems occur, you can activate a trace at the operation system level. The trace files dev_cp

and dev_xpg contain trace information. They are located in the work directory of the instance. To

analyze the trace files from R/3, use Transaction or .

8/11/2019 BC305_EN_46B



© SAP AG 1999

Long-running background jobs can occupy a background work process for a long period of time. If

many of these jobs are running simultaneously, there may be no available background work

processes in the system.

SAP offers parallel-processed background jobs as a solution for the problem of “not enough

background work processes” or “not enough time during the night”. For example, parallel processing

is used for the Material Resource Planning Run (MRP) and for the Summarization Run in CO

(Transaction ).

Parallel processing enables long-running background jobs to be divided into smaller parts. The work

is split up in units and done in parallel by the available work processes in the R/3 System. The

results are collected later. The data processing task to be performed in parallel must be logically

independent of other parts of the task. That is, the task is performed without reference to other

records from the same data set that are also being processed in parallel, and the task does not depend

on the results of other parallel operations.

Parallel processing is implemented in ABAP reports and ABAP programs, not in the background

processing system itself. This means that jobs are only processed in parallel if the report that runs in

a job step is programmed for parallel processing using the keyword CALL FUNCTION STARTING

NEW TASK DESTINATION IN GROUP.

Parallel processing is not suitable for data that must be sequentially processed or if the processing of

one data item is dependent upon the processing of another item of the data. Parallel processing does

not ensure that data is processed in a particular order, or that a particular result is available at a given

point during processing.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Using other types of asynchronous RFC circumvents the built-in safeguards in the correct keyword,

and can have a negative impact on system performance. By using RFC groups, you can permit

certain servers to only be used for the parallel processing. Servers outside of RFC groups are notinvolved in parallel processing.

Before you implement parallel processing, the system administrator must define RFC groups. To do

this, choose → → → (or call Transaction ).

To display the RFC groups, choose → (or call Transaction ).

For each R/3 instance included in an RFC group, you can configure several resource limits. Having

several recourse limits ensures that dialog processing is available even if the system is under a heavy

load caused by parallel processing. The resource limits correspond to R/3 profile parameters, which

normally start with rdisp/rfc* and are described in detail in SAP Note 99284.

For example, the entry corresponds to the R/3 profile parameter

rdisp/rfc_min_wait_dia_wp. This parameter fixes the number of dialog work processes that shouldremain free for the other dialog users. If no dialog work process is free, no further resources are

returned to the caller, to protect the server from being overloaded. These parameters can be switched

dynamically.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The standard background scheduling system of R/3 offers a set of functions that can be accessed

through Transaction . The new job wizard is an easy-to-use interface for defining and releasing

background jobs. For example, it is easy to define a job chain or to start two jobs independent from athird one.

If you need more enhanced scheduling mechanisms, such as periodically started or complex

scheduled job chains, you can use the application programming interface (API) of the background

processing system. This is a set of function modules that can be used from your own ABAP

programs to schedule and manage background jobs.

The API offers function modules for the following tasks:

• Managing jobs (creating, releasing, displaying, copying, and deleting jobs)

• Checking and triggering events, which can be used to start other background jobs

• Displaying the log generated by a background job

There are two methods to schedule background jobs using the API:

• An with only two function modules and limited functionality

• A , which offers complete functionality

The API is described in the Online Documentation under → →

→ .

8/11/2019 BC305_EN_46B



© SAP AG 1999

The entire background job can be defined by using the function modules located in the function

group .

To schedule a background job from within a program using the , you must:

• Create the job using function module JOB_OPEN. This function module passes a name to the

background system. The system then returns the job count, the unique ID number that identifies

the job, and the job name.

• Collect the job specifications (report or program to run, start time, and so on).

• Add one or more job steps to the job with the function module JOB_SUBMIT.

• Close the job and pass it to the background processing system for execution with the function

module JOB_CLOSE. You can specify lots of job-start attributes and many run-time attributes of

a job in this function module.

With these function modules, it is easy to plan a periodically scheduled job chain: You need a report

that plans a job chain consisting of two jobs. The second job starts after the first one. You need to

schedule the planing report to be run periodically.

The disadvantage of using the is that you need time and a bit of experience in

ABAP programming.

8/11/2019 BC305_EN_46B


8/11/2019 BC305_EN_46B



© SAP AG 1999

The XMI logs external access. When external programs want to use R/3 background functions, for

example, they first have to open a XMI session using an RFC connection. This means, they have to

log on with an R/3 user and password. The logon is only successful if the R/3 user’s authorization isbased is on authorization object S_XMI_PROD. After logon, all the background functions that are

used by using the XBP interface are logged by the XMI.

The XMI consists of a set of RFC-enabled function modules. The names of these function modules

start with BAPI_XMI, and they are located in function group SXMI. Since R/3 Release 4.5, XMI is a

standard and stable BAPI interface. Information about the business object XMISESSION is located

in the business object builder (Transaction ). offers detailed information in the open

BAPI network (use the SAPNet shortcut located at the end of the unit).

Each session between the R/3 System and an external management tool begins by establishing an

RFC connection. An RFC session consists of one or more XMI sessions, which are opened by using

function module BAPI_XMI_LOGON. Each XMI session contains a series of function calls to the

function modules in the individual interfaces. If one of the session partners (the R/3 System or the

external tool) is affected by a program crash and a new RFC session is initiated, the changed

situation is recognizable through a new session ID.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The XMI log is a database table containing message texts that have various degrees of detail. The

audit level determines the degree of detail to which messages in the XMI log are written.

You can review the access monitoring information that has been collected and logged in the R/3

System by using Transaction . This transaction displays the following information:

• Time at which the entry was triggered

• SAP user ID

• Changes carried out within the system (for example, an alert reset)

You can also read the information from the XMI log with an external tool, using the function

BAPI_XMI_SELECT_LOG. You can use this function to read parts of the XMI log in another

language (other than English), as long as the message texts were installed in this language.

You can only delete old XMI log entries using Transaction . The process of deleting entries

itself creates an entry in the XMI log, recording that deletion has taken place. There is no external

function for this kind of reorganization. This prevents external agents from being able to cover up

their own tracks.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Job A0003

Start Job A0003 on non-R/3 System

Jobs can be created and monitored from outside the R/3 environment using certified third-party

software tools. These tools use the XBP interface, which is constructed through a pool of function

modules on the R/3 side. External management systems can call these modules using RFC.

The names of these function modules start with BAPI_XBP, and they are located in function group

SXBP. They call exactly the same function pools as the internal R/3 operations. Since R/3 Release

4.5, XBP is a standard and stable BAPI interface. Information about the business object XBPJOB is

located in the business object builder (Transaction ). offers detailed information about

the Open BAPI Network.

In order to be able to work in the R/3 System, an external job scheduling system must be able to

carry out the following functions in the R/3 System:

• Define, work with, and delete jobs

• Start jobs, terminate active jobs

• Access information about jobs (such as status and log) and resources in the R/3 job scheduling

system (number and status of background work processes)

Any critical changes to R/3 jobs (such as creation, editing, and deletion) are recorded in the XMI log

in the R/3 System, which can be display using Transaction .

For a list of available certified third party software tools, see

in (use the SAPNet shortcut located at the end of the unit).

8/11/2019 BC305_EN_46B



© SAP AG 1999

For reasons of security, the R/3 System features its own authorization component. This ensures that

critical operations and data are protected against unauthorized access.

Authorization checks are performed when jobs are , , and .

Authorization checks are based on the roles users have when handling jobs:

•

Authorized to create Class A background jobs, use external commands, and to view all jobs in all

clients in the background processing system

•

Authorized to schedule Class B and C jobs and display the status and output of their own jobs

Each step of a background job has to run under a specified R/3 user. The user is entered during step

definition. When a job is executed, the R/3 System checks whether the user master record permits

processing or not. For security reasons, you must define R/3 authorizations to restrict the users thatcan be entered. Periodically scheduled system jobs should be run under “dummy” background users,

which are defined in Transaction . These are permanent “dummy users” with specially

designed user master records, and are only used for background processing, not for interactive work.

If an end user must access operating system commands, use external commands to restrict their

access. You should restrict end users from accessing external programs, since you can only give

them full authorization (for all external programs) you cannot define one specific program.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Operation on jobs

(S_BTCH_JOB)

DELE Delete jobs of other usersLIST Display spool lists of other usersPROT Display job logs of other usersRELE Release own jobs automatically

SHOW Display other users job definitions

JOBACTION

* Reserved, set to *JOBGROUP

Backgrounduser name

(S_BTCH_NAM)

<name> Authorized user when schedulingBTCUNAME

Y User is background administratorN or empty Restricted to jobs in current client

Administrator(S_BTCH_ADM)

BTCADMIN

To set up a background administrator, maintain a of the activity group

SAP_BC_BATCH_ADMIN_AG.

This group bundles most of the authorization objects used in the background system, such as:

• S_BTCH_JOB

Operations on Background Jobs. This authorization object allows a user to release their own jobs

and perform operations (other than release) on the jobs of other users.

Determines the following functions:

DELE Delete jobs of other users

LIST Display spool requests created by jobs of other users

PROT Display job logs created by other users

RELE Release your own jobs automatically during scheduling

SHOW Display job definitions of other users

• S_BTCH_NAMBackground User Name. Determines which authorized users you can choose when scheduling a

job. An authorized user provides the authorizations required for performing a background job.

• S_BTCH_ADM

Grants authorizations to an administrator, enter Y.

This authorization object allows an administrator to access background jobs in all clients of an

R/3 System, perform all functions on background jobs, and execute external programs in job

steps.

8/11/2019 BC305_EN_46B



© SAP AG 1999

System administration

(S_RZL_ADM)

01 All CCMS management functions03 Only display activities in CCMS

ACTVT

Externalcommands

(S_LOG_COM)

<name> Name of logical commandCOMMAND

<name> Name of operating system

<name> Host name of target systemHOST

OPSYSTEM

• S_RZL_ADM

This authorization is required to grant update and maintenance capabilities to the system

administrator for CCMS functions.Activity code 01 grants the administrator all management functions with CCMS.

Activity code 03 grants only display capabilities in CCMS.

• S_LOG_COM

Execute Logical Commands. This authorization object allows a user to execute external

operating system commands. This authorization object is missing in the activity group template

and must be inserted manually.

The following fields are available:

COMMAND: Logical name of the external command

OPSYSTEM: Name of the operating system on the target host

HOST: Host name of the target system

8/11/2019 BC305_EN_46B



© SAP AG 1999

To display the status of the background jobs scheduled under your user ID, choose → (or call Transaction ). A list of the most recent active and cancelled jobs are also displayed.

To display the , choose → → → (or call Transaction

). Choose and specify the jobs you want displayed.

The status of a job is written to the . If an error occurred, the job status is . If this

occurs, you can also check the .

Check for jobs with a high delay time. These jobs were scheduled, but there was no free background

work process available to process them.

You can perform a general check of the background system by using Transaction . The check

area can be expanded by choosing → .

More statistical information is shown in Transaction . These statistics include the number of

times the job has run, the average runtime, and the difference between the average runtime and theruntime of the job. If no job history statistics are displayed, you can update the statistics database in

Transaction , by choosing → .

8/11/2019 BC305_EN_46B



© SAP AG 1999

With respect to workload balancing, you should keep the following in mind:

• You can reserve background work processes for Class A jobs using Transaction . However,

you should not reserve too many, as this will delay important Class B and C jobs.

• You should avoid using the central instance for background processing. The central instance

should be mostly used for update requests.

• and jobs cannot be forecast in the

(Transaction ). These jobs may exceed the average runtime and result in additional

delays. Since the resources required for these jobs cannot be determined in advance, you should

limit the amount of and jobs.

• You should set R/3 profile parameter rdisp/btctime differently on the R/3 instances. Assume this

parameter is set to 60 on both instance A and instance B, and A is started before B. In this case,

the background scheduler of A always runs first. If enough free work processes are found on A,

no jobs or very few jobs are dispatched to B. If parameter rdisp/btctime is set to 61 on instance A

and set to 62 on instance B, A and B pick up jobs in turn, which results in better load

distribution.

(See SAP Note 24092)

8/11/2019 BC305_EN_46B



© SAP AG 1999

8/11/2019 BC305_EN_46B



© SAP AG 1999

→ → →

8/11/2019 BC305_EN_46B



© SAP AG 1999

8/11/2019 BC305_EN_46B



1.1 Create the external command ZPING, which executes a at the operatingsystem level. Allow the specification of additional parameters.

1.2 Execute the external command in dialog and check the results.1.3 Create a background job with the following specifications. Do use the job

wizard:

: ZEXTERNAL

: C – Low priority

: Select central instance

: ZPING

: Name of R/3 server of your neighbor

: Name of your R/3 server

Define the job so that:

The external output is copied to job log.

The external errors are recorded in job log.

The job waits for termination of external program

There is only one step in the job chain.

The job is started immediately.

Check the job results in the job log.

8/11/2019 BC305_EN_46B



1.1 To create the external command ZPING, run Transaction and go into

mode. Select → . Specify the following:

: ZPING : ping

: Select

Save your entries and go back to the initial screen of the transaction and savethe list again.

1.2 To execute the external command in dialog, run Transaction anddouble-click on the command ZPING created in exercise 1.1.

Under , enter the name of the R/3 server of yourneighbor and choose

The output of the ping command is displayed.

1.3 To create a background job, run Transaction . Specify the following:

ZEXTERNAL

: C

: Select central instance

Choose

Select

Specify the following: : ZPING

: Name of R/3 server of your neighbor

: Windows NT

: Name of your R/3 server

Choose

Select

Select

Select

Choose

Choose again.

Choose

Choose

Save your entries.

Save the whole job.

To check the results of your job, choose (Transaction

Select job ZEXTERNAL, then choose .

8/11/2019 BC305_EN_46B



© SAP AG 1999

8/11/2019 BC305_EN_46B



© SAP AG 1999

The skills listed here have already been covered in the TCC course unit, R/3 Spool and Print, which

describes simple administration tasks.

More advanced features, such as pool devices or load balancing for spool servers, are covered in this

unit.

8/11/2019 BC305_EN_46B



© SAP AG 1999

This unit focuses mainly on the full administration menus of Transaction .

include all the simple administration tasks, as well as maintaining

real and logical output management systems (OMS) definitions.

OMS require a partner product and therefore are configured by partner consultants. For details of

OMS systems see → → →

→ → → →

→ → .

include all the extended administration tasks, as well as maintaining:

• Device types

• Print controls

• Formats

• Character sets

8/11/2019 BC305_EN_46B



© SAP AG 1999

Device pools in R/3 allow you to group multiple devices under a single name. A device pool can be

used in two different ways:

• To send output to all devices in the pool at the same time. This scenario can be used when the

same document needs to be sent to different locations within the company.

• To send output to a single device in the pool according to a load-balancing mechanism. In this

scenario, the system chooses a device from the pool.

Each device in a pool can also be addressed individually by its own name. In this example, the user

has the following options:

• Print to the pool called Pool_1

• Print to the device called Printer_A

• Print to the device called Printer_B

A pool can also be used to create logical device names. In this case, the pool contains only one

device. The users access this device through the pool name, and if the device is not available at some

point, the administrator can change the pool to point to a different device.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To define a device pool, use Transaction and choose .

The following fields are used for a device pool:

• : Specify the pool name as defined in R/3. Pool names follow the same rules as

output device names.

• : Specify the name that the spool system uses to access the pool. The short name can

be automatically generated by the system when the pool is defined.

• : Specify the type of the devices included in the pool. Generally, all devices included

in a pool should have the same type.

• : Specify the class of the pool being defined, for example, a printer pool or fax pool.

• : Select .

To enter the list of devices included in the pool, choose . In the dialog box that appears,select one of the functions displayed to specify whether output should be sent to all devices in the

pool, or to a single device in the pool.

Note: Transaction recognizes the last entry of each user. You can change the predefined

output device and its access method by selecting → →

→ → then choose

8/11/2019 BC305_EN_46B



© SAP AG 1999

hs5821_TC1_00

hs5821_TC1_00

: allowed

hs5822_TC1_00

hs5823_TC1_00

: not allowed

hs5823_TC1_00

hs5822_TC1_00

Load balancing allows the system to dynamically determine the best spool server available to

process an output request. Load balancing works for both logical and real spool servers.

Load balancing can be activated independently for each spool server. If an output request is

generated for a spool server where load balancing is active, the system searches both the mapping

and the alternate definition of that server to find the spool server that has the shortest queue of spool

requests waiting to be processed. This selection algorithm is recursive. As the system checks the

mapping and alternate defined server hierarchies, it applies the selection rules to each level.

In this example, an output request is generated for output device . Assume that all the real

servers shown are active. has been assigned the logical spool server . Since load

balancing is active on , the system searches through the mapping and alternate definitions,

looking for the best server. The mapping field of points to the real server . Since this

is not a logical server, and it does not have an alternate server defined, it is considered a terminal

node and potential server to use for the output request. Now the system searches through the

alternate path of ,and it finds logical server . Since load balancing is not active for

, the system does not search through the alternate definition of . It only goes

through the mapping definition and finds real server , which is also a terminal node.

Therefore, at the end of the process, two servers are returned to the root of the server hierarchy:

and (one for each path). These two servers are then compared, and server is

chosen because it has the shortest queue. If load balancing had been active on , the system

would have chosen real server as the best server available.

8/11/2019 BC305_EN_46B



© SAP AG 1999

hs5821_TC1_00

hs5822_TC1_00

When load balancing is active you have to consider that the one physical printer is defined or

accessible from all machines with the R/3 real spool server running.

• In a Windows NT environment, this means that the printer must be defined locally on the remote

server (in this example, hs5822) and be connected to the server where the printer is physically

connected to. Proceed as follows:

- On the local server (in this example, hs582) define the local printer (PRI) and share it to the

network.

- On the remote server (in this example, hs5822) define the printer (PRI) locally but connect

this printer to the LPR port and printer of the local server (hs5821).

- Note: It is not sufficient to just define the printer as a network printer on NT on the remote

server. The name of this printer on hs5822 (‘PRI on hs5821’, or \\hs5821\PRI) would then be

different to the name on the local server (PRI) or this name would contain blanks. Blank

characters in printer names are not recognized by R/3.

• In an UNIX environment, the printer must be defined as a remote UNIX printer. However, the

printer names must be identical.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Query status

A spool work process keeps track of the print requests it sends to a host spool system, so users can

monitor the status of their own requests within R/3. To enable this monitoring, a spool work process

must query the host spool system periodically.

While the spool work process is querying the host spool system, it cannot process other output

requests. This may lead to overall performance problems in the spool system, especially if the spool

work process has to query a remote host through a slow or unreliable network link.

To avoid potential performance problems, particularly with printers using remote access methods,

deactivate the status query for an output device. To do this, call Transaction , choose

, select the output device you want to change, and go to the section.

Select the option .

If this option is selected, output requests are considered as soon as they are passed on to

the host spool system.

Important instance profile parameters

• For : rspo/lpq/temp_disable_slow, rspo/lpq/temp_disable_time, rspo/lpq/retries,

rspo/lpq/warn_time

• For : rspo/tcp/retries, rspo/tcp/retrytime, rspo/tcp/timeout/write,

rspo/tcp/timeout/connect, rspo/tcp/timeout/read

For information about instance profile parameters, see the documentation in Transaction .

8/11/2019 BC305_EN_46B



© SAP AG 1999

If the option in the section is selected

for an output device, request processing for this device can be monitored using the

. The output device is visible in the CCMS Alert Monitor only after the first output requesthas been sent to this device.

As a result of this selecting this option, an entry for the device is created in the . This

entry is created in Transaction under → →

→ → → → , or under

→ → → → →

Because of the memory required to set up this structure, monitoring should be restricted to critical

devices.

If the printer is deleted, you can also manually delete the node in the CCMS. To do this, mark the

output device in the alert monitor, activate the maintenance function and choose →

→

8/11/2019 BC305_EN_46B



© SAP AG 1999

Name

Character set

Name

Character set

R/3 supports a variety of printers by using standard device types. However, if you have a printer that

is not supported, there is no standard device type that fulfills all the printer requirements. If you have

a non-standard printer, a new device type must be defined for them. To do this, a standard devicetype can be copied, and the copy can be modified.

The following spool objects are related to a device type, and may be used in the modification

process:

• : Specifies the codes with which characters must be represented in the print-ready

output stream. These codes replace the generic character set used internally by the spool system.

• : Represents printer operations such as switching to boldface or changing the font

size. Print controls are replaced by printer-specific commands during output request formatting.

• : Identifies a type of paper supported by R/3, such as LETTER or DINA4. There are also

formats for SAPscript (type S) and for ABAP lists (type L).

• : Provides the interface between a format and SAPscript, specifying the paper

dimensions, which enables SAPscript to determine the line and page lengths.

• : Represents the device-specific commands required to implement a format. For

example, the . action may contain a printer command to set the number of lines on

each page. There is a set of actions for each format supported by each device type.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Name

Character Set

It is not usually necessary to create a new device type from scratch since there is a standard device

type that matches the printer requirements to some extent. This device type is copied to a new type,

then the copy is changed to fully support the printer. A standard device type should never be changeddirectly.

To copy a device type, call Transaction and choose → →

. Specify the source and target device types. The new device type name should be within the

customer name range. Mark the field if you want the new device type to reference the

format actions of the source type. This is useful if you intend to make minor changes to the device

type (for example, if you only want to customize the title page for the device type). If you want to

copy all the format actions and modify them, leave it blank.

You can also make changes to the device type, according to the printer specifications. Common

changes for the new device type are:

• Changing the character set

• Changing the print controls

• Changing the format actions

• Adding new formats

Use the printer manual to identify commands and control sequences needed to control the printer.

8/11/2019 BC305_EN_46B



© SAP AG 1999

COPY

59 semicolon

60 less

61 equal

62 greater

63 question

64 at

65 A

60 B

No. Name

59 3B

60 3C

semicolon

less

No. X1 X2 X3 X4 Name

59 5E

60 3C

semicolon

less


The R/3 spool system maintains a central list of all the characters used in character sets. Each

character has an R/3 ID number. For example, character semicolon (;) has ID number 59. In order to

display this character list, call Transaction and choose → .You can add new characters to this list, and their IDs should be in the range 9000-9999.

To print a character, the spool system replaces the character with the hexadecimal sequence found in

the character set used by the target printer. For example, for character set 1143, character semicolon

(;) is replaced by the hexadecimal number 3B.

To adjust the character set for a new device type, a standard character set can be copied first. Then

the copy can be changed. A standard character set should never be changed directly.

To copy a character set, call Transaction and choose → .

Position the cursor on the character set you want to copy, and choose . Specify the target

character set, which should be in the customer name range (starting with 9).

The example above shows that the hexadecimal sequence for the character semicolon (;) was

changed from 3B to 5E in the copied character set 9143.

Once the new character set is completed, it should be assigned to the device type. To do this, call

Transaction and choose → , and modify the device type

definition.

8/11/2019 BC305_EN_46B



© SAP AG 1999

1/3

2/3

3/3

In order for a device type to support a format, a set of format actions must be defined for the device

type-format combination. These actions are sets of control sequences (escape sequences) or printer

commands that perform a particular operation on the printer, such as , orrespond to particular events such as or .

This example shows the printer initialization action for the device type EPESCP9 and the format

LETTER. This format action is copied when the device type is copied to a new device type. You can

make the required adjustments by changing the corresponding escape sequences in the copy. You

can use predefined control codes when editing the escape sequences, such as: \e (ESC character) or

\0x (marks the next two characters as a hexadecimal number).

To change the format actions for a device type and format, call Transaction and choose

. Then choose and place the cursor on the device type you want to adjust.

Choose . To display the list of available format actions, double-click the format you want to

adjust. Then double-click each action you want to adjust and make the necessary changes.

Sometimes a new format is required for the device type, for example, if a new paper size is to be

handled by a printer. In this case, a new page format and a new format must be created, and format

actions must be defined for the new format-device type combination. To create new page formats

and formats, call Transaction and choose . To create a new page format,

choose . To create a new format, choose .

8/11/2019 BC305_EN_46B



© SAP AG 1999

Print controls are generic formatting tags used by the R/3 System in all types of documents,

including SAPscript forms and ABAP lists. Print controls are used to control operations, such as

changing fonts, adjusting line spacing, or printing bar codes. Print controls are usually inserted indocuments under program control (using a SAPscript driver or an ABAP report). Print controls can

also be inserted in SAPscript forms directly.

To display a list of standard print controls, call Transaction and choose .

Then choose .

Print controls are specific to each device type. During formatting of an output request, print controls

are converted to device-specific control sequences.

This example shows the print controls for device type ZASCII. These print controls were copied

from the original device type ASCIIPRI. You can make the required adjustments by changing the

control sequences.

To modify print controls for a device type, call Transaction and choose .

Then choose . Place the cursor on the device type you want to adjust, choose

, then make the necessary changes.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The character used to display thecopyright sign is #

# by SAP AG

Once all the required adjustments have been made to the non-standard device type, you can use it to

define output devices.

To test the new device type, call Transaction and choose → →

or choose → → The tool accessed by

this transaction generates test data that can be printed on the device.

If there is a problem with the printout, check the hexadecimal display for the spool request and verify

the characters and control sequences that are sent to the printer. To see the hexadecimal display for

an ABAP list, choose from the spool request display screen. To see a hexadecimal

display for a SAPscript document, the graphical display must first be deactivated. To deactivate the

graphical display, call Transaction , which displays the spool request list. Choose →

→ → , then display the spool request containing the

SAPscript document again.

Alternatively, you can switch on the debugger for an output device. Call Transaction andchoose Select the output device you want to create a log for and choose →

The log can be displayed at the output request in Transaction .

8/11/2019 BC305_EN_46B



© SAP AG 1999

306 BA copyright


306

No. Character

© = Hex A9

306 A9 copyright


To verify the characters and control sequences sent to the printer, perform the following:

1. Call Transaction (TemSe) and choose → → Enter the number of the spool request. Column displays the number of the character set in

which the document has been created.

2. Take the hex code (A9) of the character (©) to be checked, and call Transaction Choose

and enter the number of the character set found in step 1. Choose C →

→ Search for the hex code (in column ). The number specified in column

in the same line is the number of the SAP character (306).

3. Take the SAP character found in step 2 (306), and call Transaction . Choose , and

enter the number of the character set assigned to the device type of your printer Choose

→ → Search for the SAP character found in step 2. The 4byte code

specified in columns X1 to X4 is the hex code sent to the printer. This hex code must be adapted to

either:

• A hex code (in this example, BA) representing the character that the printer knows (©), or

• A 4 byte sequence as a replacement for the non-printable character (©), such as 43 4F 50 59 for

“COPY”.

8/11/2019 BC305_EN_46B



© SAP AG 1999

ExternalExternal

communicationscommunications

Fax, X.400, InternetFax, X.400, Internet

OtherOther

mail systemsmail systems Other R/3 SystemsOther R/3 Systems

SAPconnect is a standard interface for communication between R/3 Systems and external

communication systems. SAPconnect is the successor of the SAPcomm interface used in earlier

versions of R/3.

SAPconnect offers a standard communication channel for all communication systems. It enables the

R/3 System to access other communication systems, such as fax servers, X.400 MTA (message

transfer agent), internet mail nodes, and mail systems using RFC technology.

SAPconnect sends and receives messages, and handles status notifications. It supports all R/3

address formats, such as fax, X.400, SMTP, and SAPoffice.

To connect the R/3 System with external communication systems, external adapters are normally

required. However, the connection between R/3 Systems through SAPconnect does not require any

additional module.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Complementary communication system vendors need to develop an adapter in order to integrate their

systems to R/3 SAPconnect. SAP tests the connection of this adapter to R/3.

For more information about fax and mail solutions, see → →

→ → →

→ → → →

SAP provides an adapter to integrate the Microsoft Exchange Server messaging system. The SAP

Exchange Connector acts as a message interpreter between the Microsoft Exchange Server and R/3

SAPconnect receiving, converting, and transporting messages. Using this adapter, R/3 can make use

of existing Exchange Connectors for Internet mail or X.400, and additional connectors for faxing.

However, SAP does not certify any third-party fax connectors used through the Microsoft Exchange

Server.

SAPconnect is configured and monitored almost completely in the R/3 System, the only exceptionbeing the external adapters.

8/11/2019 BC305_EN_46B



© SAP AG 1999

In this example, the sender system is DEV, the recipient system is QAS.

This example shows how two R/3 Systems can exchange documents using SAPconnect. On the

sender system, an R/3 user creates a fax from SAPoffice. The user on the recipient system receives

the document as an SAPoffice inbox message.

The different R/3 components involved in this process:

• SAPconnect

• SAPoffice

• Address management

8/11/2019 BC305_EN_46B



© SAP AG 1999

To configure SAPconnect, you must first call Transaction and choose →

Transaction is displayed. Now choose → .

To enable fax communication, set the communication method SAPconnect to address type FAX.

Call Transaction and choose → . Choose , and

enter the value for address type FAX.

Once you return to Transaction , you will see that your changed settings are not yet displayed.

To refresh the display, restart Transaction .

For more information about customizing SAPconnect and SAPoffice, see SAP Note 92950

( ).

8/11/2019 BC305_EN_46B



© SAP AG 1999

A SAPconnect node:

• Is the logical view of an external communication system in R/3

• Can represent an e-mail system, a fax system, or another R/3 System

• Is required to transmit messages to an external system

In this example, a SAPconnect node is defined that represents the recipient R/3 System (QAS). This

node must also be defined on the sender R/3 System (DEV).

8/11/2019 BC305_EN_46B



© SAP AG 1999

To create a SAPconnect node, use the wizard: Call Transaction and choose → .

Specify the following values:

•

• : Name of the RFC destination with which the R/3 System is to communicate.

• : The type of communication supported for this node, such as fax,

X.400, Internet, or SAPoffice.

• Every node must be assigned the addresses that it can edit. A node is not usually

assigned individual addresses, but rather address areas. The send process only sends messages

with recipient addresses within one of the specified address areas to the node.

• : Define the internal SAP format (such as RAW or PDF)

• : Used only for SAPscript documents

• Country code for the node location. Allows node-specific fax number changes

for outgoing faxes.

•

•

• : Indicates that the node is active. Documents are sent not to nodes that are not in

use.

8/11/2019 BC305_EN_46B



© SAP AG 1999

In this example, the RFC destination used by the SAPconnect node is type 3 (R/3 connection)

because the communication partner is an R/3 System.

The R/3 user specified in the RFC destination for SAPconnect:

• Must be defined on the recipient system

• Needs the authorization profile S_A.SCON assigned to it

• Should be a user of type CPIC

In this example, the user who executes the RFC call on the recipient system is SAPCONN.

To define an RFC destination, use the wizard for the creation of the SAPconnect node or call

Transaction .

8/11/2019 BC305_EN_46B



© SAP AG 1999

One or more address areas can be assigned to each address type in a SAPconnect node. The

SAPconnect transmission process only sends messages to a node if their recipient address falls

within the specified address area.

This example shows address areas DE06227*, which is created for the address type , for node

FAXE. This means that node FAXE should process all faxes sent to country DE (Germany), area

codes 06227. An example of an address area for address type R/3 (communication with a remote

R/3 System) could be QAS:100:US*, where QAS is the target R/3 System ID, 100 is the client

number in the target system, and US* means all users starting with US.

The section of the address area specifies the list of document types that are

supported in the target system, such as SCR for SAPscript documents, or PDF for PDF documents.

Based on this list, the system tries to convert the document to be sent to one of the supported types.

If it cannot find a proper conversion routine, the document is rejected. SAP provides a set of modules

for converting document formats. To display this list, use Transaction and choose → .

The process of node determination is called . You can have overlaps between the address

areas of different nodes. Therefore, if more than one node qualifies for the transmission, the node for

which the address area contains more characters in the recipient address is chosen.

8/11/2019 BC305_EN_46B



© SAP AG 1999

In the sender system DEV, you must maintain the fax number of the users who can send faxes. To

maintain the fax number for a user, call Transaction and enter the number in the field

under . The country code is taken from the country specified for the users company.

In the recipient system QAS, the fax number given in the sender system must be assigned to the user

who you want to receive the document.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To display all the requests waiting to be processed, call Transaction and choose →

. The screen shows the requests that are in the queue for each address type.

The larger screen in this example shows that one FAX request is waiting to be processed.

To send documents to a connected communication service, a transmission process must be started.

For test purposes, you can start a transmission process in a dialog. To start a transmission process in

a dialog, choose from the screen of Transaction . In the dialog

box, specify the address type you want to process. This example shows how to start a transmission

process for FAX.

Periodic scheduling of a transmission background job is generally recommended for a production

environment. To schedule a transmission process in the background, call Transaction and

choose → → → , then specify the following values:

•

•

•

•

Once a request has been processed, it appears as or , depending on whether or

not the transmission was successful. The status screen also shows which node processed the request.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To analyze failed requests, display the error log. Choose → .

From the overview of send orders, you can also notify a sender that a request was incorrect or try to

send the incorrect request again.

8/11/2019 BC305_EN_46B



© SAP AG 1999

• To make the SAPconnect nodes marked for use in the visible, the data

collection method must be started. For details see → →

→ → →

→ .

• For a test run of the collection method use Transaction → → →

• To test if there is an active SAPconnect node for an , call Transaction

and choose → Specify the recipients address (FAX number, mail address).

To display a detailed log of the routing and address conversion, choose →

• To test if there is an active SAPconnect node for an , call Transaction and choose → → → To display

a detailed log of the routing and address conversion, choose → . This test must

always be performed in the receiving system.

• To trace both outgoing and incoming transmission requests, call Transaction and choose

→ →

8/11/2019 BC305_EN_46B



Note for these exercises, the course participants will be divided into two groups: will work in the (Client 200), unless otherwise stated. will work in the (Client 200), unless otherwise stated.

1.1 Create two identical local output devices in R/3: BC305_01 and BC305_02.Specify the following:

: BC305_01 and BC305_02

: ASCIIPRI

: Use the default value.

: Group A enter DEV, group B enter QAS.

: Use the default value.

: C :Direct operating system call (Windows NTprinter)

1.2 Create a pool device that includes the two printers created in exercise 1.1.

Fill in the relevant fields for defining a pool device.

1.3 Submit an output request to the device pool just defined. You can print the listof application servers using Transaction . Ensure the output is correct.

Check the output request list for the spool request generated, and make surethat only one output request is on the list.

1.4 Modify the device pool defined in exercise 1.2. to print to all devices in thepool.

1.5 Submit an output request to the device pool just changed. You can print thelist of application servers using Transaction . Ensure the output iscorrect.

Check the output request list for the spool request generated making sure thatthis time two output requests are on the list.

2.1 Create a logical spool server BC305 in the R/3 System. Use the dialoginstance for the mapping server and the central instance for the alternateserver. The instructor will help you with the instance numbers.

2.2 Using Transaction , view the logical server mapping information.

Discuss with your partner the hierarchy and the color coding in the diagram.2.3 Change the output device BC305_01 created in exercise 1.1. to use the

logical server created in exercise 2.1.

2.4 Submit an output request to the output device BC305_01. You can print thelist of application servers using Transaction . Ensure that an outputrequest has been created.

2.5 Shut down the application server used as the mapping server (dialoginstance) for the logical server defined in exercise 2.1.

Submit an output request again to the output device BC305_01. You can printthe list of application servers using transaction . Make sure the output iscorrect.

Display the mapping relationships for the logical server BC305 and check the

8/11/2019 BC305_EN_46B



new color for the mapping server.

Start up the application server that was shut down.

3.1 To activate the load-balancing feature, modify the logical spool server createdin exercise 2.1.

3.2. Submit 10 output requests to your printer BC305_01. Make sure you create anew spool request each time. You can print the list of application servers

using Transaction .Verify that your spool requests were processed by both the mapping and thealternate servers specified in your logical server.

4.1 Change the output device BC305_01 created in exercise 1. Turn on themonitoring flag.

4.2 Submit an output request to the output device BC305_01. You can print thelist of application servers using transaction . Make sure output iscorrect.

4.3 Open the and verify that your device is being monitorednow.

5.1 Copy the standard device type ASCIIPRI into the new device type ZASCIIPR.Make sure all the dependent objects are copied. Do not reference the originalobjects.

5.2 Modify the output device BC305_01 to use the non-standard device typecreated in step 5.1.

5.3 Your user BC305 received a SAPoffice mail with the title .

Print out this mail to printer BC305_01 in order to test the copyright sign

5.4 Check the printout to see if the copyright sign has been printed correctly.

Hint: If there is no printer in the classroom, a print file stores the printout. Youdo not need Operating System access to display this file. Instead, useTransaction and double-click the directory DIR_PRINTFILE. Group Adouble-click the print file DEV for the printer DEV. Group B double-click theprint file QAS for the printer QAS.

5.5 Determine the hex code of the copyright sign using the spool request created

in 5.3.5.6 What is the SAP character number for the copyright sign?

5.7 Copy the given character set 1105 used for your device type ZASCIIPR tocharacter set 9105, and change your device type ZASCIIPR to use thecharacter set 9105.

5.8 Change the copied character set 9105 and add the code for the copyright sign(SAP character as in 5.6.) by the four letters "COPY" (Hex . 43 4F 50 59).

5.9 Print out the test mail again and check the printout again using Transaction .

8/11/2019 BC305_EN_46B



For this exercise you need two R/3 Systems:

The system where you create the message will be called the source system(for group A the source system is DEV, for group B the source system isQAS).

The system that receives the message is called the target system (for group A

the target system is QAS, for group B the target system is DEV).Your user in the sending system is BC305. In the receiving system use userSAP.

6.1 Initial customizing for use of the FAX component.

Activate the FAX component for your source system and client 200.

6.2 Create a SAPconnect node called BC305 in the source system with thefollowing specifications:

: BC305

: Test

: Name of the destination created in the security chapter.

: Fax

: Code 0870, United Kingdom (GB0870*)

: All formats

. For SAPscript: POSTSCPT

: DE (that means fax server is running in Germany)

You should also define:

That the node is to be monitored by the Alert Monitor

That the node is ready for useThe node supports as , , and

6.3 Send a mail to the fax number in England (0870)608-4050 (SAP UK).

The number must be specified as follows: GB08706084050

6.4 In the target system, check the fax number for the SAPoffice user SAP. Howdoes the system determine the country code for this user?

6.5 Display the send queue and start the SAPconnect send process for faxes inthe source system.

6.6 Verify that the message has arrived by displaying the SAPoffice inbox of user

SAP client 200 in the target R/3 System.

7.1 Run the data collection method for the using Transaction .

7.2 Will step 7.1. be sufficient to always have up-to-date alert information aboutSAPconnect?

8/11/2019 BC305_EN_46B




1.1 To create an output device, run Transaction , and choose . In the screen displayed, choose then choose .

Fill in the following fields:

: BC305_01

: ASCIIPRI

: Select the central instance.

: Use the default value (standard printer).

In the tab : : Group A enter DEV, group B enter QAS.

: C :Direct operating system call (Windows NTprinter)

Save your output device definition, then repeat all the above steps for thesecond printer. This time, use the output device name BC305_02 . Use thesame device type you used for device BC305_01. Then exit Transaction.

1.2 To create a device pool, run Transaction , choosing . In

the screen displayed choose then choose .Fill in the following fields:

: BC305_POOL

: Use the same device type you used for the devices created instep 1.1

: Select the central instance.

: Use the default value (standard printer).

: P: Device Pool

Choose . On the device list enter the names of the printerscreated in exercise 1.1. Select the option . Choose.

Save your output device definition, then exit Transaction .

1.3 To print the list of application servers, run Transaction and choose . Then perform the following steps:

Specify the device pool created in exercise 1.2.

Specify the number of copies as 1.

Select .

Deselect .

Choose .

8/11/2019 BC305_EN_46B



Confirm the following dialog box.

A spool request should be generated by the system.

Check that your print request was successful.

To display the output request list for the spool request, use Transaction .Choose . Then select the spool request just submitted and choose . There should be only one output request on the list.

1.4 To modify the device pool, run Transaction and choose .

If you are in display mode, choose .

Double-click the device pool defined in exercise 1.2.

Then choose and select the option .

Then choose and save your changes.

Save your output device definition, and exit Transaction .

1.5 To print the list of application servers, run Transaction and choose

. Then perform the following steps:Specify the device pool created in exercise 1.2.


Select .

Deselect .

Choose .




To display the output request list for the spool request, use Transaction .On the screen displayed, choose . Then select the spool request justsubmitted and choose . This time there should be two outputrequests on the list, one for each output device in the pool.

2.1 To create a logical spool server, run Transaction and choose . In the screen displayed, choose , then choose .

Fill in the following fields:

: BC305

(Optional) Enter a brief description of the logical server.

: Use the default value

: Select this option

: Do not select this option

: Using F4, select the server with the dialog instance.

: Using F4, select the server with the central instance.

Save your spool server definition. Exit Transaction .

8/11/2019 BC305_EN_46B



2.2 To display the mapping information, run Transaction and choose . Position the cursor on the logical server you defined in exercise 2.1,then choose → .

A diagram showing the relationship between the logical server and the realservers (mapping and alternate) is displayed. The colors of the logical servershould indicate that this is a logical server with assigned spool service. Payspecial attention to the alternate server relationship (vertical lines). If it does

not appear, check your server definition. To get the latest configuration dataand the right color coding, choose .

Return to .

2.3 From , choose . If you arein display mode, choose . In the new screen displayed, double-clickthe output device BC305_01.

Position the cursor on the field and press F4. Select the logicalspool server defined in exercise 2.1.

Save the revised output device definition, and exit Transaction .

2.4 To print the list of application servers, run Transaction and choose . Then perform the following steps:

Specify the output device as BC305_01.


Select .

Deselect .

Choose .



To check that your print request was created, display the output request listfor the spool request using Transaction . On the screen displayed,choose . Then select the spool request just submitted and choose . There should be exactly one output request.

2.5 Make sure you are logged on to the central instance.

Run Transaction . Place the cursor on the dialog instance and choose → Answer the following dialog boxes with .

To verify that the instance has been stopped, choose .

To print the list of application servers, run Transaction and choose . In the screen displayed, perform the following steps:



Select .

Deselect .

Choose .

Confirm the following dialog box.A spool request should be generated by the system.

Check if your print request was successful. Because of the alternate server

8/11/2019 BC305_EN_46B



specified, you are still able to print to this output device.

To display the mapping information for the logical server, run Transaction and choose . Position the cursor on the logical server youdefined in exercise 2.1, and choose .

On the diagram shown, the mapping server should appear in dark red toindicate that the server is not available. The alternate server should appear ingreen, which indicates that this server is still available. Spool requests

directed to your logical server are now processed by the alternate server.Run Transaction . Place the cursor on the dialog instance and choose → .

To verify that the instance has been started, choose .

3.1 To modify the logical spool server created in exercise 2.1, run Transaction and choose .

If you are in display mode, choose .

In the new screen displayed, double-click the logical server created inexercise 2.1.

Select the option .

Save the modified spool server definition. Exit Transaction .

3.2. To print the list of application servers, run Transaction and choose . Then perform the following steps:



Select .Deselect .

Choose .


A spool request should be generated by the system. Note the spool requestnumber.

Repeat the steps listed above 10 times.

Then verify that both real servers have been used to process your spoolrequests as required by the load balancing mechanism. To do this, startTransaction and display your output requests. Double-click one outputrequest after another, and select the tab . In the field , the processing spool server is displayed. Note that when you usespool server load balancing, there are different spool servers for the outputrequests.

4.1 To modify the output device, run Transaction and choose . If you are in display mode, choose then double-click on theoutput device BC305_01.

Under , select the option .

Save the modified output device definition, and exit Transaction .

8/11/2019 BC305_EN_46B



4.2 To print the list of application servers, run Transaction and choose . In the screen displayed:



Select .

Deselect .

Choose .




4.3 To verify that your device is being monitored, run Transaction andexpand the tree. Double-click on

. Choose → → →

→ :

A device node should be displayed for your output device. Note: The node isusing the output device short name.

5.1 To copy a device type, run Transaction , and choose →

→ . Then specify the following fields:

: ASCIIPRI

: ZASCIIPR

: Do not select this option

Choose .

Choose .

5.2 To modify the output device, run Transaction and choose . If you are in display mode, choose then double-click theoutput device BC305_01.

Place the cursor on the field and press F4. Select the non-standard device type defined in step 6.1 from the list.

Save the modified output device definition, and exit Transaction .

5.3 To print out the SAPoffice mail you received, call Transaction . Double-click on the mail with the title .

Choose → .

Select and print to output device BC305_01.

5.4 Check the print out.

If there is no printer, check the print file. To do this, call Transaction anddouble-click the directory DIR_PRINTFILE. Now double-click the file DEV ifyou are in group A, and double-click the file QAS if you are in group B.

Display the last page of the print file. You will see that instead of the copyrightsign the number sign is displayed. This means that this ASCII printer is notable to print the sign.

8/11/2019 BC305_EN_46B



For the purpose of this exercise, we will replace this non-printable sign by thefour letters COPY.

5.5 To determine the hex code of the copyright sign, call Transaction andselect the spool request created in exercise 5.3. Since not all characters couldbe properly processed, the status of this spool request is set to .Choose → → .

Choose . The spool request is now displayed in Hex format.

Look at any of the copyright signs and note the two characters below it. In ourcase, the hexcode used is "A9".

5.6 To search for the SAP character number for the copyright sign, callTransaction in . Choose → .

Choose → → ... .

Enter and deselect .

Choose .

The SAP character for the copyright sign is 306.

5.7 To copy the character set 1105 to character set 9105, call Transaction

in . Choose → .

Go to and position the cursor on character set 1105. Choose

→

In the field enter 9105. Enter as the new shortname, and save your entries. As development class choose $TMP.

To assign this new character set to device type ZASCIIPR, call Transaction in . Choose and enter

ZASCIIPR. Choose and switch to if necessary.

In the area , replace all three 1105 entries by 9105.

5.8 To change the copied character set by adding the code for the copyright sign,call Transaction in . Choose → .

Go to and double-click on character set 9105. Choose →

In any line, in the column , enter (that is the SAP character found in5.6).

In the same line, enter 43 in column , 4F in column , 50 in column ,and 59 in column . Save your entries.

Now the SAP character 306 is represented as in the character set9105.

5.9 To print out the test mail, repeat the steps from 5.3 and 5.4.

You should now see COPY instead of the symbol # for the copyright signNote that the status of the spool request is now .

Note: This exercise is only used to demonstrate how to replace SAP

characters with printable characters. In real life, you would not replace onesingle character with multiple characters.

8/11/2019 BC305_EN_46B



For this exercise you need two R/3 Systems:

The system where you create the message will be called the source system(for group A the source system is DEV, for group B the source system isQAS).

The system that receives the message is called the target system (for group Athe target system is QAS, for group B the target system is DEV).

Your user in the sending system is BC305. In the receiving system use userSAP.

6.1 To activate the FAX component for your source system and client 200, callTransaction and choose . Then choose → → .

Change the entry for FAX from NONE to SAPCONNECT.

Save your settings, and provide the transport request.

6.2 To create a SAPconnect node, run Transaction and choose →

. Then choose → , and specify the following fields:

: BC305

: Test

Choose

: PARNTER.

Choose

: Select this field

Choose

: GB0870*

Choose

: Select all formats

Choose

. POSTSCPT

Choose

: DE (for Germany)Choose

Select ()

Choose

: Leave this field empty.

Choose

: Select this field

Choose

: Select this field

: Select , , and

8/11/2019 BC305_EN_46B



Choose

: Select

Choose

6.3 To send a mail to the fax number in England, call Transaction anddouble-click on and choose

Enter a title and a small text. Then choose →

In the field , select

In the field , specify the fax number with country code and withoutany special signs: GB08706084050 (SAP UK).

Then choose .

6.4 To check the fax number and country code for the SAPoffice user, log on tothe target system. Call Transaction and specify user SAP as the , then choose . Choose . Double-click .

The country code for this user is determined by the country code of theassigned company and must not be specified directly in the users fax number.

6.5 To display the send queue, call Transaction in the source system andchoose → .

Now you should see 1 document waiting to be sent

To start the SAPconnect send process for faxes in the source system, fromthis same screen, choose → , and select address type

6.6 To verify that the message has arrived, log on to the target R/3 System (client200, user SAP). Call Transaction and choose .

There should be one unviewed message. Choose . Themessage you sent from the source system should be on the list. Make surethe message is correct.

Log off from the target system.

7.1 To run the data collection method for the , callTransaction and choose → → .

7.2 Step 7.1. is sufficient to always have up-to-date alert information about

SAPconnect. Therefore, the data collection method must be configured to bealways started with every startup of the application server. Further details areexplained in the unit .

8/11/2019 BC305_EN_46B



© SAP AG 1999

The Computing Center Management System (CCMS) has an object-based monitoring architecture

that simplifies the task of monitoring a set of R/3 Systems. This monitoring architecture integrates

information from the entire R/3 environment and uses this data stream to present an easily-manageable overview of the condition of the R/3 Systems and their environment. The information is

displayed in a tree-based structure, called the Alert Monitor (Transaction ).

The Alert Monitor has two views:

• The , which shows the present situation of the system

• The , which shows the past situation of the system. This view is useful for

analyzing problems that occurred since the last system monitoring run.

Alerts are raised and displayed for each monitoring attribute if configurable threshold conditions are

met. To view alerts, select the monitoring attributes required and choose . The open

alert status for the entire tree is displayed if the monitor is switched to .

To analyze a problem situation, you can start an analysis tool for a specific attribute. To do this,

place the cursor on a tree element and choose

R/3 Release 4.6 is delivered with all the tool assignments required to monitor your R/3 System,

however, you can maintain additional tool assignments and threshold conditions.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Customizing is easy to perform in the CCMS. For each performance monitoring attribute node,

comparison values (threshold values) are defined. These values trigger an alert, whether they are

exceeded or not.

Four threshold values must be set. When to switch from status:

• GREEN to YELLOW

• YELLOW to RED

• RED back to YELLOW

• YELLOW back to GREEN

Ensure the thresholds, for example, from GREEN to YELLOW are set differently than the thresholds

from YELLOW back to GREEN, otherwise the monitoring attributes would switch back and fourth

to a state of alarm when they near the threshold value.

Monitoring attributes with the same physical or logical content can be grouped together in

Customizing (or attribute) groups. The threshold values set can be either specific to a monitoring

attribute or valid for all the nodes in an attribute group. This grouping of monitoring attributes

reduces the amount of work for Customizing.

In this example, the attribute group is displayed, which includes the hit ratio

attribute nodes, such as the program buffer, generic key, and single record buffer.

Ensure that you check if the default thresholds in the CCMS are appropriate for your system.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Attribute groups enable you to maintain a lot of monitoring attributes at the same time. The different

types of attribute groups in the CCMS are the:

• Performance attribute group

• Status attribute group

• Log attribute group

Depending on the type of attribute group, you can define the following:

• For a , the most important threshold to define is when to raise a

YELLOW or RED alert. You can also set a method of data processing. For example, you can

choose if only the last measured value of a performance attribute is relevant or the average over

the last 15 minutes. You can set a message class and standard message text, which will be

displayed if a YELLOW or RED alert is raised.

• The performance database stores performance data that is reported to the monitoring

architecture. As the performance database is constantly expanding, it is reorganized periodically

to clean up the data according to a reorganization plan. You can define your own reorganization

plan and assign it to an attribute group. For example, you can define how long data should be

held in a detailed state.

• The refer to messages. Instead of setting threshold values, you

can set filtering and displaying options for these groups.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Use Transaction to display or change attribute groups. To display a list of all attribute groups,

select and choose . Select an attribute

group, and choose .

Several versions can exist for each attribute group. The version is related to a properties variant. This

example shows the attribute group with the properties variant .

Under , you can set the thresholds for raising a YELLOW or RED alert. These

thresholds are valid for all MTEs of this attribute group, except the thresholds that are directly

assigned to an MTE.

Under , you can set the standard error message.

In some cases, it may be necessary to define your own attribute groups. Once you define an new

attribute group, you must assign the MTEs to that group.

For example, the attribute group collects the MTEs that show thepercentage that a file system is filled. For dedicated file systems, such as the database log file

system, a different threshold value might be set.

To create a new attribute group, choose → and select the appropriate

group type. For performance attribute groups, ensure that the display unit of the group is set correctly

(according to the unit of the MTE attributes), otherwise the new attribute group cannot be assigned.

8/11/2019 BC305_EN_46B



© SAP AG 1999

For each MTE, tree tools (or methods) with different tasks can be defined:

• The determines which data supplier is responsible for delivering the

data.

• The determines what should be done automatically (without user

interaction) in case of a YELLOW or RED alert.

• The determines which functions should be executed to analyze the alert.

A method can be assigned to individual MTES or to an MTE class.

The MTEs in the CCMS are pre-defined with standard methods. However, you can define your own

methods or change the assignment in the MTEs to suit your needs.

8/11/2019 BC305_EN_46B



© SAP AG 1999

11 1

7 5

8 4

210

There are two kinds of data suppliers that deliver new data to the monitoring architecture:

• , which are started by the monitored application. They run independently,

and are not scheduled in the Alert Monitor. You cannot predict when new data is available.

• , which are defined in and started periodically by the monitoring

architecture.

For each MTE, you can define a . If no collection method is set (entry

< >), either there is no data supplier connected with the MTE or an active data supplier

delivers the data. If there is a collection method set, it is the passive data supplier, which is regularly

triggered by the auto ABAP program . In the monitoring architecture delivered by SAP,

normally no changes are required to the data collection method.

Auto ABAPs are ABAP programs that are regularly triggered by program SAPMSSY6. This

program runs with a time period defined in the profile parameter rdisp/autoabaptime (the default

value is 300 seconds). Auto ABAPs (such as SAPMSSY8, which starts the data collection method)

run without a terminal, in dialog work processes, under the user context of user SAPSYS.

To display a list of auto ABAPs, choose → → →

(or call Transaction ), and then choose → → . To display

the reports that are triggered by SAPMSSY6, select a server and choose . For more

information, see SAP Note 16201.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Program SAPMSSY8 periodically checks if the data provided by the data suppliers fulfils the

threshold conditions for YELLOW or RED alerts set for the MTEs. If the conditions are met,

program SAPMSSY8 starts the actions defined as for these MTEs.

run automatically, without user interaction. Therefore, no dialog transactions

can be used. An can be:

• An

• A that has the interface defined in the sample function module

SALT_TOOL_REFERENCE_MODULE. For function modules, static parameter values can be

passed.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Use Transaction to define and maintain methods. To display a list of all methods defined, mark

, and choose . To define a new method, choose . To

maintain a defined method, choose .

This example shows how to maintain the that sends an e-mail when an alert

occurs. The name of the auto-reaction method is , and it represents the

execution of the function module SALO_EMAIL_IN_CASE_OF_ALERT. The content of the e-mail

is exactly the alert content shown in the Alert Monitor (Transaction RZ20).

Under , you can define how the method is executed and started up. The method can be

executed in dialog, background, or manually. For more information, see the 4.6A Release Notes

(under BC/ CCMS/MON, ).

Under , the following settings must be defined and SAPconnect must be configured for

R/3 mail (RML), for details see SAP Note 176492:

• SENDER: R/3 mail user in the format: <SID>:<client>:<SAPoffice user name>

• RECIPIENT: Shared distribution list existing in client 000 or R/3 mail user in the format:

<SID>:<client>:<SAPoffice user name>

• RECIPIENT-TYPE ID: The entry R indicates you have specified an R/3 mail user, the entry C

indicates a shared distribution list.

A method has to be before it can be used in the Alert Monitor (Transaction ). In the

example above, the method is released as an auto-reaction method.

8/11/2019 BC305_EN_46B



© SAP AG 1999

When an alert occurs, the Alert Monitor (Transaction ) guides you to the R/3 functions defined

as which will help you investigate the problem.

Because must be manually started by the administrator, dialog transactions can also

be used. If you use dialog transactions, you can specify on which R/3 System or R/3 instance the

transactions will run.

An can be:

• A

• An

• A that has the interface defined in the sample function module

SALT_TOOL_REFERENCE_MODULE. For function modules, static parameter values can be

passed.

• A

8/11/2019 BC305_EN_46B



© SAP AG 1999

Use Transaction to define and maintain methods. To display a list of all methods defined,

select , and choose . To define a new method, choose . To

maintain a defined method, choose .

This example shows how to define an for controlling the communication component

, which is Transaction .

Transaction is a dialog transaction. Therefore, under select .

A method has to be before is can be used in the Alert Monitor (Transaction ) In this

example, the method is released as an analysis method.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To change the method assigned to an MTE, go to the Alert Monitor, mark an MTE, and choose

. Select the folder and choose Under , you

can select one of the following:

• Select and specify the method to assign a method directly to an MTE.

• Select so that the methods are inherited from higher

level MTEs. For example, if all MTEs in a subtree use the same analysis method, you can assign

this method to the highest MTE of the subtree and pass the method (the method will

automatically be passed) down to all lower levels.

• Select so that MTEs with the same physical or logical

content are grouped together in MTE classes. For example, if all hit ratio MTEs are assigned to

the MTE class , the method can be assigned once to the MTE class (and is

active for all MTEs within the class where no assignment is set) instead of assigning each of

these MTEs a method individually. This simplifies Customizing.

8/11/2019 BC305_EN_46B



© SAP AG 1999

11 1

7 5

8 4

210

MTE classes enable you to maintain a lot of monitoring attributes at the same time. When creating

an MTE class, you must define the properties and the methods.

The properties you can define are:

• A description text

• The visibility level

• The monitoring attributes

The more important part of the MTE class definition is the assignment of the collecting, auto-

reaction, and analysis methods.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Use Transaction RZ21 to define and maintain MTE classes. To display a list of all MTE classes,

select Properties assigned to MTE classes and choose Display overview. To maintain an MTE class,

choose Edit data.

Several versions can exist for each MTE class. The version is related to a properties variant. This

example shows the MTE class R3BufferHitRatio with the properties variant Test.

Under Description text, you can set a message class and message number for a short text description.

To maintain a message, choose Tools → ABAP Workbench → Development → Programming

Environment → Messages (or call Transaction SE91). Message class RT is reserved for the CCMS.

Under Visibility level, you can choose between overview, analysis, and expert analysis. If you select

Overview, all the MTEs of this class are visible in all monitors. If you select Expert analysis, the

MTEs of this class are only visible if the monitor itself is set up to expert analysis level.

Under Properties only for monitor attributes, you can specify the severity of the alerts, which alerts

should be kept, when to start the data collecting tool, and when to raise alerts for the first time.

The severity is used to rank alerts that have the same importance. Among RED alerts, the RED alert

that has the highest severity is passed to higher tree levels, and is displayed in the Alert Monitor as

the most important alert. By default, the severity is set to 50 for most MTEs. You can change the

alert propagation by changing the severity accordingly.

When an instance is started, the hit ratio of the R/3 buffers are extremely poor because the buffers

are empty. Therefore, the alerts are not raised within the first 20 minutes (1,200 seconds).

8/11/2019 BC305_EN_46B



© SAP AG 1999

To display a list of all MTE classes and their method assignment, select

and choose . Select an MTE class, and choose .

Several versions can exist for each MTE class. The version is related to a properties variant. This

example shows the MTE class of with the properties variant .

For each of the three methods for data collection, there are three selections to choose from:

• An explicit method name. Before you can specify a method name, the method has to be

. The method will be assigned to all MTEs of this MTE class, however it can be

overwritten by an individual MTE.

• No method for MTEs of this class

• The method is passed from higher tree levels

8/11/2019 BC305_EN_46B



© SAP AG 1999

The Alert Monitor for R/3 Release 4.6 is delivered with stable monitoring templates that can be used

directly, which are predefined and fully customized views on the R/3 System. Ensure that you check

if the default threshold values are applicable for your system requirements.

There are monitors for the entire R/3 System and for specific areas of the system architecture, such

as for data archiving, security, communication and for the database. The MTEs displayed in these

SAP monitor templates cannot be changed, but they can be copied and the copy can be modified.

Sometimes only a subsystem of R/3 will be monitored. When you work with the R/3 Alert Monitor:

• You can use the predefined SAP monitor templates. Check if there is a specific template for the

part of the system that will be monitored, otherwise all the MTEs of the R/3 System are shown in

the SAP template .

• You can copy an SAP monitor template and modify it using Transaction . However, to do

this, you must first activate the maintenance function (under → ). To increase the clarity, you can define your own monitor set and put the copy of the

SAP monitor template into the new set. The attributes of a monitor set determine if the set is

visible for or modifiable by other users.

8/11/2019 BC305_EN_46B



© SAP AG 1999

If no appropriate SAP template is available, you can define a new monitor. Remember that a new

monitor means a new view on the known MTEs of a system. The thresholds of an MTE can be

customized only once and is valid in all monitors.

To create a new monitor, call Transaction and activate the maintenance function. Then mark

your monitor set and choose . All the MTEs known by the system are displayed, select the

MTEs you want for the new monitor. To change an existing monitor, from Transaction mark

the monitor, and choose . Note that SAP monitor templates cannot be changed.

When you save the new monitor, you can specify its name. To organize the structure of your

monitor, you can insert virtual nodes that are used as a description. These nodes are marked with a

special icon (a circle with a cross in the center).

Any MTEs can be aligned under virtual nodes. There are two ways to select MTEs:

• Under , all MTEs of all R/3 Systems that are known and running are shown.

Click the node to expand the tree, and mark the MTEs that should be included into the new

monitor. If an MTE on a higher tree level is marked, all the MTEs under this subtree are

automatically included. The result is a , which shows the selected MTEs.

• You can choose to determine –by predefined rules– which MTEs should be inserted.

The result is a , which shows all MTEs fitting the rules at the moment of

monitoring.

8/11/2019 BC305_EN_46B



© SAP AG 1999

In this example, a monitor is designed for showing all R/3 buffers on all R/3 instances that are

known and running at the moment the new monitor is created.

To create a static monitor, expand the tree under until you see the MTE . Select the buffer MTEs, and choose .

This new monitor shows all the MTEs that are aligned under the . This means, the program

buffer, generic, and single record table buffer, screen, CUA buffer are displayed.

The advantage of creating a static monitor is its simplicity. Only select what you want to see.

The disadvantage of creating a static monitor is that you can only select what is known and running

at the moment the new monitor is created. For example, if one of the R/3 instances is not running at

the moment the new monitor is created, none of the MTEs relating to this instance can be selected. If

new R/3 Systems are included into the monitoring architecture later on, they are not shown in the

static monitors that were already defined. Another disadvantage of creating a static monitor is that

you man have to select a lot of MTEs of a special MTE class, and you may forget to select some of

them.

8/11/2019 BC305_EN_46B



© SAP AG 1999

Instead of using static monitors, you can select MTEs dynamically, using rules. The MTEs that you

want are not marked explicitly, they are described dynamically. The monitor runtime environment

processes rules to make sure that a monitor that includes rules is updated periodically. Three rulescan be used for monitor design:

• : This rule creates virtual MTEs for R/3 Systems that have

been included in the Alert Monitor. The selection options include ALL (all available R/3

Systems); CURRENT (R/3 System where the Alert Monitor is running), and specific systems by

name. Use this rule to set up rule-based monitoring across one or more R/3 Systems. Rule MTEs

that you add below this MTE are interpreted for each system that you have selected.

• : This rule inserts monitoring functions by MTE class. The

<MTEclass> parameter lets you add monitoring functions by MTE type (such as CPU, response

time, and buffer hit ratio). The members of the MTE class are displayed as real nodes in the

monitoring tree.

• and

: Use these two rules in conjunction. When

you select the CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL rule, use the <MTEclass>

parameter to include the MTE class as a virtual node in the tree. You then select the

CCMS_GET_MTE_BY_CLASS_UNDER_CLASS rule. In the <ChildMTEclass> parameter,

specify the MTE classes that you want to monitor as real nodes in your monitor.

8/11/2019 BC305_EN_46B



© SAP AG 1999

In this example, a monitor is designed for showing all R/3 buffers on all R/3 instances that are

known and running at the moment the new monitor is created.

To create a rule-based monitor, choose and insert a rule node. The first rule is

CCMS_DEFINE_R3_SYSTEMS with parameter <ALL>, which delivers the names of all known

R/3 Systems. Place your cursor on this rule node, and click to insert another rule node

under the first one. The second rule is CCMS_GET_MTE_BY_CLASS. The first parameter of this

rule is fixed to <ALL> and is passed from rule CCMS_DEFINE_R3_SYSTEMS of the higher level.

For the second parameter, the MTE class must be selected.

This new monitor shows all the MTEs that are aligned under the . That is, the program buffer,

generic, and single record table buffer, screen, CUA buffer are all displayed. This is shown for all

instances of all R/3 Systems that are known and running at the moment of monitoring.

The advantage of creating a rule-based monitor is that the monitor shows all MTEs that meet the

rules each time it is used. The monitor is always up-to-date. It is also easy to include all MTEs of anMTE class.

The disadvantage of creating a rule-based monitor is that you must know how the rules are handled.

You can mix rule-based and explicitly selected MTEs in one monitor.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The Alert Monitor contains a lot of MTEs that each have special threshold settings and method

assignments. With the CCMS Monitoring Architecture, you can define several different setups for

the entire monitor. The monitor can be switched directly from one setup into another. These setupsare called .

A properties variant is a collection of settings for one or more MTEs in the Alert Monitor. The

advantages of properties variants are:

• The monitor can be directly adapted to a new R/3 System situation. For example, the settings for

the Alert Monitor might be set differently between day and night operating system mode.

Therefore, a properties variant can be linked to a specific operation mode.

• The properties variants can be customized and transported centrally to remote R/3 Systems.

• The properties variant SAP-DEFAULT includes SAP standard threshold settings and method

assignments. This variant cannot be changed or deleted. However, you can copy either the whole

variant or specific values in it to a separate properties variant, and then make changes to this

copy. SAP-DEFAULT can be used as a backup if you accidentally change the values provided

by SAP in the R/3 System.

Note: Each MTE class and each Customizing group exists in one version per properties variant.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To create your own properties variant, call Transaction and choose → →. Enter a name and description for the variant.

A properties variant hierarchy exists in the monitoring architecture, with the values contained in

SAP-DEFAULT at the bottom level. MTE values that have been changed by customers and stored in

an active properties variant are the top of the hierarchy. An additional layer in this hierarchy is the

, whose values should be used if the customer-defined properties variant

does not contain values for an MTE class. If, in turn, this properties variant does not contain values

for that MTE class, then the system uses the values contained in the SAP-DEFAULT properties

variant.

You can also specify the name of a manufacturer of a system management program that provides an

agent for logging on to the R/3 System and making use of the CCMS system management interfaces.

This variant is used if Customizing changes are made by an agent outside of the R/3 System.

To define Customizing group settings for the new variant, display the overview list of Customizinggroups using Transaction . Select and choose

. You can mark multiple Customizing groups and copy them into the new variant

by choosing → → . During the maintenance of a single Customizing

group, the values can be copied into a new variant by choosing → → .

Remember: Customizing group settings for properties variant SAP-DEFAULT must be first copied

into a new variant before they can be changed.

8/11/2019 BC305_EN_46B



© SAP AG 1999

To define MTE classes for the new variant, display the overview list of MTE classes using

Transaction . Select and choose . You can

mark multiple MTE classes and copy them into the new variant by choosing → → . During the maintenance of a single MTE class, the values can be copied into a new

variant by choosing → → .

To change the method assignment of MTE classes in certain properties variant, display the overview

list of methods assigned to MTE classes using Transaction . Select and choose . Select the desired MTE class and choose . The

properties variant can be changed using → → .

The settings of a properties variant becomes active when the variant is activated. To do this, call

Transaction and choose → → . All changes made in the Alert

Monitor (Transaction ) are stored in the properties variant that is currently active.

You can link properties variants to operation modes of your R/3 System. To define an operationmode, choose → → → (or call Transaction

). Then choose . Under , you can link a

properties variant directly to the operation mode. During an operation mode switch, the variant and

its settings becomes active.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The new monitoring architecture in the CCMS enables you to monitor other R/3 Systems. Alerts and

data from multiple systems can be displayed in a single monitor and can be captured by a single

monitor definition (this is automatically done in rule-based monitors). Systems across platforms andacross releases can be monitored, including 3.x Systems. The basis for multi-system monitoring is

the monitoring architecture in each of the systems to be monitored.

Multi-system monitoring is realized through a loose coupling of individual monitoring architectures

by means of RFC links. The monitoring architectures in the monitored systems remain independent.

Threshold settings and method assignment and execution is done in the monitored system. The

central system collects information as required from the remote systems that are known to it.

To include a remote R/3 System in a central monitoring system, use transaction and choose

→ Enter the remote R/3 System SID and

the name of an RFC connection that is properly defined in transaction and which points to the

remote R/3 System. Choose whether a specific instance or all instances of the remote system should

be included in the Alert Monitor. Choose .

If there is a valid user and password entry made in the RFC connection, no logon prompt appears

while opening the Alert Monitor. If this is not the case, you need to obtain authorization in the

remote system to collect the data.

Remote systems do not automatically appear in the SAP monitoring templates, although they are

rule-based. After copying the templates, you must change the parameter <CURRENT> to <ALL> in

rule CCMS_DEFINE_R3_SYSTEMS.

8/11/2019 BC305_EN_46B



© SAP AG 1999

The settings of the Alert Monitor are linked to the R/3 System. Remote systems can be monitored

centrally, but the Customizing of the monitor cannot. However, you can use properties variants to

define thresholds and methods, for example, in a central system once and distribute the completesettings to the remote systems. After the settings are activated in the remote systems, they are also

visible in the central monitoring system.

Once a new properties variant is defined and set up, you can transport its content. To do this, display

the variants overview using transaction (or choose → →

. The choose → . You can choose between the transport of:

• General properties of MTE classes

• Method assignment of MTE classes

• Performance, status, or log attribute groups

Note that the assignment of methods to MTE classes can be transported. The methods themselves arenot included in the change request. There is a transport connection for customer-defined methods

directly in the method definition screen of transaction : Select and choose

. Select the method that should be transported, and choose . Choose

to include the method definition (without the underlying ABAP program or function

module) into a change request.

After the import of the change request into the remote systems, the variants must be activated.

8/11/2019 BC305_EN_46B



© SAP AG 1999

For background processing, you can monitor the following:

• Aborted jobs

• Utilization and queue properties for the background server

• Number of background work processes per instance

• System log messages

For the analysis methods you can use:

• Transaction : Job overview

• Transaction : Work process overview

• Function module BP_SHOW_ABORTED_JOB for listing job logs

• Transaction : R/3 System log

8/11/2019 BC305_EN_46B



© SAP AG 1999

In the spool system, you can monitor the following:

• Utilization and queue properties for the spool service

• Processing groups, which include:

- Work processes used for administrative purposes

- Work processes, print jobs, and pages for regular operation

- Work processes, print jobs and pages for frontend output

• Output devices, which include:

- LPQ_Time

- Pages/Min

- Error messages• System log messages

8/11/2019 BC305_EN_46B



© SAP AG 1999

Before SAPconnect can be monitored, the data collection method must be activated. For details see

→ → → →

→ → .

To automatically start the data collection method, run Transaction choose → . A list of all method definitions is displayed. Select the method name by

double-clicking on it. Switch to change mode. On the tab page , select . Save your entries.

In the area of SAPconnect, you can monitor the following:

• The number of send orders that are waiting for processing by the SAPconnect send process

- If more than 250 orders are waiting, a warning is displayed (YELLOW). If more than 500

orders are waiting, an alert is displayed (RED). You can change these default threshold values

in the Alert Monitor. Each client is monitored separately.

• Errors that occurred during the data collection

- These alerts indicate problems in the confirmation of data to the Alert Monitor

• Operating status of external components

• System log messages

8/11/2019 BC305_EN_46B



© SAP AG 1999

The SAP CMMS Technical Expert Monitor contains the CCMS Self Monitoring monitor, which

reports on the status of the monitoring architecture and the Alert Monitor itself.

The self monitoring system shows whether the Alert Monitor has been able to:

• Start the data collection methods for which it is responsible (MTE for SAPMSSY8, the ABAP

program that periodically starts collection methods)

• Allocate and access the shared memory that it needs for collecting and managing data and alerts

• Establish RFC communication links to remote R/3 Systems and components

Some Alert Monitor methods (data collection methods and automatic reaction methods) can also

register problems and status in the self-monitoring tree. The self-monitoring tree also registers

whether a reorganizations of the list of completed alerts is recommended, in order to reduce the

storage needed in the database for these alerts.

To prevent completed alerts from taking up too much space in the database, the Alert Monitor

watches the amount of database storage used. If thresholds are exceeded, then the Alert Monitor

triggers alerts in the CCMS self-monitoring part of the Alert Monitor. You can delete old alerts

according to your specifications, which reduces the amount of database space used.

8/11/2019 BC305_EN_46B




1.1 Create your own monitor set BC305.

1.2 Copy the following into the monitor set BC305:

a. and from the SAP monitor templates to and

b. from SAP Business Communication to

c. from SAP CCMS Technical Expert Monitors to

2.1 Create your own properties variant.

Group A, name the variant .

Group B, name the variant

2.2 Activate your properties variant.

3.1 Define an analysis method using Transaction to analyze SAPconnectalerts.

Group A, name the analysis method .Group B, name the analysis method

3.2 All the MTEs that monitor outbound SAPconnect documents are members ofthe MTE class Therefore, there should be one uniqueanalysis method assigned to all MTEs of that class.

Assign an analysis method to the MTE class so that theanalysis method is active for all types of outbound documents of theSAPconnect tree.

, assign analysis method ZCONNECTDEV.

, assign analysis method ZCONNECTQAS.

The assignment of your analysis method to the MTE class should only bevalid for the properties variant ( or ) created inexercise 2.

3.3 In the Alert Monitor, check if Transaction is executed when starting theanalysis method for the node → →

→ .

4.1 Create the rule-based monitor FILESYSRULE. Use the rules

CCMS_DEFINE_R3_SYSTEMS and CCMS_GET_MTE_BY_CLASS tocreate the monitor.

8/11/2019 BC305_EN_46B



5.1 Create an auto-reaction method for sending an R/3 alert mail to SAPofficeuser BC305 in client 200 in your R/3 System. The execution mode should beset to .

, copy the auto-reaction method CCMS_OnAlert_Email toZCCMS_OnAlert_Email_DEV

, copy the auto-reaction method CCMS_OnAlert_Email toZCCMS_OnAlert_Email_QAS.

5.2 Assign your auto-reaction method created in exercise 5.1. to the MTE classFilesystemPercentageUsed and to your properties variant created in exercise2.

6.1 Change the threshold values of the attribute group that is related to the filllevel of the file system (MTE attribute Percentage_Used).

Decrease the thresholds in order to raise a RED alert.

The thresholds of the attribute group should only be valid the propertiesvariant you created in exercise 2.

6.2 When is the auto-reaction method executed? And how long does it take, ingeneral, for you to receive the mail in your SAPoffice inbox after the alert isvisible in CCMS?

Check the content of the mail.

7.1 Include your R/3 partner system into your monitoring architecture. Use theRFC destination .

, include system QAS.

, include system DEV.

7.3 Is the remote R/3 System visible in the rule-based monitor created in exercise4.1? If not, why?

7.4 Is the remote R/3 System visible in the monitors copied in exercise 1.2? If not,what can you do to make them visible?

8

The first part of this exercise is done by Group A. The second part of this

exercise is done by Group B.

8.1 :

Create a change request and containing your properties variant created inexercise 2.

Add the methods created in exercise 3 and 5 to the change request.

Release the change request.

8.2 :

Import the change request of exercise 8.1 into the quality assurance system.

Activate the imported variant.

Check the imported method definitions and their assignment and behavior in

8/11/2019 BC305_EN_46B



the Alert Monitor.

8.3 Do you think that the imported auto reaction methodZCCMS_OnAlert_Email_DEV also works in system QAS?

What would you have to do in QAS to make it work?

9.1 What is the prerequisite for SAPconnect nodes to report errors to the

?9.2 What is the prerequisites for the data collection method SAPconnect to

always provide the with current information aboutSAPconnect?

8/11/2019 BC305_EN_46B




1.1 To create your own monitor set, run Transaction . To activate themaintenance function, choose → .

Note: The maintenance function must be activated for all CCMS exercisesusing Transaction .

Choose .

Select

Choose

Specify the name of the monitor set: BC305

Choose

1.2 To copy the templates into the monitor set BC305, you must first expand thefolders (for example, the SAP monitor templates) and display the S and templates.

For all templates to be copied, perform the following:

Place your cursor on the template required and choose

In the dialog box displayed, in the field select monitor setBC305.

Copy the name for the new templates but add a Z at the beginning of thename (for example, Zsecurity)

Choose

2.1 To create your own properties variant, run Transaction and choose

→ → .

Choose

Specify the following:

: (TRAININGDEV for Group A, TRAININGQAS for Group B)

: Training BC305

Save your entries.

2.2 To activate your properties variant, run Transaction and choose → → .

Select the appropriate properties variant and

3.1 To define an analysis method, run Transaction . Select

from the field and choose . Then choose

8/11/2019 BC305_EN_46B



Enter the tool name (ZCONNECTDEV for Group A, ZCONNECTQAS forGroup B) and a short description.

Choose and select

In the field enter Transaction .

Choose and select

Choose and select .

Save your entries.

3.2 Note: If you do not know the MTE class name of an MTE, open the AlertMonitor, select the MTE in question, and choose . The MTE classname is displayed in the field .

To assign an analysis method to an MTE class, run Transaction . Select and choose in the field.

Choose .

In the field , enter .

In the field , select the appropriate properties variant(TRAININGDEV or TRAININGQAS) created in exercise 2.1.

In the fields and select .

In the field , mark , and enter the name of theanalysis method (ZCONNECTDEV or ZCONNECTQAS) created in exercise3.1.

Save your entries.

3.3 To check if Transaction is executed when the analysis method isstarted, run Transaction , expand the tree of your monitor set BC305and double-click on the node representing SAPconnect.

In the monitoring tree displayed, look for . Mark the node andchoose .

Transaction will be executed.

4.1 To create a new rule-based monitor in your monitor set, run Transaction . Place your cursor on your monitoring set and choose .

Then place your cursor on the node < choose ,select and

Select the rule CCMS_DEFINE_R3_SYSTEMS and . Set theparameter to and choose

Place the cursor on the node CCMS_DEFINE_R3_SYSTEMS choose select and

Select the rule CCMS_GET_MTE_BY_CLASS and press enter. Set theparameter to and choose

Save your entries and enter as the name for the new monitor.

8/11/2019 BC305_EN_46B



5.1 To create an auto-reaction method, run Transaction . Select and in the field , and choose .

Select and choose .

Enter the tool name (ZCCMS_OnAlert_Email_DEV for Group A, andZCCMS_OnAlert_Email_QAS for Group B) and choose . Go backand then choose .

Select your method and choose .

Choose .

Select and enter the following values for parameter.

SENDER <SID>:200:BC305

RECIPIENT <SID>:200:BC305

RECIPIENT-TYPEID R

Select and select .

Select and select

Save your entries.

5.2 All monitoring attributes are members of MTE class .

To assign an auto-reaction method to an MTE Class, run Transaction .

Select .

In the field choose .

Mark the MTE class and choose .

Choose → → and choose your properties

variant form exercise 2.1.

In the field , select .

, select the auto-reaction method ZCCMS_OnAlert_Email_DEV.

, select the auto-reaction method ZCCMS_OnAlert_Email_QAS.

Save your entries.

6.1 All monitoring attribute nodes of the MTE attribute Percentage_Used aremembers of the attribute group .

Note: In order to find out the name of an MTE´s attribute group, start the AlertMonitor, select the MTE in question, and choose . The name of theattribute group is displayed in the field .

To check the threshold values of the attribute group, run Transaction ,expand the tree of your monitor set BC305, and double-click the monitorFILESYSRULE.

Make sure that the monitor is set to .

Read the current value for the attribute Percentage_Used for any drive.

To maintain the threshold values of an attribute group in the active variant,select the MTE attribute and choose .

8/11/2019 BC305_EN_46B



Select and choose .

The system informs you that the values of the attribute group in the current properties variant will bechanged.

Decrease the thresholds to a value smaller than the current value in order toraise a RED alert.

Save your entries.

The new threshold settings are active for MTEs because you have changed the corresponding attribute group in the currentvariant.

6.2 The execution time and frequency of the auto-reaction method depends on itsdefinition.

To determine the definition, run Transaction and select and in the field and choose .

Double-click on the tool name ( for Group A, for Group B)

Choose

Depending on the selection in field , the following happens:

a) Automatic in dialog process (short-running program)

The auto-reaction method is executed using report SAPMSSY8, which runsevery 5 minutes under user SAPSYS in client 000 in dialog.

Advantage: Fast reaction (max waiting time 5 minutes for the run ofSAPMSSY8 + period of the SAPconnect sending process (in the trainingsystem 5 minutes are configured.))

Disadvantage: Long-running programs cannot be used as auto-reactionmethod since the R/3 instance parameter rdisp/max_wprun_time limits theruntime for dialog programs by default to 300 seconds.

b) Automatically in background (as job)

The auto-reaction method is executed in the background jobSAP_CCMS_MONI_BATCH_DP

Advantage: Long-running programs can be used as auto-reaction method.

Disadvantage: By default, this job runs every hour, so max. waiting time isone hour + period of the SAPconnect sending process.

c) Manually executable only

Used for the execution of transactions.

Since you defined as the execution mode inexercise 5.1, case a) applies here.

Wait a few minutes (max 10 minutes) before you check the content of yourSAPoffice inbox.

To check the content of your SAPoffice inbox, run Transaction . A

CCMS mail will appear.

8/11/2019 BC305_EN_46B



7.1 To include a remote R/3 System, you need an RFC connection. You can usethe RFC destination . This connection points to your partnersystem and is set up with a CPI-C user.

To include your partner system in your monitoring architecture, callTransaction and choose → .

Under , nter the R/3 SID of your partner system.

Under , enter .

Choose .

7.3 In exercise 4.1 you created a rule-based monitor. If the parameter is set to , the rule CCMS_DEFINE_R3_SYSTEMS shows all knownR/3 Systems

Therefore you do not have to change anything. The new remote R/3 Systemis displayed without any further action.

7.4 The remote R/3 System is not visible in the monitors copied in exercise 1.2.The SAP monitoring templates are normally created as rule-based.

SAP uses the rule CCMS_DEFINE_R3_SYSTEMS with the parameter set to . If you want to display all known remote R/3Systems, change this parameter to and choose .

8.1 :

To transport the information stored in your properties variant created in

exercise 2.1, start Transaction . Choose →

→

.

Choose → . Select properties variant TRAININGDEV. Under select all check fields.

Choose

To create a new change request, choose .

Enter a short description and save.

Choose

To add the methods created in exercise 3 and 5 to the change request, useTransaction . Select , and in the field choose .

Select your analysis method created in exercise 3.1, and choose .

Choose .

The system informs you that only the method definition will be transported,not the ABAP programs or function modules itself. Remember that self-developed ABAP functionality must be transported separately.

Choose

Now perform the same steps with the auto-reaction method created inexercise 5.1.

To release the change request, call Transaction and choose

8/11/2019 BC305_EN_46B



Position the cursor on the task and choose

Choose

Choose

Position the cursor on the change request and choose

8.2 :

Use Transaction to import the change request created by Group A into

your system:

Choose → .

Double-click on the queue

Choose

Position your cursor on the change request number created by Group A inexercise 8.1.

Choose →

Choose and confirm if necessary.

After the change request is successfully imported, check the following:

To check if the properties variant TRAININGDEV is visible, run Transaction and choose → → .

To check if the imported methods are visible, run Transaction , select , and choose :

To check if the imported threshold values are visible, run Transaction ,select , and choose Select the attribute group anddisplay the threshold values.

To activate the imported properties variant , run Transaction and choose → → .

To start the imported analysis method, run Transaction . Expand thetree of your monitor set BC305 and double-click on the node representingSAPconnect.

In the monitoring tree displayed, look for . Mark the node andchoose .

8.3 The imported auto reaction method ZCCMS_OnAlert_Email_DEV has therecipient parameter DEV:200:BC305. You would think that user BC305 in

system DEV receives the mail, but it does not. This is because SAPconnect inthe target system is not configured to send mails to the source system.

In order to send mails from QAS to DEV, you would have to change the RFCdestination and possibly the address space used in this SAPconnect node inclient 000.

9.1 The SAPconnect node to be monitored must support the CCMS Alert Monitor.

To check this, run Transaction and choose → .Double-click on the node name.

Field must be marked.

If this is not the case, go into , select the field, and save your

8/11/2019 BC305_EN_46B



entry.

9.2 The data collection method SAPconnect must be

To check this, run Transaction . In the field , mark and choose Double-click on the method . Choose In the field , the must be selected. If it is

not, go into , select the field, and save your entry. To check this, run Transaction and open the monitor .Expand the monitor tree. Place the cursor on a node on the lowest level of themonitor tree and choose → . A value must be specified inthe field . If it is not, go into , specify a value of 300 seconds, and save your entries.

8/11/2019 BC305_EN_46B



SMLG Tools → CCMS → Configuration → Logon groups

SCAT Tools → ABAP Workbench → Test → TestWorkbench → CATT

AL11 Tools → CCMS → Control/Monitoring →Performance Menu → Exceptions/Users →Exceptions → SAP directories

Tools → Administration → User Maintenance →Activity Groups

System → Services → Reporting

Tools → Administration → Administration → ClientAdministration → Special Functions → CopyTransport Request

Tools → Administration → Administration → Client

Administration → Client Transport → Client Export

Tools → Administration → Administration → ClientAdministration → Client Copy → Local Copy

Tools → Administration → User Maintenance →

Central User Administration → Logs for CentralUser Administration → Environment → Dist. mod.Assignment

Tools → Administration → User Maintenance →Central User Administration → Logs for CentralUser Administration → Environment → TransferUsers

Tools → Administration → User Maintenance →Central User Administration → Logs for CentralUser Administration → Environment → ModelSelection

Tools → Administration → Administration →Security Audit Log → Reorganization

Tools → Administration → Administration →Security Audit Log → Confirmation

Tools → Administration → Administration →Security Audit Log → Analysis

System → Services → Table Maintenance →Extended Table Maintenance

Tools → Administration → Administration →Network → RFC Destinations

Tools → Web Development → Web Repository

8/11/2019 BC305_EN_46B



Tools → AcceleratedSAP → Customizing → EditProject

Tools → Administration → User Maintenance →Users

Tools → Administration → User Maintenance →Activity Groups → Environment → Check Indicator

Tools → Administration → User Maintenance →Activity Groups → Environment →Installation/upgrade

Tools → Administration → User Maintenance →Activity Groups → Environment → MassGeneration

Tools → CCMS → Control/Monitoring →Performance Menu → Exceptions/Users →Exceptions → SAP directories

Logistics → Production → MRP → Planning →Total Planning → As Background Job

Tools → CCMS → Control/Monitoring → Job

Scheduling Monitor Tools → CCMS → Configuration → Operation

Modes/instances

Tools → Administration → Administration →Network → RFC Destinations → RFC → RFCgroups

Tools → CCMS → Jobs → Definition

Tools → CCMS → Jobs → Maintenance

Tools → CCMS → Jobs → Performance Analysis Tools → CCMS → Jobs → External Commands


Tools → CCMS → Jobs → Check Environment

Tools → CCMS → Configuration → ExternalCommands

System → Own Jobs

Tools

→

Administration→

Monitor→

Traces→

Developer Traces

Tools → Administration → User Maintenance →

8/11/2019 BC305_EN_46B


Users

Tools → Business Framework → BAPIDevelopment → Business Object Builder

Tools → CCMS → Control/Monitoring → Alert

Monitoring

Tools → Business Communication →Communication → SAPconnect

Tools → Business Communication → Office →Shared Office Settings


BC305_EN_46B

Documents

Transcript of BC305_EN_46B