sappress netweaver as abap system administration

Frank Föse, Sigrid Hagemann, Liane Will

SAP® NetWeaver AS ABAP System Administration

SAP system administration fundamentals

Bonn � Boston

ch00_FM_5112.indd 3ch00_FM_5112.indd 3 6/4/08 9:21:18 AM6/4/08 9:21:18 AM

Contents at a Glance

1 Architecture of SAP NetWeaver

Application Server ABAP ................................................. 25

2 Process Concept of SAP NetWeaver

Application Server ABAP ................................................. 63

3 Getting Started ................................................................ 153

4 Setting Up the System Landscape ................................... 181

5 Client Administration ...................................................... 209

6 Software Logistics ........................................................... 245

7 Maintaining Instances .................................................... 285

8 SAP Users and Authorizations ......................................... 315

9 System Monitoring .......................................................... 363

10 Tools for Creating and Analyzing ABAP Programs ........... 415

11 Monitoring Architecture .................................................. 439

12 Data Archiving ................................................................. 477

13 Data Distribution and Transfer ........................................ 499

14 Installation Concepts ....................................................... 537

15 Service and Support ......................................................... 555

A Control Questions and Answers ...................................... 577

B Important Transaction Codes ......................................... 593

C Profi le Parameters ............................................................ 599

D Menu Structures .............................................................. 607

E Glossary ........................................................................... 619

F References ........................................................................ 627

G The Authors ...................................................................... 629


7

Contents

Foreword ..................................................................................... 17Acknowledgments ....................................................................... 19Introduction ................................................................................. 21

1 Architecture of SAP NetWeaver Application Server ABAP ............................................ 25

1.1 Components of SAP NetWeaver AS ABAP ..................... 251.2 Client/Server Architecture in SAP NetWeaver ................ 271.3 Access over the Internet ............................................... 32

1.3.1 Internet Communication Manager (ICM) ............ 341.3.2 Integrated Internet Transaction Server (ITS) ........ 371.3.3 Standalone Internet Transaction Server ............... 38

1.4 Presentation Layer ........................................................ 391.5 Application Layer .......................................................... 441.6 Database Layer ............................................................. 511.7 Network ....................................................................... 541.8 Operating System ......................................................... 55

1.8.1 Directory Structure ............................................. 561.8.2 User ................................................................... 58

1.9 Tips .............................................................................. 591.10 Transactions and Menu Paths ........................................ 591.11 Additional Documentation ............................................ 591.12 Questions ..................................................................... 60

2 Process Concept of SAP NetWeaver Application Server ABAP ............................................. 63

2.1 Dialog Processing .......................................................... 632.2 Background Processing ................................................. 65

2.2.1 Concepts ............................................................ 652.2.2 Defi ning Background Jobs .................................. 682.2.3 Analysis .............................................................. 742.2.4 Analysis Functions .............................................. 762.2.5 Authorizations .................................................... 79


8

Contents

2.2.6 Maintenance Jobs ............................................... 802.2.7 External Interface .............................................. 832.2.8 SAP Central Process Scheduling by Redwood ...... 842.2.9 Tips .................................................................... 882.2.10 Transactions and Menu Paths ............................ 892.2.11 Questions ........................................................... 90

2.3 Updating ...................................................................... 902.3.1 Concepts of Updating ......................................... 912.3.2 Confi guration of the Update System ................... 952.3.3 Monitoring and Troubleshooting an Update ....... 972.3.4 Tips .................................................................... 1022.3.5 Transactions and Menu Paths ............................. 1032.3.6 Additional Documentation ................................. 1032.3.7 Questions ........................................................... 104

2.4 Lock Management ........................................................ 1042.4.1 Types of Locks .................................................... 1052.4.2 Lock Owners ...................................................... 1062.4.3 Enqueue Server and Lock Table .......................... 1082.4.4 Managing Lock Entries ....................................... 1132.4.5 Useful SAP Notes ............................................... 1162.4.6 Questions ........................................................... 116

2.5 Output Processing ........................................................ 1172.5.1 Basic Principles ................................................... 1172.5.2 Confi guring the Spool Work Processes ................ 1192.5.3 Confi guring Spool Servers ................................... 1212.5.4 Confi guring the Landscape of Output Devices .... 1262.5.5 SAPSprint Service ............................................... 1372.5.6 Analysis and Troubleshooting ............................. 1382.5.7 Authorizations .................................................... 1442.5.8 Tips ................................................................... 1462.5.9 Transactions and Menu Paths ............................. 1462.5.10 Questions ........................................................... 147

2.6 SAP Virtual Machine Container (VMC) .......................... 148

3 Getting Started ............................................................ 153

3.1 Starting SAP NetWeaver AS ABAP and Java ................. 1533.2 Stopping SAP NetWeaver AS ABAP and Java ................ 155


9

Contents

3.3 Logging the Startup Process .......................................... 1563.4 SAP GUI — The Graphical User Interface ....................... 1633.5 General Administration Tasks ........................................ 165

3.5.1 Status ................................................................. 1663.5.2 System Monitoring ............................................. 1663.5.3 System Log ......................................................... 1733.5.4 System Messages ................................................ 1733.5.5 Lists .................................................................... 1743.5.6 Table Maintenance ............................................. 175

3.6 Tips .............................................................................. 1773.7 Transactions and Menu Paths ....................................... 1773.8 Additional Documentation ............................................ 1783.9 Questions ..................................................................... 179

4 Setting Up the System Landscape ............................... 181

4.1 Tasks of a System Landscape ......................................... 1824.2 Initializing the Transport System .................................... 1864.3 Confi guring the Transport Management System ............ 190

4.3.1 Transport Domains ............................................. 1904.3.2 Transport Routes ................................................ 1974.3.3 Extended Transport Control ................................ 2014.3.4 QA Approval Procedure ...................................... 202

4.4 Transport Control Program tp ........................................ 2034.5 Tips ............................................................................. 2054.6 Transactions and Menu Paths ........................................ 2054.7 Additional Documentation ............................................ 2054.8 Questions ..................................................................... 206

5 Client Administration .................................................. 209

5.1 Default Clients and Users ............................................. 2105.2 Creating New Clients .................................................... 2135.3 Local Copying .............................................................. 2205.4 Remote Copy ............................................................... 2265.5 Client Transport ............................................................ 2295.6 Special Functions .......................................................... 2385.7 Tips .............................................................................. 239


10

Contents

5.8 Transactions and Menu Paths ........................................ 2425.9 Additional Documentation ............................................ 2435.10 Questions ..................................................................... 243

6 Software Logistics ....................................................... 245

6.1 Implementation Guide .................................................. 2456.2 Processing Objects ........................................................ 250

6.2.1 Change Requests ................................................ 2506.2.2 Processing Requests with the Transport

Organizer ........................................................... 2526.2.3 Transport Logs .................................................... 2636.2.4 Transport Organizer (Extended View) .................. 2696.2.5 Transport Tools ................................................... 270

6.3 Importing Transport Requests ....................................... 2706.4 Manual Operation of the Transport Control Program tp 2736.5 Installing Support Packages and Industry Solutions ....... 275

6.5.1 Installing Support Packages ................................ 2756.5.2 Installing Add-ons .............................................. 278

6.6 Tips .............................................................................. 2796.7 Transactions and Menu Paths ........................................ 2806.8 Additional Documentation ........................................... 2816.9 Questions ..................................................................... 282

7 Maintaining Instances ................................................ 285

7.1 Profi le Maintenance ...................................................... 2857.2 Operation Modes ......................................................... 2977.3 Control Panel ................................................................ 3047.4 Dynamic User Distribution ............................................ 3057.5 RFC Server Groups ....................................................... 3087.6 Tips .............................................................................. 3127.7 Transactions and Menu Paths ........................................ 3137.8 Additional Documentation ............................................ 3147.9 Questions ..................................................................... 314


11

Contents

8 SAP Users and Authorizations ..................................... 315

8.1 Basic Principles ............................................................. 3158.2 User Maintenance ......................................................... 316

8.2.1 Creating a User ................................................... 3178.2.2 License Data ....................................................... 3238.2.3 Changing Users and Mass Changes ..................... 3238.2.4 Logon and Password Protection .......................... 3248.2.5 Default Users ...................................................... 325

8.3 Authorizations .............................................................. 3268.3.1 Authorization Checks – Overview ....................... 3278.3.2 Authorizations and Authorization Objects .......... 3288.3.3 Authorization Profi les ......................................... 3308.3.4 Important Profi les in the System

Administration Area ........................................... 3318.3.5 Role Maintenance .............................................. 3328.3.6 Important Roles in the System

Administration Area ........................................... 3398.3.7 User Assignment and User Comparison ............... 3408.3.8 Transporting Roles .............................................. 3438.3.9 Upgrade Procedure ............................................. 3448.3.10 Troubleshooting and Traces ................................ 345

8.4 Personal Settings ........................................................... 3458.5 Internet Users ............................................................... 3468.6 Information About Users and Authorizations ................ 348

8.6.1 Information System ............................................ 3488.6.2 Security Audit Log .............................................. 349

8.7 Central User Administration .......................................... 3518.7.1 Setting Up the ALE Scenario ............................... 3538.7.2 Activating and Confi guring Central User

Administration ................................................... 3538.7.3 Deleting the Central User Administration ............ 3558.7.4 Administrating Users in the Central User

Administration ................................................... 3558.8 Directory Services ......................................................... 3578.9 Tips .............................................................................. 3578.10 Transactions and Menu Paths ........................................ 3588.11 Additional Documentation ............................................ 3608.12 Questions ..................................................................... 360


12

Contents

9 System Monitoring ...................................................... 363

9.1 Server and Process Overviews ....................................... 3639.2 User Overviews ............................................................. 3719.3 System Log ................................................................... 3739.4 Analysis of Runtime Errors ............................................ 3759.5 Trace Files ..................................................................... 3779.6 Lock Entries .................................................................. 3809.7 Performance Monitoring ............................................... 382

9.7.1 Administrative Principles .................................... 3829.7.2 Monitors ............................................................ 383

9.8 Database Administration ............................................... 3859.8.1 Tasks to Be Planned at Regular Intervals ............. 3859.8.2 Database Fill Level and Objects .......................... 388

9.9 Overview of Regular Tasks ............................................ 3899.10 Administration of the Integrated Internet

Transaction Server (ITS) ................................................ 3919.10.1 Parameter Tabstrip ............................................ 3929.10.2 Memory Statistics Tabstrip ................................ 3939.10.3 Template and MIME Cache Tabstrip .................. 3939.10.4 Mutex Locks Tabstrip ........................................ 3949.10.5 HTML Template Directory Tabstrip .................... 3959.10.6 Feature List Tabstrip ......................................... 3959.10.7 BHTML Runtime Tabstrip .................................. 395

9.11 Internet Communication Manager Administration ........ 3969.12 System Administration Assistant ................................... 4019.13 SAP NetWeaver Administrator (NWA) .......................... 4039.14 Tips .............................................................................. 4089.15 Transactions and Menu Paths ........................................ 4099.16 Additional Documentation ............................................ 4129.17 Questions ..................................................................... 413

10 Tools for Creating and Analyzing ABAP Programs ...... 415

10.1 The New ABAP Editor .................................................. 41510.2 The New ABAP Debugger ............................................. 420

10.2.1 The Technology of the New Debugger .............. 42110.2.2 The Interface of the New Debugger .................. 422


13

Contents

10.3 Runtime Analysis .......................................................... 42510.3.1 Initial Screen .................................................... 42710.3.2 Single Activity Trace (SAT) – Further

Development of the Runtime Analysis .............. 42910.4 Performance Trace ........................................................ 431

10.4.1 The User Interface of the Performance Trace ..... 43210.4.2 Creating a Performance Trace ............................ 43310.4.3 Analyzing Individual SQL Statements ................ 436

10.5 Tips .............................................................................. 43710.6 Transactions and Menu Paths ........................................ 43710.7 Additional Documentation ............................................ 438

11 Monitoring Architecture .............................................. 439

11.1 Alert Monitor ............................................................... 44011.1.1 Basic Principles ................................................. 44011.1.2 Components .................................................... 44211.1.3 Technical Implementation ................................. 445

11.2 Customizing the Alert Monitor ...................................... 45211.2.1 Integrating Remote Systems ............................. 45211.2.2 Creating Customer-Specifi c Monitors and

Monitor Sets .................................................... 45311.2.3 Specifi c Adjustment of Properties ..................... 455

11.3 Analyzing Alert Monitors .............................................. 46111.4 Setting Up a Central Monitoring-System (CEN) ............. 46211.5 Customizing Examples .................................................. 464

11.5.1 Analyzing a Log File .......................................... 46411.5.2 Auto-Reaction Method: Sending Email ............. 46811.5.3 Filtering the System Log ................................... 469

11.6 Tips .............................................................................. 47211.7 Transactions and Menu Paths ........................................ 47411.8 Additional Documentation ........................................... 47411.9 Questions ..................................................................... 476

12 Data Archiving ............................................................. 477

12.1 Archive Development Kit (ADK) ................................... 47812.2 Customizing .................................................................. 483


14

Contents

12.2.1 Cross-Archiving-Object Customizing ................. 48712.2.2 Archiving-Object-Specifi c Customizing .............. 48712.2.3 Basis Customizing ............................................. 49012.2.4 Application-Specifi c Customizing ...................... 491

12.3 Control and Evaluation ................................................. 49112.4 Tips .............................................................................. 49312.5 Transactions and Menu Paths ........................................ 49512.6 Additional Documentation ............................................ 49612.7 Questions ..................................................................... 496

13 Data Distribution and Transfer .................................... 499

13.1 RFC Connections .......................................................... 50013.2 Application Link Enabling ............................................. 507

13.2.1 Technical Basics ................................................ 50713.2.2 Close and Loose Coupling Using BAPIs ............. 51113.2.3 Confi guration ................................................... 51113.2.4 Monitoring and Analysis ................................... 518

13.3 Data Transfer ................................................................ 52013.3.1 Batch input ....................................................... 52113.3.2 Direct Input ..................................................... 52413.3.3 Fast Input/Call Transaction ................................ 52513.3.4 BAPI ................................................................. 52513.3.5 Legacy System Migration Workbench ............... 52613.3.6 Data Transfer Workbench ................................. 527

13.4 SAPconnect .................................................................. 52713.5 SAP NetWeaver Process Integration

(SAP NetWeaver PI) ..................................................... 53013.6 Tips .............................................................................. 53213.7 Transactions and Menu Paths ........................................ 53313.8 Additional Documentation ............................................ 53413.9 Questions ..................................................................... 535

14 Installation Concepts ................................................... 537

14.1 Preparations ................................................................. 53714.2 Installation with SAPinst .............................................. 53914.3 Post-Installation Actions ............................................... 544


15

Contents


15 Service and Support ..................................................... 555

15.1 Overview of SAP Service Marketplace ........................... 55615.2 SAP Solution Manager as a Collaboration Platform ....... 558

15.2.1 Services ............................................................ 56015.2.2 Monitoring ....................................................... 561

15.3 Confi guration of the Support Connections .................... 56515.3.1 Remote Connections to Customer Systems ....... 56515.3.2 SAProuter Program ........................................... 56615.3.3 Confi gure Users ................................................ 57115.3.4 Maintenance of Customer Data ........................ 571


Appendices .......................................................................... 575

A Control Questions and Answers .............................................. 577B Important Transaction Codes ................................................. 593C Profi le Parameters .................................................................. 599D Menu Structures .................................................................... 607E Glossary ................................................................................. 619F References ............................................................................. 627G The Authors ........................................................................... 629

Index ............................................................................................. 631


63

In this chapter, we discuss the different process types that are available with SAP NetWeaver AS ABAP. We explain the proper-ties of the process types and introduce the concepts related to the individual processes.

Process Concept of SAP NetWeaver 2Application Server ABAP

The following section introduces the basic process types of SAP NetWeaver AS ABAP and its architecture. You learn why there are differ-ent process types and which tasks they perform in particular. Each sub-section of this chapter describes a specific process type. You’ll find tips and frequently asked questions at the end of each section. As the conclu-sion to this comprehensive chapter, you will also be given a brief insight into the functions of the virtual machine container (VMC), although this itself is not an independent process type.

Dialog Processing2.1

Dialog processing mainly takes place within dialog work processes. These normally constitute the largest portion of work processes in an OLTP system. At least two dialog work processes in addition to the dis-patcher process are required for an independent instance.

Although all of the processes described in the following sections per-form specific tasks such as background processing, printing, or updating, dialog work processes deal with the basic load of all pending tasks. All requests made by a user online to SAP NetWeaver are processed by a dialog work process. Depending on the request, a suitable specific pro-cess such as the update process may also be included, if necessary. The following components are involved in processing a dialog request (see Figure 2.1):

174.indb 63 6/5/08 9:06:10 AM

64

2 Process Concept of SAP NetWeaver Application Server ABAP

EE The dispatcher work process (central control process)

Possibly the dispatcher queue (dispatcher process queue)EE

A dialog work processEE

Components in the shared memory of the application server (e.g., EE

buffers)

Frontend: SAP GUI

DispatcherDispatcherRequestQueue

Dialog Work Process 1

Internal Mem

ory

TaskHandler

DatabaseInterface

ABAPProcessor

DynproProcessor

Dialog Work Process 2

Internal Mem

ory

TaskHandler

DatabaseInterface

ABAPProcessor

DynproProcessor

Dialog Work Process n

Internal Mem

ory

TaskHandler

DatabaseInterface

ABAPProcessor

DynproProcessor

Shared Memory

Application Buffer Roll Area

• Factory Calendar•Dynpros•ABAP Programs• Tables•….

User Context-

User Context

User ContextRoll File

Roll-in Roll-outBuffer Accesses

Components Involved in a Dialog StepFigure2.1

If the dispatcher forwards a dialog request to a dialog work process, the task handler takes over the request in the dialog process. It decides whether the screen or ABAP processor should be activated and whether a database query may have to be executed using the database interface. The task handler also looks after the roll-in and roll-out of the user con-text. The user context contains authorizations and variable values, for example.

The work process also has access to different memory areas. We differen-tiate between memory areas that are exclusively available for the dialog

Components involved in dialog

requests

Heap memory and cross-process

memory

174.indb 64 6/5/08 9:06:10 AM

65

Background Processing 2.2

work process (heap memory) and memory areas that can be shared by all work processes (cross-process memory). Mode-specific data that is kept longer than for the duration of a process step is stored in the exclusively used memory. This data is automatically made available for the process at the beginning of a dialog step (rolled in) and saved for the process at the end of the dialog step (rolled out). This is data that characterizes the user (user context), such as authorizations, administration information and other data for the ABAP and dialog processor, which was collected in the dialog steps of the current transaction that were already carried out.

The shared user area contains various SAP buffers such as the factory calendar and screen, program, and table buffers.

Background Processing2.2

In addition to the dialog mode, reports can also be processed in the background in an SAP system. This is particularly interesting for long-running programs that don’t require any interactive input. This chapter focuses on the management of background jobs. We’ll show you how to schedule time-driven and event-driven background jobs and how to analyze flow traces.

Concepts2.2.1

In principle, you can also run all programs, which don’t require any explicit user dialog, in the background. This is particularly useful if the process to be performed is time-consuming and requires a lot of system resources and should therefore be carried out at a time when there is a minimal workload on the system. Performing the process online would block a dialog process for the entire duration and thereby indirectly impede other dialog users.

To prevent users from executing long-running reports interactively, you can define a runtime limit for the dialog steps. The default limit is 600 seconds. The processing terminates after this period has elapsed. You can set this limit in the system profile using the rdisp/max_wprun_time parameter. Background processing is not restricted in this way.

174.indb 65 6/5/08 9:06:10 AM

66


The automation of routine tasks for periodic completion is another obvi-ous option you can use. The SAP system provides the background service with its background work processes (also simply background or batch pro-cesses) for background processing. Unlike dialog processing, in which the dispatcher assigns the next available dialog process to each LUW (Logical Unit of Work – see Section 1.5, Application Layer), background process-ing consists of a fixed connection with exactly one background process during the entire execution. The system administrator or the user sched-ules the start time of the background job. The user can choose between time control and event control.

The time-driven approach involves defining a start time when you sched-ule the job. Each instance of the SAP system, on which background work processes are configured, has an active time-driven job scheduler that checks, at defined intervals, whether there are background jobs waiting to be processed. The descriptions of pending jobs are held in central database tables. The time-driven job scheduler is an ABAP pro-gram that is interpreted and processed within a selected dialog process. The scheduler automatically selects the specific dialog process when the SAP system is started. The time interval, after which the time-driven job scheduler becomes active, is configured to 60 seconds by default. The administrator can change this time interval as required in the instance profile using the rdisp/btctime parameter. The time interval between two job scheduler runs can cause delays when you start a job. You would therefore reduce the time interval if the delays were too great for your own requirements. However, if a possible delay when starting a job is not a crucial factor, you can increase the time interval. Nevertheless, the associated reduction in the frequency of runs of the time-driven job scheduler has hardly any effect on the system load.

In contrast to the time-driven job scheduler, the event-driven job sched-uler reacts to events. After an event is triggered (as discussed later), the event-driven job scheduler initiates the start of background jobs that are to start running when the event occurs. The event-driven job sched-uler is also processed by a dialog work process; you use the rdisp/btc-name = <host name> parameter in the standard profile of the SAP system (DEFAULT.PFL).

Time-driven job scheduler

Event-driven job scheduler

174.indb 66 6/5/08 9:06:10 AM

67


Parameters for Dialog or Background Processing

rdisp/max_wprun_time:EE Time in seconds, after which a dialog step termi-nates because the runtime has been exceeded.

rdisp/btctime:EE Time interval of the background job scheduler.

rdisp/btcnam:EE Instance for background processing.

The events to which you want the job schedulers to react must first be defined as events in the SAP system. A number of events are already deliv-ered by default with the SAP system. You can display an overview of these events in Event Maintenance (SM62). The events already included in the SAP system delivery are also called system events. They are frequently used for internal SAP control but can also be used by users for their own purposes.

Users can also use the same menu path to define their own events called user events. The event definition is initially nothing more than an entry in a table.

You can trigger an event in various ways:

Manually for test purposes using the context menu for an event in EE

Event Maintenance (SM62) (right-click Trigger• Event)

By using the BP_EVENT_RAISE function module from an ABAP pro-EE

gram within the SAP system

Using the EE sapevt external program

You can use sapevt to trigger an event in an SAP system from an external program. sapevt is available for executable programs in the SAP standard directory (see Chapter 1, Architecture of SAP NetWeaver Application Server ABAP). You can use it as follows:

sapevt <EventID> [-p <parameter>] [-t] pf=<profile>|name=<SAP system name> nr=<SAP system number>

The -t option initiates the writing of a dev_evt log file in the sapevt call directory. The -p option can transfer a parameter that determines an SAP module (e.g., Financials, FI). This means that an event can be assigned to an application area. This assignment is merely descriptive in nature.

System events

User events

Triggers

sapevt

174.indb 67 6/5/08 9:06:10 AM

68


For example, the

sapevt SAP_TRIGGER_RDDIMPDP name=QO1 nr=00

call triggers the SAP_TRIGGER_RDDIMPDP event in the QO1 SAP system.

Event control is used within the SAP system when transporting objects between SAP systems, for example. Transports performed using the tp transport control program are processed in several phases. Beyond the actual data import, you also often have to generate or activate the individual objects. The tp program therefore triggers the SAP_TRIGGER_RDDIMPDP event after the data import has been completed. In an SAP sys-tem, the RDDIMPDP job is always scheduled based on this event. When the SAP_TRIGGER_RDDIMPDP event is triggered, the RDDIMPDP job is executed automatically in the background.

Using this technology gives you greater fl exibility. You can’t always pre-dict when actions will be completed, therefore, it’s almost impossible to establish dependencies between background jobs. Event control creates new possibilities in this case.

Defining Background Jobs2.2.2

You use the Job Defi nition ( SM36) to set up background jobs (see Figure 2.2).

Job Defi nitionFigure2.2

tp

174.indb 68 6/5/08 9:06:11 AM

69


Planning background jobs is also often integrated directly into the appli-cations, for example, when you copy clients or perform a user master comparison. Depending on the application, the appearance of the screen templates for entering the job data may differ, or the application may predefine certain job properties already. However, the basic principles and options of background processing described in this chapter remain valid and can be applied to these specific cases.

Three important aspects are involved in defining background jobs:

General information such as job name, job class, and target hostEE

Information about the start time or about assigning a triggering EE

event

List of processing stepsEE

The general information is the starting point for defining a background job (refer to Figure 2.2). The job name you select should be as descriptive as possible because all logs and overviews that you’ll subsequently have to analyze are based on this job name. From a technical point of view, the name is irrelevant; it doesn’t need to be unique either.

The priority when executing a job is initially controlled by assigning the job to a job class. We differentiate between the following job classes:

A Highest priority EE

Time-critical jobs that ensure the functional efficiency of the SAP NetWeaver system.

B Medium priority EE

Periodic jobs that ensure the functional efficiency of the SAP NetWeaver system.

C Normal priority EE

The usual job class for SAP users.

System resources are assigned using these job classes. If a very high num-ber of Class C jobs are frequently waiting to be processed, which means that Class A and B jobs also have to wait for background processes to be released, the system administrator can use Operation Mode Mainte-nance (RZ04) to keep an n number of background processes available for processing Class A jobs. This configuration ensures that n background

General information

Job class

174.indb 69 6/5/08 9:06:11 AM

70


processes are always available for executing Class A jobs. Class B and C jobs must wait with the processing until at least n+1 processes are avail-able. The configuration is described in Section 7.1, Profile Maintenance, in Chapter 7 as part of the topic on maintaining operation modes.

In a distributed SAP system, you can assign the execution of a job to any SAP instance with a background service. In the context of background processing, this instance is referred to as a target server. If you don’t explicitly specify a target server, the first available background process will be selected when you execute the job.

The priorities for processing a request on a defined background server are as follows:

Job class A, target server specified1.

Job class A, no target server specified2.

Job class B, target server specified3.

Job class B, no target server specified4.

Job class C, target server specified5.

Job class C, no target server specified6.

If the pending jobs have equal priority based on the criteria mentioned previously, the queue time is used.

If you have defined a target server, this information is binding. If the tar-get server is not available when you want the job to start, a background work process of another instance won’t take over the processing. The job remains in the queue until the defined target server resumes the work, or the processing is explicitly moved to another server.

The output generated by an ABAP program is stored as a spool request in the SAP spool system. You can use spool list recipients to send the output to a user, which means that different people can manage a background job and analyze its results, for example. Because the output can be exten-sive, you should use this option with caution. For performance reasons, the length of an output list sent through SAPoffice is restricted to 1,000 lines. You specify the information about the print parameters themselves in the step definition.

Target servers

174.indb 70 6/5/08 9:06:11 AM

71


In another step, you must select the parameters that determine the start time. To do this, you select the Start Date button from the initial screen for the job defi nition. You can defi ne the start date using time data or as event-driven (see Figure 2.3).

The time data and the time zone used are based on the system time. In addition to specifying the start time directly, time-driven scheduling of jobs also enables you to schedule jobs periodically, as it can be useful for regular evaluations or maintenance jobs described later. You can select the time intervals here as you wish: in cycles of minutes, or hourly, daily, weekly, and so on. You can use the Restrictions function to defi ne differ-ences in the normal period, which is convenient for taking into account public holidays in the valid factory calendar. For time-sensitive jobs, you can defi ne a time after the elapse of which, these jobs must not be started any more.

Defi ning a Start Date and TimeFigure2.3

Instead of time-based control, you can also specify a defi ned event as the trigger. In particular, operation mode switching and the end of a

Start time

Start event

174.indb 71 6/5/08 9:06:12 AM

72


job are also defi ned as events to ensure that a background job can also be started as a follow-on job. You can use the Start status dependentoption to ensure that the job starts, provided the preceding job has been completed successfully. If the preceding job is canceled, the status of the dependent follow-on job is also set to Canceled, and the job is not executed.

If jobs with the After job, After event, or At operation mode start date can’t be started because no background work processes are available when the expected event occurs, they are earmarked to start at the earli-est possible date and then also started using the time-driven job sched-uler (see Figure 2.4).

Defi ning a Processing StepFigure2.4

174.indb 72 6/5/08 9:06:13 AM

73


As already mentioned, you can also run all dialog-free ABAP programs in the background. To do this, select the ABAP Program function. Enter the name of the ABAP program to be run and, if necessary, specify a language in which any log is to be generated. Many ABAP programs are controlled using variables. One example is the RSPARAM program. This program generates a list of all set instance parameters. A user can restrict the namespace of the instance parameters to be displayed before he runs the program. To run these types of programs in the background, you must create program variants. These variants represent a fixed allocation of values for program variables that is saved under a variant name. You define a variant in the ABAP Editor (SE38) by selecting Goto• Variants. You enter a variant name and the required parameter values here. You can then schedule the background execution of an ABAP program vari-ant defined in this way.

Figure 2.4 shows the scheduling of the RSPARAM ABAP program, for which a “TEST” variant was previously created to generate a list of all currently defined instance parameters. The list here is to be generated in English. You can configure the print output of this list using the Print specifications function.

SAP users with administrator authorization can use the External pro-gram option to run any programs from the SAP system at the operating system level. Parameters can be transferred; the name of the target host must be specified in this case. To execute the program, the SAPXPG rou-tine is started on the target host, and the calling SAP system then com-municates with this routine by RFC, using the ID of the specific SAPCPIC SAP user.

To enable you to use the SAP internal authorization mechanism and also use external programs to a limited degree, external commands are precon-figured extensibly. An external command consists of a logical name and an assigned external program with a possible allocation of parameters that can vary greatly, depending on the selected operating system. Before you use external commands in background processing, you must first define these using Create External OS Commands (SM49).

When you define a work step within a background job, the external command to be executed is determined using the name and the relevant

ABAP program

External programs

External commands

174.indb 73 6/5/08 9:06:13 AM

74


operating system, for example, UNIX. You can also allow users to add other parameters to the ones predefined. As with external programs, you must always specify the target host.

If you use external commands or external programs in the step list of a background job, for better integration, you can use the Control flags option in the step definition to define whether the data output and the error messages of the operating system program should be included in the step’s job log and whether a synchronous or an asynchronous execu-tion is required.

When you have entered the general information, start time, and individ-ual work steps of the background job, its definition is complete. Lastly, you must save the information you entered.

You can also query all described entries step-by-step using the job wizard. You can call the job wizard directly from the Job Definition (SM36).

To schedule background jobs, SAP also provides an interface (Application Programming Interface, API), in addition to the menu-driven method just described, which users can use in their own ABAP programs.

Analysis2.2.3

You analyze and monitor background jobs using Simple Job Selection (SM37) or Extended job selection (SM37C). You can filter jobs accord-ing to different criteria such as scheduling user, time period, job period, event, and status. You use the authorization concept to restrict the selec-tion criteria. If you have administrator authorization for background pro-cessing, you can display the jobs in all clients in the extended job selec-tion; otherwise, you can only display the jobs in the logon client.

A list of all background jobs is created based on the criteria you select.

The statuses of a job are described as follows:

Scheduled EE

The step definitions of the job have been saved; a start time has not yet been defined.

Job wizard

API

Statuses

174.indb 74 6/5/08 9:06:13 AM

75


Released EE

The job has been scheduled, and a start time has been explicitly set, or the job is waiting for an event.

Ready EE

The start time was reached, or the expected event has occurred; the job is waiting for system resources for the execution.

Active EE

The job is currently being processed.

Finished EE

The job was successfully completed.

Canceled EE

The processing had to be canceled due to a problem. The job could not be successfully completed.

You can double-click a selected job to display the execution details in its job log. In addition to the start and end times, the log contains valuable information about the causes of any canceled jobs.

All essential operations for background jobs are integrated into the job overview. These include the following:

Display scheduling data.EE

Cancel jobs with the EE Active status.

Delete jobs with the EE Scheduled, Released, Finished, or Canceled status.

Undo the release of one or more jobs; the job status changes to EE

Scheduled.

Compare several jobs. Specifying the general job information, step EE

definition, and start conditions.

Move to another server.EE

Interrupt an active job when problems are suspected (long-running EE

programs). This enables you to pause a job that is currently executing an ABAP program and analyze it using the ABAP debugger. The pro-gram will continue running again after you exit the debugger.

Check the status of EE active jobs.

174.indb 75 6/5/08 9:06:13 AM

76


Copy scheduled, released, or fi nished jobs; the new job gets the EE

Scheduledstatus.

In addition to this list overview, you can also use a graphical display, which not only enables you to display jobs but also to change and release jobs and check active jobs. You can access the graphical monitor from the Job Monitor ( RZ01) path (see Figure 2.5). The statuses of the jobs are displayed in color for a better overview.

Job Scheduling MonitorFigure2.5

You can also select Own Jobs ( SMX) or Job Defi nition ( SM36) • Own Jobs to display an overview of your own background jobs.

Analysis Functions2.2.4

Because, unlike dialog work, a user will often not immediately notice problems in his background processing , other analysis functions are available within the CCMS.

Information about the planned and actual start time and runtime of a background job are integrated into the Simple Job Selection (SM37). Major differences between the planned and actual start times indicate a bottleneck in the available background processes. This means that a long period of time elapsed after the job was released before a background process could be made available for the processing. If performance bot-tlenecks can be ruled out when scheduled background jobs are executed, the administrator should check the resources in this case and increase the

Runtime analysis

174.indb 76 6/5/08 9:06:13 AM

77


number of background processes, if necessary (rdisp/wp_no_btc param-eter in the instance profi les, or using profi le maintenance, see Section 7.1, Profi le Maintenance, in Chapter 7).

When you start an SAP system, it checks to see whether there are still jobs with theReady or Active statuses, which are not possible in this situ-ation. They are then set to the Scheduled or Canceled status. This type of zombie can occur if you shut down an application server before the job fi nishes and the status could be changed in the database.

To check whether the displayed job status matches the actual status or whether there is an inconsistency, you can select the critical jobs in the Simple Job Selection (SM37) and select Job • Check Status to fi nd any possible discrepancies. If necessary, you can reset the status of the jobs to Scheduled or cancel the actual jobs.

Some parameters from the background processing were integrated into the CCMS monitoring architecture. The Background processing monitor provides information about the average utilization of the background work processes, the server-specifi c length and average length of the wait queue for jobs that are ready to be started but can’t be processed due to the lack of a background server, and the number of canceled jobs (see Figure 2.6).

Alert Monitoring in CCMSFigure2.6

Zombies

Status check

Background processing alerts

174.indb 77 6/5/08 9:06:14 AM

78


You can use the Background Control Object Monitor ( SM61) to check that the controller is working correctly in background processing. This monitor enables you to check important components of background pro-cessing — such as time-driven and event-driven job schedulers, zom-bie cleanups, the start of external programs, and switching of operation modes — and use additional trace outputs to analyze them.

Control Object MonitorFigure2.7

You can perform a comprehensive analysis of all aspects of background processing using the Analysis of Background Processing ( SM65). In par-ticular, this tool enables you to fi nd and correct inconsistencies in the database tables for job control. Figure 2.8 shows an example of the out-put from this tool.

Control object list

Analysis tool – background processing

174.indb 78 6/5/08 9:06:15 AM

79


Analysis LogFigure2.8

Authorizations2.2.5

Authorizations control which actions a user is allowed to perform in background processing . Table 2.1 provides an overview of the most important authorizations in this area. All users are allowed to sched-ule, cancel, delete, and check the status of their own jobs without spe-cial authorization. However, special authorization is required to do the following:

Manipulate a job that was scheduled by another user.EE

Display the job log.EE

Display a spool request generated by a background job.EE

Release a job for execution.EE

Use an external command.EE

174.indb 79 6/5/08 9:06:15 AM

80


Unlike dialog processing, no passwords are checked in the background operation. The SAP users involved simply have to be created and not locked in the current client.

Authorization Description

S_BTCH_ADM Batch administration.

S_BTCH_JOB Operations with client-dependent background jobs.

Possible values:

DELE – Deletes jobs of other users.

LIST – Displays spool lists of other users.

PROT – Displays logs of other users.

RELE – Schedules own jobs and releases them for execution.

SHOW – Shows job details of other users.

You can use the Job Group field to restrict the authorization to selected job names.

S_BTCH_NAM Uses an explicit background user.

S_DEVELOP Interrupts jobs.

S_LOG_COM Executes external commands.

Required parameters:

COMMAND – Name of logical command.

OPSYSTEM – Operating system.

HOST – Name of target system.

S_RZL_ADM CCMS system administration.

S_ADMI_FCD System authorization for special functions.

Authorizations for Background ProcessingTable2.1

Maintenance Jobs2.2.6

The system administrator is responsible for performing certain jobs at regular intervals to ensure the functional efficiency of his SAP system. For example, maintenance jobs delete tables that are no longer required or collect statistical data for analyzing the performance of the system. Table 2.2 provides an overview of the most important programs. Other

174.indb 80 6/5/08 9:06:15 AM

81


jobs may be required, depending on the applications used or on your own applications.

Recommended Job Name/Description

ABAP Variant Interval

SAP_COLLECTOR_FOR_ PERFMONITOR

EE Collects general statistical data for analyzing the performance of the SAP system.

Cross-client.EE

Schedules in client 000 as EE

DDIC.

RSCOLL00 No Hourly

SAP_COLLECTOR_FOR_ JOBSTATISTIC

Collects statistical data EE

for evaluating the average runtime of periodically executed jobs.

Cross-client.EE

RSBPCOLL No Daily

SAP_REORG_JOBS

EE Deletes all logs of success-fully executed jobs. System administrator can use vari-ants to define how many days must elapse before a log is to be deleted.

Cross-client.EE

RSBTCDEL Yes Daily

SAP_REORG_JOBSTATISTIC

EE Cleans up the runtime sta-tistics of background jobs.

All objects older than the EE

specified date are deleted.

Cross-client.EE

RSBPSTDE Yes Monthly

Important Maintenance JobsTable2.2

174.indb 81 6/5/08 9:06:16 AM

82




SAP_REORG_BATCHINPUT

EE Deletes processed batch input sessions and their logs as well as logs that no longer have any sessions.

Client-specific.EE

RSBDCREO Yes Daily, but at times when there is no batch input activity

SAP_REORG_SPOOL

EE Deletes obsolete spool objects.

Client-specific.EE

RSPO0041/RSPO1041

Yes Daily

No standard name.EE

Deletes spool lists that EE

remain from canceled background programs.

Consistency check of spool EE

tables.

Cross-client.EE

RSPO0043 / RSPO1043

Yes Daily

SAP_REORG_ABAPDUMPS

Deletes runtime error EE

entries (short dumps).

Cross-client.EE

RSSNAPDL Yes Daily

SAP_REORG_PRIPARAMS

Reorganizes print param-EE

eters.

Cross-client.EE

RSBTCPRIDEL No Monthly

SAP_CCMS_MONI_BATCH_DP

System monitoring.EE

Client-specific.EE

No standard name.EE

Implements transport EE

requests.

RSAL_BATCH_ TOOL_ DISPATCH ING

RDDIMPDP

No Hourly

Event- driven

Table2.2 Important Maintenance Jobs (Cont.)

174.indb 82 6/5/08 9:06:16 AM

83




EU_PUT

Administration job for EE

updating object lists and navigation indexes.

Cross-client.EE

SAPRSLOG Daily

EU_REORG

Administration job for EE

updating object lists after a transport.

Cross-client.EE

SAPRSEUT Daily

Table2.2 Important Maintenance Jobs (Cont.)

For more information about the properties and parameters of these jobs, refer to the documentation of each individual program. You use the ABAP Editor (SE38) for this purpose. Enter the program name and select Documentation • Display.

You can schedule all of the preceding jobs individually or automatically with standard parameter settings by choosing Job Definition (SM36) • Standard Jobs.

In addition to the maintenance jobs related to the Basis component, application-specific reorganizations can also improve the performance of the system. One important example is the SBAL_DELETE report for delet-ing the application log.

External Interface 2.2.7

You can use the SAP-BC-XBP interface to integrate SAP background jobs with external job management systems. The supported functions are listed here:

Defining jobsEE

Changing, editing, and deleting jobsEE

Starting jobs EE

SAP-BC-XBP

174.indb 83 6/5/08 9:06:16 AM

84


Canceling active jobsEE

Accessing job information (status, log files, etc.)EE

This interface is also used by the new SAP Central Process Scheduling by Redwood (SAP CPS) tool described in the following section.

SAP Central Process Scheduling by Redwood2.2.8

In cooperation with the software manufacturer, Redwood, SAP provides (with SAP NetWeaver 2004 SP12) SAP Central Process Scheduling by Redwood as an external job scheduling tool that enables you to execute and monitor time-driven processes in the complex SAP Central Process Scheduling by Redwood system landscape.

This enabled SAP to react to new requirements, some examples of which are as follows:

Using SAP NetWeaver as the integration platform, a cross-component EE

tool that supports both AS ABAP and AS Java is required for automat-ing processes.

More and more business processes run on a time-driven or event-EE

driven basis.

The conventional tool for planning background jobs in the SAP envi-EE

ronment, Transaction SM36 (Job Definition), has its limitations (e.g., defining job chains across systems) and can therefore no longer com-pletely meet today’s requirements.

In contrast, the external SAP Central Process Scheduling tool offers sev-eral new functions that facilitate the administration of company-critical business processes centrally and across systems in SAP and non-SAP environments. Realtime-driven and event-driven functions form the basis for this.

SAP CPS is available in two versions: basic and full.

The basic version of SAP CPS is available at no extra cost to all SAP cus-tomers with an SAP NetWeaver license. SAP CPS provides the central administration point for defining, controlling, and monitoring jobs of an ABAP system landscape.

Basic version

174.indb 84 6/5/08 9:06:16 AM

85


However, you can’t use it to schedule and manage processes from third-party applications, operating system commands, and database jobs.

The full version can be licensed separately and provides additional options beyond the functions mentioned previously, such as schedul-ing and managing background jobs for many non-SAP systems, starting activities at the operating system level, a wide range of options for the load distribution of background jobs, and many more.

Table 2.3 shows an overview of the range of functions in the basic and full versions.

Function Basic Version

Full Version

Schedules ABAP programs as a job (also in older SAP releases up to 3.1)

Yes Yes

Schedules event-driven jobs within SAP systems Yes Yes

Defines, manages, and controls jobs from a central administration interface

Yes Yes

Uses calendars Yes Yes

Uses alarms Yes Yes

Models complex jobs with a graphical user interface Yes Yes

Generates reports and forecasts Yes Yes

Monitors job logs and spool lists from a central administration console

Yes Yes

Uses predefined job chains Yes Yes

Executes and manages jobs in non-SAP systems No Yes

Starts activities at the operating system level No Yes

Configures several process servers for load distribution and system stability

No Yes

Creates, plans, and executes database jobs, for example, backups

No Yes

Supports adaptive computing environments No Yes

Range of Functions in VersionsTable2.3

SAP CPS is currently available as a standalone solution (see Figure 2.9).

Full version

174.indb 85 6/5/08 9:06:16 AM

86


SAP System forCentral Monitoring

Process Managerfor Web

Oracle DB

Job Repository

Process Server

Event-Driven

Non-SAP System

App

ABAP Systems

Basic

SAP App

OS

Browser RedwoodExplorer

CPS ArchitectureFigure2.9

For the CPS architecture, a standalone solution means the following:

The core element, the process server, is installed separately.EE

The process server requires a separate Oracle database for saving the EE

job repository; an Oracle runtime license is required for this.

An existing Oracle database, for example, for an SAP NetWeaver sys-EE

tem, can be used as the database for the job Repository; no additional Oracle license fees are incurred in this case.

An alternative database system is not supported.EE

The process server can be installed on all operating systems supported EE

by SAP.

The Redwood Explorer is used as the user interface; it connects to the EE

process server via HTTP or OracleNet.

The process manager for the Web should be deployed in an SAP EE

NetWeaver AS Java for maintenance reasons. The Redwood Explorer

174.indb 86 6/5/08 9:06:16 AM

87


or any browser can connect to the process server by HTTP, albeit with restricted functions.

One approach is to change the architecture of SAP CPS to an extent that it no longer is a standalone solution but instead is fully integrated into SAP NetWeaver (see Figure 2.10). This solution has been available since March, 2008.

In the integrated version of SAP CPS, the job Repository moves from the previous standalone Oracle database to the database of the SAP NetWeaver system. The biggest advantage here is that you now no lon-ger have to save the job Repository exclusively in an Oracle database. You can use all operating systems and database combinations supported by SAP NetWeaver. The process server is deployed as a service in an SAP NetWeaver AS Java. There will no longer be an independent user inter-face; a browser-based user interface integrated into SAP NetWeaver AS Java will be provided instead.

Non-SAP System

App

ABAP Systems

Basic

SAP App

SAP NW JAVA

SAP App

OS

SAP System forCentral Monitoring

Note: Scheduler also runs on a single java stack!

RedwoodProcess Server

CEN

Automation

JXBP

XBP

Web-BasedUI

CPS Architecture of Integrated VersionFigure2.10

Integrated version

174.indb 87 6/5/08 9:06:17 AM

88


Tips2.2.9

Defining jobsEE , specifying a target host If you often use job definitions where you specify a target server, you must make sure to modify the job definitions when there are configu-ration changes. For example, this applies when:

You move an application server to other hardware (server name EE

changes).

You change the distribution of work processes when defining an EE

operation mode.

Deleting EE jobs with the Scheduled status that are no longer current When you display the current job queue in the Simple Job Selec-tion (SM37), the checkbox for the Scheduled job status is not selected by default, which means that the administrator may not notice jobs with this status that are no longer required. Users also often overlook the Or after event checkbox, which means that event-triggered jobs won’t be displayed.

Scheduling jobs using a non-generic user EE

When you schedule periodic jobs that will run over a long period, it makes sense to assign the individual steps to generic background users. This helps you to avoid problems that occur when users, whose accounts were used to schedule jobs, are deleted.

Minimum number of processes EE

You must configure at least two background work processes for the transport system, even if you don’t want to use any background processing.

Moving the start times of individual, time-driven job schedulers EE

If you use several instances with background work processes, it may be useful to set the rdisp/btctime parameters in the instance profiles to different values to achieve a better load distribution.

Problems with self-scheduling periodic jobs with a limited start time EE

When you use periodic jobs that reschedule themselves at the end of a run and define a time after which they can no longer be started, you may not be able to start these jobs anymore following a long system shutdown. You must monitor these jobs manually.

174.indb 88 6/5/08 9:06:17 AM

89


Transactions and Menu Paths 2.2.10

ABAP Editor: SAP Menu • Tools • ABAP Workbench • ABAP Editor (SE38)

Analyzing background processing: SAP Menu • Tools • CCMS • Jobs • Check Environment (SM65)

Creating external operating system commands: SAP Menu • Tools • CCMS • Configuration • External Commands (SM69)

Maintaining operation modes: SAP Menu • Tools • CCMS • Configura-tion • Operation Modes/Instances(RZ04)

Own Jobs: System • Own Jobs (SMX)

Simple job selection: SAP Menu • Tools • CCMS • Jobs • Maintenance (SM37)

Extended job selection: SAP Menu • Tools • CCMS • Jobs • Maintenance • Extended Job Selection (SM37C)

Triggering events: SAP Menu • Tools • CCMS • Jobs • Trigger Event (SM64)

Maintaining events: SAP Menu • Tools • CCMS • Jobs • Maintain Event (SM62)

External operating system commands: SAP Menu • Tools • CCMS • Jobs • External Commands (SM49)

Background control object monitor: SAP Menu • Tools • CCMS • Jobs • Background Objects (SM61)

Job definition: SAP Menu • Tools • CCMS • Jobs • Definition (SM36)

Job monitor: SAP Menu • Tools • CCMS • Control/Monitoring • Job Scheduling Monitor (RZ01)

Performance analysis: SAP Menu • Tools • CCMS • Jobs • Performance Analysis (SM39)

174.indb 89 6/5/08 9:06:17 AM

90


Questions2.2.11

Which transaction can you use to analyze job logs?1.

a. SE38

b. SM37

c. S000

Which external programs can you use to trigger events in the SAP 2. system?

a. sapevt

b. sapxpg

c. sapstart

d. spmon

What does the Ready status mean for a background job?3.

a. The job scheduling was completed and saved.

b. The job was run and is ready for printing the log.

c. The job is waiting for system resources so that it can begin running.

Updating2.3

Each change by an SAP transaction ultimately results in an update on the database. The term update means the implementation of changes in the database within the SAP environment. The SAP update system usually performs an update asynchronously when you enter or change data. This system ensures that the changes within an SAP LUW are con-sistent. Special features for monitoring and troubleshooting an update are explained next.

The update system is a central component of the SAP NetWeaver AS ABAP. However, it’s not an independent system but is instead always to be considered in connection with other services of the SAP system such as dialog, background, and, in particular, enqueue services. The update works closely with these services.

174.indb 90 6/5/08 9:06:17 AM

91

Updating 2.3

In the SAP system, a business process is mapped to an SAP LUW that can consist of several screen changes. This dialog or background process-ing causes a data change that must only be implemented completely on the database (in other words, with all changes from the LUW) or not at all. The SAP update system therefore ensures that changes are first written to the database when the SAP LUW is completed, and that no data whatsoever is changed if the SAP transaction terminates. In most cases, the update is implemented asynchronously at the end of an LUW. This significantly improves the performance for the dialog user, who can already continue working in the next LUW, while the update system is still implementing the change on the database.

As long as the update has not been implemented, the objects to be changed remain locked; depending on the type of lock, other users can’t access these objects, or at least not in change mode. Updating problems impair the functions of the entire system and, consequently, the high-est priority is to solve the problems. The following sections describe the basic concepts of updating and explain how to use the update monitor-ing tools integrated into the SAP NetWeaver AS ABAP.

Concepts of Updating2.3.1

You need a special update system to map the SAP LUW to database transactions. Logical SAP units of work are converted into independent SAP LUWs that can in turn consist of several database transactions. This is only possible with a separate update system because each SAP LUW would otherwise have to be mapped to exactly one database transaction. You can use this update system to manage the data entry and updating separately and bundle update processes.

If a user enters data, for example, this is first received by the dialog pro-cess. However, the required changes in the database are not performed by the dialog process itself, but by update work processes specifically provided for this purpose; the changes are therefore made asynchro-nously (see Figure 2.11).

During the dialog processing of the SAP LUW, the changes to be made are saved in the update request as modules that are defined by function modules and associated data. At the end of the dialog part of an SAP

SAP LUW

Updating system

174.indb 91 6/5/08 9:06:17 AM

92


transaction, the update request is completed, the update header (see Fig-ure 2.12) is written, and the update task that performs the changes on the database according to the update request is called. The lock entries from the dialog or background processing are inherited by the update task, which only unlocks the objects after the update has been completed successfully.

Update WP

Dialog WP1

Dialog WP2

Dialog Part

SAP LUW

Asynchronous UpdateFigure2.11

Update Header

Module X1

Data

Module Y1

Data

Module Z1

Data

Module X2

Module Y2

Module Z2

Data Data

Data Data

Data Data

Module Z3

Module Y3

Module X3V1 Modules

V2 Modules

Collective Run Modules

Update RequestFigure2.12

174.indb 92 6/5/08 9:06:18 AM

93

Updating 2.3

This increases the performance for the user, compared to a synchro-nous data change, that is, an immediate change by the dialog process itself. While the user is quickly entering, changing, or deleting data, he doesn’t have to wait for the changes to be updated in the data-base. This is done asynchronously by the update work processes. The asynchronous update method particularly improves the performance of the system where comprehensive data changes are made in dia-log mode, for example, order entry. In addition, the concept of the asynchronous update increases the scalability of SAP NetWeaver AS ABAP. However, the user doesn’t normally have any influence over whether his database changes are made asynchronously or synchro-nously. This depends on the relevant implementation in the ABAP program used.

The data changes to be made for an SAP LUW are saved in an update request (also known as an update record). The update request consists of an update header and one or more V1, V2, and collective run modules (see Figure 2.12).

Information about update requests is saved in update tables:

VBHDR EE

Update headers.

VBMOD EE

Update modules.

VBDATA EE

Data transferred to modules.

VBERROR EE

Error information when an update is canceled.

Because these tables permanently change, database statistics must not be generated for them. The processing of the update tables is designed in such a way that these tables are relatively small. For performance reasons, it’s therefore important to monitor the update and cleanup can-celed updates.

Update request

Update tables

174.indb 93 6/5/08 9:06:18 AM

94


Update mode and update modules

There are three different update types in ABAP programming:

Local updateEE

Asynchronous updateEE

Synchronous updateEE

The program design already controls which mode is used, and this can’t be altered by the administrator or user.

The local update bypasses the methods described previously and makes the change on the database directly from the relevant work process. These updates are not visible in the update monitoring and can’t be administrated.

The asynchronous update is the most frequently used update mode and offers dialog users the best possible performance. To ensure that the sys-tem will work correctly, you must monitor the update system with the update requests.

The synchronous update works with the same methods as the asynchro-nous update. After the update request has been transferred to the update task, the calling program nevertheless waits until the update work pro-cess returns the status of the update. Synchronous updates are identi-fied accordingly in the information column (see Table 2.4) in update management.

We differentiate between V1 and V2 update modules within an update. There are also collective runs called V3 updates for frequently used func-tion modules. V1 updates contain critical changes with control func-tions. They relate to business processes such as changes to material stock, for example. These objects must always be changed as quickly as pos-sible. In contrast, V2 updates are mostly used for statistical purposes and are therefore subordinate. You therefore need to treat V1 updates with higher priority than V2 updates.

Each update module corresponds to one update function module. The allocation as to whether this is a V1, V2, or V3 update is a property of the function module and can’t be altered by the administrator.

Update mode

Local update

Asynchronous update

Synchronous update

V1 and V2 updates

174.indb 94 6/5/08 9:06:18 AM

95

Updating 2.3

At the system level, the processing of the V1 and V2 modules can be distributed to separate update work processes of the UPD and UPD2 classes. You define the number of V1 and V2 update processes using pro-file parameters. You can check this distribution of work processes in the Process Overview (SM50). If UPD2 work processes were not configured for a system, the V2 update is performed in the UPD work process.

You can only perform V2 updates after V1 updates. When processing a V1 component, the system also automatically tries to process the V2 components from this update request.

Updates for collective run modules(V3) are performed asynchronously using a batch job (report RSM13005), rather than in an update process. All function module calls collected are first aggregated; if the same entry is repeatedly modified, the resulting value is calculated first and only this value is written to the database once. Otherwise, you manage and handle the function modules identically to the V2 update modules, whichmeans that the update requests remain in the update tables until they are pro-cessed by the collective run.

Either the ABAP programming or application customizing will already specify whether V3 modules will be used for a collective run (one exam-ple is the delta extraction in logistics in Transaction LBWE). If the appli-cation specifies that V3 modules will be used, the SAP administrator will be responsible for scheduling and monitoring a regular collective run.

From the system administrator’s point of view, it’s not of major impor-tance which processes a user carries out, that is, which transactions gen-erate update records. On the contrary, it’s not important to the user how an update process is performed within the SAP system. What matters to the user is throughput and results. The system administrator’s task is to guarantee the throughput and results. The following sections explain the tools and methods available for this purpose.

Configuration of the Update System2.3.2

By default, update requestsare evenly distributed from the SAP system to all update work processes; update dispatching takes place with load balancing.

Collective run modules

174.indb 95 6/5/08 9:06:18 AM

96


The number of V1 and V2 update processes is defined by the rdisp/wp_no_vb and rdisp/wp_no_vb2 parameters in the instance profile. The number of update records to be processed is the crucial factor for the number and distribution of update processes. The upper limit here is set by the hardware performance and therefore the resources available for the SAP system. This consequently means that you need to monitor the work of the update processes. As a guideline for the initial settings, you specify approximately one update work process (UPD) for every four dia-log processes. Because the V2 update is not time-critical, a UPD2 work process is normally sufficient for each system.

Parameters for Configuring the Update System

rdisp/wp_no_vb:EE Number of UPD work processes.

rdisp/wp_no_vb2:EE Number of UPD2 work processes.

In rare cases, it can be useful to deactivate the automatic dispatching (i.e., the automatic distribution of pending update requests on the avail-able update processes) and instead carry out multiplexing using server groups that have to be configured manually (similar to installations with several database instances). However, this is a special case that we can’t discuss in detail here.

The Update Program Administration (SM14) provides a good overview of the profile parameters for controlling the update task, as well as a brief description of each parameter. We explain some of the most important configuration parameters in detail in the following list:

Configuration Parameters for the Update

rdisp/vbmailEE You can configure the SAP system so that a message is automatically sent to the relevant user if an error occurs with his update request. You can do this using the rdisp/vbmail = 1 setting. The 0 value, in contrast, deac-tivates the option for messages to be sent to the user if an update termi-nates. This parameter is set to 1 by default during installation.

Multiplexing

174.indb 96 6/5/08 9:06:18 AM

97

Updating 2.3

Configuration Parameters for the Update

rdisp/vbdeleteEE This parameter specifies a period in days, whereby date requests that are incomplete after this period has elapsed are deleted when you restart the SAP system or an instance. This parameter is set to 50 days by default when the SAP system is delivered. The business environment will deter-mine whether update requests are allowed to be deleted automatically; this will also probably have to be agreed upon by the auditors. Set the value of this parameter to 0 if you never want incomplete update requests to be deleted.

rdisp/vbreorgEE This parameter controls whether you want incomplete update requests to be deleted when you restart the SAP system or an instance. The 0 value suppresses the reorganization of update requests, whereas 1 activates it. You can also delete incomplete update requests using Update Program Administration (SM14), Administration of Update Requests (SM13), or the RSM13002 report. Incomplete update requests are caused by the user explicitly triggering terminations (rollbacks), whereby part of the update request was nevertheless already written by the database before a termi-nation.

rdisp/vb_stop_activeEE This parameter determines whether the update can be deactivated. You can either deactivate the update manually using the 1 value, or it can be deactivated automatically if serious database problems occur. If the 0 value is set, you can’t deactivate the update.

Monitoring and Troubleshooting an Update2.3.3

The canceled update already causes the entire system to shut down after a short time because the objects to be changed remain locked, and the update tables permanently increase. No regular maintenance measures are normally required for updating an SAP system. However, if database-related problems occur, you must clean up these exceptional situations as quickly as possible.

Possible causes of incorrect updates or even of an entire update sys-tem breaking down include database problems or lock conflicts in the application.

Causes of errors

174.indb 97 6/5/08 9:06:18 AM

98


There are basically two different issues:

System-wide difficulties that may be caused by database problems EE

often result in the update being deactivated. For example, a possible cause would be reaching the maximum size of a table in an Oracle system. If an update is stopped, you should first refer to the SAP system log (see Chapter 15) and the database log files to find general system problems. After you have solved the problem, you must start the update again manually.

The second category of update problems is more isolated and local. EE

This type of problem is often caused by programming errors in cus-tomer-specific objects, whereby the developer and user department must consult with each other to solve the problem. Together, they must decide what should be done with the canceled update records. In the overview of the Update Records (SM13), you can use the Update Records menu option to delete, repeat, update, or reset individual records or all records. Repeat means that the update is continued, whereas update means that the status of the update records is still ini-tial (init status). If a repeat update or new update is not successful, you must delete or reset the records in question and process them again.

Monitoring an update

Initially select either Update Requests (SM13) administration (see Figure 2.13) or Update Program Administration (SM14) (see Figure 2.14) to monitor the update generally and for detailed troubleshooting.

The most important information is the current status of the update. In extreme error situations, the update is deactivated automatically. Each user who wants to update data then receives the information in the sta-tus bar that the update has been stopped and is prompted to wait. The current mode remains blocked until the update runs again.

174.indb 98 6/5/08 9:06:18 AM

99

Updating 2.3

Update Requests (SM13)Figure2.13

Update Program Administration (SM14)Figure2.14

174.indb 99 6/5/08 9:06:19 AM

100


If system-wide errors occur, you can also manually deactivate the update in Update Program Administration (SM14) and reactivate it again after the problems have been solved. Update errors and problems during updating are recorded in the SAP system log.

To get an overview of the current situation, you should first display all update requests. When accessing the requests using Update Records (SM13), you should make sure to select all update records of all users from the past in all clients.

The SAP locks inherited by the update from the dialog or background process remain until the V1 update is performed for the relevant objects. If a user tries to process an object again that is locked because it’s still waiting for the update, an error message is issued. You must select the number of update processes in a way that these types of error messages will occur as seldom as possible. As a guideline, the queue time on an update work process should not exceed five minutes.

Troubleshooting Canceled Updates

Canceled updates are particularly critical. When updates are canceled, the required operations for updating a data record can’t be performed successfully, and the changes in the database are therefore incomplete.

To analyze canceled updates, you can select the update processes, based on various conditions, from the initial screen of Update Program Admin-istration (SM14). The client, user, entry time, and transaction code that lead to this update record being created, any additional information about the update request, and its current status are displayed for every data record to be updated (update record). Update records can basically accept the following statuses:

EE init The record is waiting for the update.

auto EE

If the update is active again after the update server was stopped, the update of the record is automatically repeated.

run EE

The record is currently in process.

Locks

Update record statuses

174.indb 100 6/5/08 9:06:19 AM

101

Updating 2.3

err EE

An error occurred, which caused the update to cancel.

V1 EE

The V1 modules of the request were carried out incorrectly; the request is now waiting for the V2 update.

V2 EE

The request is waiting for a collective run (V3 update).

The information column contains additional information about the type of update generation or current status. Table 2.4 shows the possible icons and their descriptions.

Icon Short Text from Update Records (SM 13)

Description

Synchronous update Update request with synchronous update.

No restart possible Update request in V1 module canceled; update can’t be repeated.

Update request with enqueues

SAP locks exist for this request.

Enqueues released The SAP locks for this request are already released.

External commit Update request was created by an external system.

Created by the batch input Update request was created by batch input session. Request update can’t be repeated.

Table 2.4 Description of Information IconsTable2.4

You must analyze the cause of cancellations in detail in each case. In addition to solving the cause of an error, you must also decide what to do with the canceled update requests. Business aspects are the crucial fac-tors here, which means that you can only carry out the analysis in close cooperation with the user department as follows:

In the Update Records (SM13) management, select the 1. Canceled sta-tus, corresponding client, user, and relevant period.

Select 2. Execute.

Troubleshooting

174.indb 101 6/5/08 9:06:20 AM

102


A list of all canceled updates is displayed. The client, user, timestamp, 3. transaction code that created the update, and status are displayed for each record.

Analyze the cancellation of the update together with the responsible 4. user department.

You can select individual update records for this and test them 5. by selecting Update Records • Test. You can also carry out an update in debugging mode by selecting Update Records • Debugging. How-ever, use this function carefully because it places considerable strain on a system’s resources.

If this doesn’t achieve any results, check the update header of 6. the data record. The update header contains all of the update record’s management data. Select Goto• Update Header here.

From the overview of the canceled update records, you can select Update Modules to find out which function modules (update mod-ules) should be executed for updating a record. This overview reflects the structure of an update request from Figure 2.12.

Select 7. Goto• Display Data to check the actual data of an update record.

Analyze the 8. System Log (SM21) of the SAP system for error messages that were issued when the update canceled.

Note

During normal operation of the SAP system, you have to monitor three es-sential points concerning the update:

Is the update active?EE

Are there update cancellations?EE

How big is the queue for the pending requests to be updated?EE

Monitoring update activities is one of the system administrator’s daily tasks.

174.indb 102 6/5/08 9:06:20 AM

103

Updating 2.3

Tips2.3.4

Overview of all open updates EE

When you access Transaction SM13, you should enter “*” as the user and client for an initial overview and select a date before the instal-lation date. Otherwise, you’ll only receive a list of your own update records from the current date for the default settings in the current client.

Deleting lock entries EE

The update request inherits the SAP locks during the update. If lock entries are simply deleted, the corresponding objects can be pro-cessed further by other users, and a clear decision can no longer be made about how the relevant update request must be processed. Lock entries and update records must therefore always be processed together when there is manual intervention.

Transactions and Menu Paths2.3.5

Lock Entries: SAP Menu • Tools• Administration • Monitor • Lock Entries (SM12)

System Log: SAP Menu • Tools • Administration • Monitor • System Log (SM21)

Update Program Administration: Can’t be accessed from the standard SAP menu (SM14)

Update Records: SAP Menu • Tools • Administration • Monitor • Update (SM13)

Additional Documentation2.3.6

Table 2.5 provides an overview of important SAP Notes in relation to the update system.

Contents SAP Note

V3 Update, Questions and Answers 396647

Update Groups (for Deactivated Dispatching) 109515

Notes for the Update SystemTable2.5

SAP Notes

174.indb 103 6/5/08 9:06:20 AM

104


Questions2.3.7

The update was deactivated because of a tablespace overflow. 1. Which actions are required after you extend the tablespace?

a. No actions are required; the update is automatically activated again.

b. The update must be activated.

c. All update records must be manually updated again.

What status does an update record have when it’s waiting to be 2. updated?

a. Active

b. Released

c. init

d. Start

Which SAP profile parameters can you use to control whether an 3. SAP user is sent a message when his update is canceled?

a. rdisp/vbmail

b. A message is always sent to the user.

c. rdisp/rbdelete

Lock Management2.4

SAP NetWeaver AS ABAP has an independent lock mechanism that is used to synchronize database access and at the same time ensure that two transactions can change the same data in the database in parallel.

Locks are defined as a lock object in the SAP system’s ABAP dictionary. A lock entry is a specific characteristic of a lock object. A specific data object (e.g., exactly one table row) is locked by a lock entry. The program automatically sets lock entries and also deletes them again. As adminis-trator, you therefore have no power over when a lock entry is created or deleted again. Nevertheless, it’s extremely important that you under-stand the SAP lock mechanism because you may have to delete orphaned

Lock object and lock entry

174.indb 104 6/5/08 9:06:20 AM

631

A

ABAP, 25, 619Central system, 112Debugger, 420Dictionary, 175, 177, 211, 619Editor, 73, 83, 89, 415, 417, 437Processor, 47Runtime Analysis, 425Workbench, 416

Access method, 127, 147E, 129F, 131G, 131I, 132L, 128Local, 127P, 129Remote, 129S, 129U, 130

ACID, 49, 619Action authorization, 145Action log, 263Adapter, 532Add-in installation, 155Add-on Installation Tool, 280Address maintenance, 316, 317ADK, 477, 478, 480, 619Administration of stored documents, 495Administration of update requests, 97ADO, 619Agent, 446, 447

Installation, 449Log analysis, 464Log files, 451SAPCCM4X, 448, 473SAPCCMSR, 447, 448sapccmsr.ini, configuration file, 465

SAPCCMSR - j2ee, 447SAPCM3X, 448

AL08, 410AL11, 378, 411AL15, 474Alert, 476Alert Monitor, 389, 409, 440, 474, 619

Analysis, 461Customizing, 452, 464

ALO1Analysis of background processing, 78, 89Analysis of buffer load, 456ANSI, 619AOBJ, 479, 491, 495API, 74, 619APPC, 619Application layer, 27, 29, 44Application Link Enabling (ALE), 353, 499, 507, 535, 619

Background job, 519Configuration, 511Coupling with BAPIs, 511Create scenario, 507Customizing, 358, 359Management, 533Status Monitor, 390, 409, 518

Application Monitor, 383, 409Application server, 30, 619Archive Administration, 483, 491

Initial Screen, 495Statistics, 493

Archive configuration, 486Archive Development Kit (ADK), 477Archive file

Access, 487Size, 488Transfer, 482

Archive Information System, 494, 495ArchiveLink, 132, 481, 619

Interface, 477

Index

174.indb 631 6/5/08 9:08:41 AM

632

Index

Monitor, 495Archiving

Customizing, 483Dataset, 485Object, 478, 479, 485, 495, 496, 620

ASAP, 620Attribute group, 460Auditing, 518Authorization, 79, 147, 326, 328

Check, 327Data, 345, 358Maintaining, 338Object, 328, 329Profile, 330

Auto-reaction method, 457, 468Central, 473

B

Background, 66Background Control Object Monitor, 78, 89Background jobs

Analysis, 74API, 74Definition, 68Deleting, 88External interface, 83Job wizard, 74Runtime analysis, 76Start date, 71Status check, 77Zombies, 77

Background processing, 45, 47, 65, 622Alerts, 77Analysis function, 76Analysis tool, 78Authorization, 79

Background service, 47Backup Domain Controller, 193Backup Log, 412BAPI, 514, 525, 526, 533, 620

ALE, 511BAPI Explorer, 526, 533Basic maintenance, 335

Batch, 47Batch Input, 410, 521, 523, 533, 620

Session, 521, 522Session Overview, 524

Batch work process, 47BD64, 359, 514, 518, 533, 534BD73, 520, 533BD82, 359, 516, 533BD87, 409, 518BDLS, 237, 243, 532BDM2, 520, 533Berkeley protocol, 130Block compression, 419BMV0, 525, 533Bookmarks, 418Breakpoint, 418Buffer, 196, 383Buffering, 51Buffer load, 411, 474Buffer trace, 380Business Application Programming Interface (BAPI), 525Business Object Repository (BOR), 526Business object type, 525Business process

Analysis, 383, 410Expert Community, 557Monitoring, 562

C

Call transaction, 525CATT, 217CCMS, 439, 476, 620CEN, 462Central monitoring system, 462Central user administration, 344Change and Transport System (CTS), 181Change Control Management, 565Change documents, 348Change indicator, 419Change option, 186Change pointer, 509Change request

Local, 251Transportable, 251

174.indb 632 6/5/08 9:08:42 AM

633

Index

Class Builder, 416Client, 209, 624

000, 210001, 210066, 211Changeability, 215Comparison, 238Concept, 243Copying over, 241Copy profile, 220Creation, 213Default, 210Deleting, 238Maintenance, 175, 177, 217, 218, 242, 513, 533Protection level, 216Role, 214Transport, 220, 229

Client administration, 209, 353, 358

Special functions, 238Client copy, 213, 243, 548

Copy profile, 220, 229Database indices, 240Local, 220, 222, 225Log Analysis, 236, 242Post-processing, 237Preparatory tasks, 219Remote, 220, 226Size of client, 239

Client export, 230, 231, 242Restart, 241

Client import, 235, 236Client-independent object, 216Clients

Comparing, 238Client/server architecture, 27Client-specific object, 215Cluster, 53CMS, 481Cofiles, 196Collective run module, 95Command, external, 73Command field, 43Communication system, 194Company address, 319, 358Component packages, 275

Composite role, 339Configuration

Multilevel, 29Three-level, 28Two-level, 27

Connection info, 35Consistency check, 289Consolidation route, 200Consolidation system, 183, 184Content Repository, 490Control, 131Control object list, 78Control Panel, 304, 313, 389, 410, 620Conversion of logical system name, 237, 243, 532Copy

Local, 220Copy according to transport request, 238, 242Copy profile, 220, 221, 222, 229Cost-based optimizer, 387CPI-C, 54, 620Create Model View, 514Creating external operating system commands, 73, 89Creating system messages, 173, 178Cross-process memory, 65CTS, 181, 183, 620

Components, 181, 182Initialization, 189

CUA, 351Activation and configuration, 353Administrating users, 355Deleting, 355Distribution Model, 353, 359Setup, 352

Customer namespace, 261Customizing, 181, 209, 620

Archiving, 487Client, 215Content Repositories, 490, 495Cross-System Viewer, 217, 242

Customizing requestAssigning, 256Creating, 253Releasing, 257

174.indb 633 6/5/08 9:08:42 AM

634

Index

D

Data, 196Administration, 439Browser, 59, 175, 177Class, 210Client-independent, 209Client-specific, 209Collection, 439Collector, 445Profile, 220Retention, 439Transfer, 520

Data archiving, 477, 496, 620Archive Information System, 494Basis Customizing, 490CCMS monitoring, 487Control and evaluation, 491Document Relationship Browser, 494Index, 489Process, 480Reloading, 493

Database, 620Copy, 240Fill level, 388Instance, 620Interface, 51, 53Layer, 27, 30, 51Log, 410Monitor, 410Server, 621

Database administration, 385Backup, 387Cost-based optimizer, 387Database fill level, 388Dictionary consistency, 389Tasks, 30Verification, 387Weekly planning, 385

Database performanceTables and indices, 240, 242

Data Transfer Workbench, 527, 533DB01, 411DB02, 58, 240, 242, 385, 388, 412DB03, 385, 410DB12, 387, 412DB13, 386, 390, 410

DB15, 484, 495DB24, 410DBA action log, 387DBA planning calendar, 386, 390, 410DB parameter changes, 385, 410DCL, 621DDL, 621Deadlock, 621Debugger, 420

Exclusive mode, 422Interface, 422Profile parameter, 425Technology, 421

Debugging, 370Default client, 210Default parameters, 346DEFAULT.PFL, 158, 163, 212, 312Default user, 325

DDIC, 211EarlyWatch, 212SAP*, 211

DefinitionArchiving objects, 479, 491

Deleting a client, 238Delivery route, 200Delivery system, 184Demo client, 215Desktop printer, 127Developer trace, 377, 408, 413Development class, 261

Temporary, 261Device

Attribute, 133Authorization, 145Class, 132Management, 126

DIAG protocol, 621Dialog

Instances, 46Processes, 60Processing, 63Request, 64Service, 45, 47Step, 49Work process, 621

Direct input, 524, 525

174.indb 634 6/5/08 9:08:42 AM

635

Index

Direct Input Management, 525, 533Directory services, 357Directory structure, 56Dispatcher, 46, 60, 158, 621disp+work, 171Distribution model, 359, 514Distribution model maintenance, 518, 534Distribution parameter, 354, 356, 359DML, 621Document relationship browser, 494, 495Domain link, 195Double stack, 27

Installations, 155dpmon, 168, 169Dump analysis, 376, 389, 410Dynpro, 621

E

E2E Trace, 563EarlyWatch Alert, 560eCATT, 217, 621EDI, 621Emergency repair disk, 548End marker, 272End to End, 563enque/backup_file parameter, 110enque/table_size parameter, 110Enqueue server, 48, 108Enqueue service, 48Enqueue trace, 380, 431Enqueue work process, 380Enterprise IMG, 246Error log file, 378, 410Event maintenance, 67, 89Export, 263Extended job selection, 74, 89Extended table maintenance, 175External breakpoint, 418External operating system commands, 89External system, 194

F

Fast input, 525FB03, 479FDDI, 621Feature list, 395FILE, 490, 495File system clean up, 409Filter, 515Firewall, 621Frontend

Computer, 621Installation, 546Printing, 130Software, 41Trace, 379

Function Builder, 416

G

Gateway, 45, 54Monitor, 313, 366, 390, 410Process, 173Service, 50, 61

General administration task, 165Global performance analysis, 409, 410Global process overview, 370Global user overview, 372, 410Global work process overview, 410GoingLive service, 560Graphical editor, 200GUI, 621

H

Hardware key, 366Heap memory, 65Hierarchical Storage Management System (HSM), 481High availability, 622Host spool access method, 134Host spool system, 117HSM, 622

174.indb 635 6/5/08 9:08:42 AM

636

Index

HTML, 622Template cache, 394Template directory, 394

HTTP, 622Log, 398Server, 398

I

IAC, 622ICF, 32, 33, 36ICM, 34

Important profile parameters, 35ICM Monitor, 396, 410IDES, 622IDoc, 509, 518, 533, 622

Check, 518, 533Create, 509Deleting, 533Error Handling, 520, 533List, 519, 533Structure, 510Tracking, 520, 533Type, 509, 622

IGS watchdog, 158Implementation guide (IMG), 246, 256, 280, 623Import, 270Importing, 273Import queue, 272Industry solution, 275Information system, 348, 358Informix, 58Installation

Backup, 548Check, 547Checklist, 539Concepts, 537Post-installation actions, 544Preparation, 537

Instance, 28, 30, 623Central, 45Parameter, 73Profile, 158, 161, 162Recording, 299Status, 364

Integrated ITS, 391Integration system, 184Internet, 32Internet application components (IACs), 37Internet Communication Manager (ICM), 34Internet user, 346, 358IPC, 623ITS, 29, 33, 37, 623

External, 38Important parameters, 38Integrated, 37

J

J2EE engine, 149Java shared closures, 149Job class, 69Job definition, 68, 74, 76, 83, 88, 89Job log, 75Job monitor, 76, 89Job overview, 75, 492, 495Job scheduler

Event-driven, 66Time-driven, 66, 88

Job scheduling monitor, 76Job selection, 389, 410Job status, 74Job wizard, 74

L

Language import, 548Language management, 550LDAP, 623Legacy System Migration Workbench (LSMW), 526LICENSE_ADMIN, 323, 358License Administration, 545License Administration Workbench, 323, 358License data, 323License key, 549List, 174

174.indb 636 6/5/08 9:08:42 AM

637

Index

List editor, 198List of favorites, 43, 44Load analysis, 390, 411Load distribution, 122, 305Local client copy, 242Local copy, 220Lock

Logic, 113Management, 45, 104, 108, 113, 380Monitor, 381, 389, 412Object, 104Owner, 106Server, 108Statistics, 114Table, 108, 110, 116, 409Type, 105

Lock entry, 103, 104, 113, 380, 381Managing, 113

Lock waits, 385, 411log, 196Log attribute, 459Logging the startup process, 156Logical File Names, 490, 495

Client-Specific, 490, 495Logical server, 121Logical systems

Maintain, 512Renaming, 532

Logon group, 306, 307, 313, 314Logon group maintenance, 306, 313

Logon load balancing, 306LSMW, 526, 527LUW, 49, 623, 626

M

Maintenance job, 80, 83Maintenance of profile parameters, 294MAPI, 624Mass changes, 220, 321, 323, 358Mass printing, 127, 147Master password, 325MaxDB, 58MCOD, 31, 543, 624memlimits, 297

Memory Area, 51Management, 57, 158Pipes, 35Size, 158

Menu bar, 41Message control, 509Message maintenance, 468, 474Message server, 45, 48, 60, 61, 158Message server monitor, 313Message server overview, 366, 411Message type, 508, 514Microsoft Management Console (MMC), 154MONI, 382Monitor attribute, 443, 458Monitoring, 561

Properties and methods, 457, 463, 468, 474

Monitoring architecture, 439, 440Alert monitor, 440

Monitor object, 443Monitor segment, 443Monitor set, 441, 442

Creating customer-specific, 453MTE, 442, 476

Analysis method, 456Auto-reaction method, 457Class, 460Data collection method, 456Real and virtual, 445

Multilingual capability, 44Multiplexing, 96Multisystem landscape, 185Multithreaded architecture, 111Mutex locks, 394Mutual exclusions, 394

N

Name range, 187Namespace, 187, 188

ABAP and GUI tools, prefix/1BCABA/, 188Customer name range, 188

174.indb 637 6/5/08 9:08:43 AM

638

Index

Development Workbench, prefix/1BCDWB/, 189Enqueue function groups, prefix/1BCDBWEN/, 189General SAP name range, 188

Native SQL, 51Note Assistant, 572

O

OAAD, 495OAC0, 490, 495OAM1, 495Object class, 328, 359Object Linking and Embedding (OLE), 55Offline redo log, 477OLE, 55, 624OLTP, 624OMS, 124, 136, 624

External, 136ROMS and LOMS, 136

Online documentation, installation, 549Online system log analysis, 335Open SQL, 51Operating system, 55

User, 58Operating system data collector, 446Operation mode, 285, 297, 314, 620

Definition, 299Maintenance, 298Overview, 299Profile view, 300Time table, 303

Operation mode calendar, 313Operation mode maintenance, 69, 89, 298, 304, 313, 461, 474Optimizer, 387, 486

Statistics, 486Oracle, 58, 477OS, 624OS03, 384, 411OS6, 365, 411OS07, 384, 411, 474OS Monitor, 365, 411OS Parameter Change, 384, 411OSS, 572, 624

OSS1, 572OS System Configuration, 384, 411Output

Attribute, 135Control, 389, 409Controller, 128, 138, 146Devices, 132Processing, 117Request, 118, 139Requirement, 118Service, 48

Output management system (OMS), 124Overview send requests, 528Own data, 321, 345, 358Own jobs, 76, 89

P

PAI, 624Parallel process, 223Parameter

Creating, 296Parameter changes, dynamic, 294Partner Profile, 359, 516, 533PBO, 624Performance analysis, 89, 380, 411, 431Performance attribute, 458Performance monitoring, 382

Buffer, 383Database, 384Operating system, 384

Performance trace, 380, 431Enqueue trace, 435Profile parameter, 432RFC trace, 380, 435SQL trace, 434Table buffer trace, 435User interface, 432

Personal settings, 345PFCG, 322, 330, 340, 359Pool table, 52Port, 517, 624Port definition, 533Post-client import method, 236, 242

174.indb 638 6/5/08 9:08:43 AM

639

Index

Post-installation actions, 189Presentation layer, 27, 29, 39Print output

Data flow, 119Process

Error log file, 370List, 170Reasons for stop, 368Selection, 371Semaphore, 368Start behavior, 368Status, 367Type, 367

ProcessesParallel, 223

Process numberAt the operating system level (PID), 367Internal, 367

Process overview, 95, 177, 224, 313, 367, 369, 389, 411, 430

Global, 370Of an instance, 167With OS tools, 173

Production client, 214Production printer, 127Production system, 181Profile, 158, 179, 624

Activating, 293Basic maintenance, 291Changes, manual, 312Changing management data, 290Copying, 290Evaluation, 163Extended maintenance, 292Generator, 624Importing, 286, 289Maintenance, 285, 286, 287, 290, 312, 313Special case profile, 312

Profile parameter, 294Changing, 312, 383, 411Creating, 295Maintenance, 295, 313

Program, external, 73, 74Project administration, 247Project creation, 280

Properties variants, 460

Q

QA approval procedure, 202Q-API, 55, 624qRFC Monitor, 506, 534

Inbound, 390, 411, 506, 533Outbound, 390, 411, 506, 534

Queue application programming interface, 624Quick Sizing Tool, 538Quota, 309

R

R3setup, 285Control files, 549Templates, 550

R3trans, 182, 203, 273RAID, 624RDBMS, 30, 58RDDIMPDP, 273rdisp/enqname, 110rdisp/j2ee_start, 155rdisp/wp_no_enq, 110Reference client 000, 210Regular tasks, 389Release, 263Reloading, 493Remote client copy, 220, 226, 227, 242, 244Remote Function Call (RFC), 50, 54, 500, 625, 500

Administration, 502, 534Asynchronous, 505Client, 500Connection, 452, 500Connection type, 501, 502Create, 502Define, 501Destination, 500Group, 504Logical connection, 505

174.indb 639 6/5/08 9:08:43 AM

640

Index

Maintain, 502Monitoring, 506Queued, 506Resource monitor, 310Server, 500Server group, 308, 309Server group maintenance, 224, 311, 313Synchronous, 505Trace, 380, 431Transactional, 506

Replication table, 113Report, 183Report Builder, 416Repository, 183, 209Request number, 251Role, 332, 625

Composite role, 339Creating, 334Standard, 333Transport, 343

Role maintenance, 322, 330, 332, 333, 340, 359

New implementation, 344Route permission table, 568Router string, 570Row numbers, 418RSBDCREO, 82RSBPCOLL, 81RSBPSTDE, 81RSBTCDEL, 81RSCOLL00, 81RSDELCUA, 355RSP00041, 143RSPARAM, 73, 296RSPO0041, 82RSRFCTRC, 503RSSNAPDL, 82Runtime analysis, 425, 438

Components, 425Initial screen, 427Profile parameter, 427

Runtime error, 82Analysis, 375

RZ01, 76, 89RZ03, 304, 313, 389, 410RZ04, 69, 89, 298, 304, 313, 461, 474

RZ10, 286, 290, 312, 313RZ11, 294, 313RZ12, 224, 309, 311, 313, 504, 534RZ20, 409, 441, 451, 474RZ21, 451, 457, 461, 463, 468, 474

S

SAA standard, 54SAINT, 278, 280SALE, 358, 359, 533SAP*, 211, 212SAP Add-on Installation Tool, 278SAP Archive Information System, 494SAP Business ByDesign, 557SAP Business Community, 557SAP Business One Customer Portal, 556SAPCCM4X, 448SAP CCMS monitors for optional components, 441SAP CCMS monitor templates, 441SAPCCMSR, 447, 448SAPCCMSR -j2ee, 447SAP CCMS Technical Experts Monitor, 441, 462SAP Central Process Scheduling by Redwood (SAP CPS), 84SAP Channel Partner Portal, 557SAPCM3X, 448SAPcomm, 527SAPconnect, 527, 528

Administration, 528, 534Send Requests, 534

SAP CRM, 25SAP-delivered object, 250, 260SAP Developer Network (SDN), 556SAP Directory, 378, 379, 411sapevt, 67SAP exception analysis, 564SAP gateway, 54SAP GUI, 29, 39, 41, 163, 178, 546

For HTML, 37For HTML, 41For Java, 40For Windows, 40

174.indb 640 6/5/08 9:08:43 AM

641

Index

SAP Help Portal, 557SAP Implementation Guide, 359SAPinst, 285, 539, 540, 541, 544

Control files, 549SAP instance, 30, 623sapinst.log, 541SAP kernel, 56SAP license key, 544SAPLOGON, 39, 164, 165, 179

Frontend installation, 546saplogon.ini, 164SAPLPD, 127, 130SAP LUW, 91sapmsg.ini, 164sapnames, 196SAP NetWeaver Administrator, 403SAP NetWeaver AS

AS ABAP, 25, 26AS Java, 27, 148Installation options, 26Starting, 153Stopping, 155

SAP NetWeaver Portal, 29SAP NetWeaver XI/SAP NetWeaver PI, 499, 530, 531SAP Operating System Collector, 153saposcol, 153, 154, 171, 382, 446, 449, 474

Destination, 474In dialog mode, 472Process monitoring, 472

SAP Partner Portal, 557sappfpar, 297SAP proposals, 344SAP reference client, 215saproute.ini, 164SAProuter, 566, 567, 568, 573, 625

Connection, 567Options, 570Routing table, 569

saprouttab, 573SAP SCM, 25SAP server administration, 224SAP Service Marketplace, 555

Overview, 556SAP Solution Manager, 558, 559SAPSprint, 137

SAP SRM, 25sapstart, 171sapstart.log, 158SAP Support Portal, 556SAP system

Configuration variants, 27Distributed, 31Hardware requirements, 538Problems during system startup, 177

SAP system identifier, 31SAP system trace, 345, 359, 379, 411SAP transaction, 48, 626SAP upgrade

Protection against, 217SAP user, 58SAP virtual machine container (VMC), 148SAP workload analysis, 564SARA, 483, 491, 495SARFC, 310, 313SARI, 494, 495Scalability

Horizontal, 28SCC1, 238, 242SCC3, 223, 233, 236, 242SCC4, 175, 177, 217, 242, 353, 358, 513, 533SCC5, 238SCC7, 236, 242SCC8, 242SCC9, 227, 242SCCL, 222, 242Scheduler

Background, 66SCMP, 239, 242SCOT, 528, 534Screen processor, 47SCU0, 217, 238, 242SCUA, 353SCUG, 355, 358SCUM, 354, 356SDCCN, 323SE01, 233, 242, 269, 281SE03, 270, 280, 281SE09, 253, 263, 280, 281SE11, 175, 177SE16, 59, 175, 177

174.indb 641 6/5/08 9:08:43 AM

642

Index

SE24, 416, 420SE30, 425, 438SE37, 416, 420SE38, 73, 83, 89, 416, 420, 437SE80, 416, 420SE91, 468, 474SE92, 471, 474SE93, 178Security audit configuration, 349, 359Security audit log, 349Security audit log assessment, 349, 359Selection authorization, 145Selection criteria, 429Semaphore, 368Server, 625

Group, 504Group maintenance, 504, 534List, 178Overview, 363, 364, 365, 366, 371, 389, 412Resources, 310, 313

Service, 45Enqueue, 48Gateway, 50Output, 48Spool, 48

Service and support, 555Service data control center, 323Service level reporting, 562Session, 39, 44, 624Session breakpoint, 418Settings, personal, 345Setting variants for help, 549SF01, 490Shared class pool, 149Shared memory, 151, 439, 625SHDB, 522, 534Short dump, 82, 375SID, 31, 544, 625Signal handler, 35Simple job selection, 74, 77, 88, 89Single Activity Trace, 429SITSPMON, 391Sizing, 537SLICENSE, 545SM01, 175SM02, 173, 178

SM04, 168, 177, 371, 410SM12, 103, 108, 113, 381, 389, 412SM13, 97, 98, 103, 389SM14, 96, 97, 98, 412SM19, 349, 359SM20, 349, 359SM21, 102, 173, 178, 335, 373, 389, 412, 474SM28, 547SM30, 175, 176SM31, 178SM35, 410, 523, 533SM36, 68, 74, 76, 83, 89SM37, 74, 88, 89, 389, 410, 492, 495SM37C, 74, 89SM39, 89SM49, 73, 89SM50, 95, 177, 224, 313, 367, 389, 411, 430SM51, 166, 178, 224, 363, 371, 389, 412SM52, 151SM53, 151SM58, 390, 412, 506, 534SM59, 502, 534SM61, 78, 89SM62, 67, 89SM63, 313SM64, 89SM65, 78, 89SM66, 372, 410SM69, 89SMGW, 313, 366, 390, 410SMICM, 396, 410SMLG, 306, 313SMLT, 550SMMS, 313, 366, 411SMO, 561SMQ1, 390, 411, 506, 533SMQ2, 390, 411, 506, 534SMQR, 506, 534SMT1, 504, 534SMTP plug-in, 528SMX, 76, 89SNA, 32SNC, 625SNOTE, 572

174.indb 642 6/5/08 9:08:43 AM

643

Index

Software component, 187Solution Management Optimization Services (SMO), 561Solution Manager, 558, 559SOST, 528, 534SP01, 128, 138, 145, 146, 389, 409SP12, 143, 146SPAD, 123, 138, 141, 146SPAM, 275, 280Spool administration, 123, 124, 138, 140, 146

Authorizations, 144Troubleshooting, 138

Spool landscape, 117Spool process, 48Spool request, 117

Overview, 139Status, 139

Spool server, 121Classification, 122Dedicated, 147Definition, 124

Spool service, 45, 48, 120Spool system

Consistency check, 143Reorganization, 143

Spool work process, 119Request management, 120Sequential processing, 120

SPRO, 246, 256, 280, 359SPRO_ADMIN, 247, 280SQL interface, 30, 47SQL trace, 380, 431, 438SR13, 549SSAA, 401, 412SSCR, 625ST01, 345, 359, 379, 385, 411ST02, 383, 411, 456, 460, 474ST03N, 382, 390, 411, 412ST04, 384, 410ST05, 380, 431, 438ST06, 365, 384, 411ST07, 383, 409ST10, 383, 412ST11, 378, 410ST22, 376, 389, 410ST30, 409, 410

STAD, 383, 410Standalone enqueue server, 111, 112Standalone ITS, 38Starting SAP NetWeaver AS, 153Starting the SAP system

Problems, 177Start profile, 158, 159, 160startsap, 154Status, 166Status attribute, 459Status bar, 44, 419Status Monitor for Integrated ITS, 391STMS, 236, 242, 270, 281Stopping SAP NetWeaver AS, 155stopsap, 155SU01, 316, 340, 348, 356, 358SU3, 321, 345, 358SU10, 220, 321, 323, 358SU21, 328, 359SU25, 344, 359SU53, 345, 358SUCOMP, 358SUGR, 321, 358Super user, 325, 332Support connections

Configuration, 565Support package, 275, 625Support package collection, 277Support Package Manager, 275, 280S user, 571SXDA, 527, 533Sys Log Daemons, 158System

Distributed, 51External, 194Virtual, 193

System Administration Assistant, 401, 412System change option, 186System configuration, 474System event, 67System identifier, 31System landscape, 181, 625

Multiple systems, 185Setting up, 181Tasks, 182Three systems, 184

174.indb 643 6/5/08 9:08:44 AM

644

Index

Two systems, 183System Load Monitor, 382, 383, 384System log, 102, 103, 173, 178, 373, 389, 412, 474

Evaluating, 374Filtering, 469Global, 373Local, 375Maintaining messages, 471Repairing a local, 408Selecting, 374

System measurement, 323, 359System message, 173, 174System monitoring, 166, 363, 561System profile, 158

T

TableCluster, 53Pool, 52Transparent, 52

Table buffer trace, 431Table calls, 383, 412Table cluster, 53Table comparison, 239, 242Table maintenance, 175, 176, 178

Extended, 175Tools, 175

Tables and archiving objects, 484Tables and indices, 385, 388, 412Table type, 52Target server, 70Task handler, 47TCP/IP connection, 504TCP/IP protocol, 54TDC, 190, 625TemSe, 48, 117, 126, 141, 143, 145, 626TemSe administration, 143, 146TemSe data storage

Consistency check, 143Test client, 214Test printing, 127Threads, 35Three-system landscape, 184

Sample structure, 214Time table, 302tmp, 196TMS, 190, 193, 237, 626

Configuration, 190Toolbar, 42tp, 68, 182, 203, 207, 229, 235, 273tp parameter, 204Trace file, 377Trace level, 378, 408

Reset, 408Trace logging, 408Training/education client, 215Transaction, 626

Database, 49SAP, 48

Transactional RFC, 390, 412Transaction code, 43, 44, 626Transaction maintenance, 175, 178Transaction Recorder, 522, 534Transparent table, 52Transport, 181, 626

Control, extended, 201Directory, 194, 195, 206Directory tree, 195Domain, 190, 206, 626Domain controller, 190, 191, 625, 626Group, 196, 206Layer, 200Log, 264Program, 203Tool, 181

Transporting properties variants, 461Transport Management System, 181, 190, 236, 242, 270, 281Transport Organizer, 181, 233, 245, 253, 263, 280, 281, 626

Extended view, 241, 269, 281Tools, 270, 280, 281

Transport route, 197, 201, 206Editor, 197List editor, 198

Transport systemInitialization, 186

tRFC, 535, 626

174.indb 644 6/5/08 9:08:44 AM

645

Index

tRFC Monitor, 506, 534Triggering events, 89Trusted System, 504, 534TU02, 383, 411Two-system landscape, 183

U

UNIX, 58, 154, 155, 305Update, 45, 90

Administration, 389, 412Asynchronous, 91, 94Configuration, 95Configuration parameter, 96Definition, 90Dispatching, 95Header, 102Information icons, 101Local, 94Mode, 94Monitoring, 98Program administration, 96, 97, 98, 103Request, 91, 92, 93, 98Service, 47Synchronous, 94System, 90Table, 93Task, 61Troubleshooting, 97V1, 94V2, 94

Update records, 98Overview, 100Statuses, 100

Upgrade, 259, 344User, 58, 315

Address, 318Assignment, 340Comparison, 328, 340Concept, 315Creating, 317CUA, 352Defaults, 321Distribution, dynamic, 305

Event, 67Group, 321Information system, 348Interface, 619Internet user, 347Logon and password protection, 324Logon data, 319Maintaining defaults, 346Maintenance, 316, 317, 340, 356Mass changes, 323Master comparison, 342Master record, 316Menu, 43, 336Name, 315Parameters, 321Role, 327SNC, 321Transfer, 355, 358Type, 320

User group, 321, 358SUPER, 212, 213

User overview, 168, 177, 371, 410Global, 372Local, 371, 372

USMM, 323, 359

V

V2 update, 45, 48Variant, 73Version management, integrated, 199Virtual machine container (VMC), 63, 148Virtual system, 193VMC system administration, 151VM overview, 151

W

Watchdog, 35WBO, 258WE05, 519, 533

174.indb 645 6/5/08 9:08:44 AM

646

Index

WE21, 533Windows, 154Windows Task Manager, 171Worker thread, 35Workload analysis, 383, 412Work process, 46, 626

Terminating, 168WORM, 626

X

XML, 626xSprint.exe, 137

Z

Zombies, 77

Complete technical detailsfor upgrading to

SAP NetWeaver AS 7.00

In-depth coverage of all upgradetools and upgrade phases

Includes double-stack upgradesand the combined upgrade &

Unicode conversion

Bert Vanstechelman, Mark Mergaerts, Dirk Matthys

SAP NetWeaver Application ServerUpgrade Guide

This comprehensive guide covers the regular aswell as the new »double-stack« upgrades. Itdescribes a complete project, explains projectmanagement questions, provides technicalbackground information (also on the upgrade ofother systems like CRM, Portal, XI, and BI), andthen walks you through the project steps —from A to Z.The authors cover the entire process in detailedstep-by-step instructions, plus how to plan theupgrade project and the impact on the systemlandscape during your SAP upgrade.

586 pp., 2007, 2. edition,79,95 Euro / US$ 79,95ISBN 978-1-59229-144-1

SAP NetWeaver Application Server Upgrade Guide

www.sap-press.com

174.indb 646 6/5/08 9:08:44 AM

sappress netweaver as abap system administration

Documents