SAP Standard Background Jobs and Job Monitoring

There are a range of background jobs that must run regularly in a production system, to, for example, delete obsolete jobs or spool objects. You should schedule the following jobs in the job definition transaction SM36, so that they are automatically started at the specified frequency:

 

Program Name / Job Name	Repetition Frequency	Description
RSBTCDEL / SAP_REORG_JOBS	daily	Deletes old background jobs
RSBDCREO / SAP_REORG_BATCHINPUT	daily	Deletes old batch input folders
RSSNAPDL / SAP_REORG_ABAPDUMPS	daily	Deletes old ABAP dumps
RSBPSTDE / SAP_REORG_JOBSTATISTIC	monthly	Deletes old job statistics
RSBPCOLL / SAP_COLLECTOR_FOR_JOBSTATISTIC	daily	Creates job statistics
RSCOLL00 / SAP_COLLECTOR_FOR_PERFMONITOR	hourly	Starts data collectors for ABAP statistics records
RSN3_STAT_COLLECTOR/ SAP_COLLECTOR_FOR_NONE_R3_STAT	hourly	Starts data collectors for non-ABAP statistics records (Distributed Statistics Records, DSRs)
RSXMILOGREORG / SAP_REORG_XMILOG	weekly	Deletes obsolete entries in the XMI log
RSAL_BATCH_TOOL_DISPATCHING/ SAP_CCMS_MONI_BATCH_DP	hourly	Starts long-running data collectors that report application-specific values to the monitoring architecture
RSPO0041/1041 SAP_REORG_SPOOL	daily	Deletes obsolete spool requests to reduce system load
RSPO1043	daily	Checks the consistency of the spooler and of the TemSe and evaluates the results if necessary
RSBTCPRIDEL/ SAP_REORG_PRIPARAMS	monthly	Reorganizes the print parameters across clients

 

 

You can monitor jobs in the following ways:

·        You can call the Job Selection transaction (transaction SM37) and check whether the jobs actually ran without errors.

·        You can use the job monitoring of the Alert Monitor (transaction RZ20) to monitor the jobs. You can set up job monitoring so that you are automatically notified if an error occurred.

With job monitoring, alerts are displayed if errors occurred. If you assign an "auto-reaction method" to these alerts, you are notified, for example, by SMS or by e-mail if problems occurred during the execution of the jobs.

 

SAP Netweaver Monitoring Availability

It is not possible to uniquely define availability with regard to IT components. Availability can mean the existence of a process at operating system level. Other definitions of availability can include, for example, the provision of a service within a certain time, or the average time for performing a user action.

SAP provides different mechanisms for checking availability: The following is common to the mechanisms:

• The availability information is usually of a technical nature.

• Once set up, the availability check is performed periodically and without user interaction.

• The result of the check is reported in the central monitoring system.

You have the following options for monitoring availability:

• You can use Availability Monitoring with CCMSPING to monitor ABAP and Java systems and their instances. With this option, the CCMSPING agent queries the message server in each case about which instances are reported as active. With ABAP systems, you can also have the availability of instances and logon groups monitored using a direct RFC call to the instance itself.

• You can check availability at application level with the Generic Request and Message Generator GRMG. With this option, the central system periodically calls a GRMG application using a URL. The GRMG application performs component-specific checks and returns the result of the checks to the central system.

• You can monitor the existence of the relevant process at operating system level. A check of this type determines a prerequisite for the availability of the component. The check is performed by the SAP programs SAPOSCOL and the agent SAPCCMSR

Execution

Check the Availability monitor for alerts. To open the monitor, proceed as described in Tasks. Depending on the affected nodes, you can react to the alert as follows:

 

Affected MTE	Meaning
Check by CCMSPING	With this monitor, you can perform availability monitoring for selected ABAP and Java systems and their instances.
<SysID> Availability: <SysID> on <Host>Instances: <SysID>	Check that the system or instance is definitely not available by attempting to log on. If this is the case, check the developer trace (dev_trace), if appropriate, and restart the system or instance (depending on the platform you are using, either with the MMC or using a start script).
J2EE Engines: Heartbeat by GRMG	The subtree for each GRMG scenario consists of two subtree types: · Availability of the scenario (Was it possible to perform the check of the components?) with the prefix Selfmonitoring · Availability of the monitored components
GRMG: J2EE <SysID> on <Host> Selfmonitoring: Scenario ...	If an alert occurred in this subtree, it was not possible to perform the monitoring of the J2EE Engine, availability values are therefore not delivered for the subtree below .
GRMG: J2EE <SysID> on <Host> Test: <Component>	If an alert occurred in this subtree, the monitored component is not available.
J2EE Engines: OS Processes	You can use this subtree to determine (sorted by the monitored Java systems) whether the most important processes (dispatchers, servers, and SDM) are running at operating system level. If required processes are not running, first check the log files using the Standalone Log Viewer, and then restart the Engine.

 

 

SAP Netweaver Monitoring Components

 

Component	Description
Alert Monitor	Use the alert monitor (transaction RZ20) as the central tool for monitoring your entire system landscape. If malfunctions or problems occur, alerts are generated. These alerts are displayed in various monitors in a tree structure, and you can assign auto-reactions to them. In this way, you are informed quickly and reliably about the alert, even if you are not working in the alert monitor at the time. If you use the alert monitor as the entry point for your central monitoring, you will use the tools listed below in this table as analysis methods, that is, after an alert is generated, you can start the appropriate tool for the alert by double-clicking the alert.
SAP NetWeaver Administrator	The SAP NetWeaver Administrator (NWA) unifies the most important administration and monitoring tools both for Java and for ABAP systems in a new, browser-based user interface. The most important advantages of the NWA are: You no longer need to switch between different tools for administration, troubleshooting, and problem analysis of your entire SAP NetWeaver system landscape. There is a central administration tool available to you landscape-wide for both Java and ABAP systems for starting and stopping instances, checking configuration settings and logs, and monitoring error-free functioning of components. The interface follows the current guidelines for interface design, is easy-to-use, task-oriented, and complete. By using Web Dynpro, it runs in a browser.
SAP Solution Manager	Solution Monitoring in the SAP Solution Manager monitors heterogeneous system landscapes. You can monitor your systems and business processes in one tool. The system monitoring and business process monitoring are based on the data of the CCMS monitoring infrastructure.
Operating System Monitor	You can use the operating system monitor to monitor the following operating system resources: Virtual and physical memory CPU File system administration and physical disks Network Transaction ST06 displays the operating system data for the local server. Transaction OS07 displays the data for the entire system.
Workload Monitor	The Workload Monitor (transaction ST03) displays statistical data for the local ABAP system for performance analysis. You can also display, for example, the total values for all instances, and compare the performance of particular instances over a period of time. The large number of analysis views and collected data allow you to quickly determine the cause of possible performance problems.
Global Workload Monitor	The Global Workload Monitor (transaction ST03G) displays statistical records for entire landscapes, both for ABAP systems and for DSR components, such as J2EE Engine, BC, and ITS. You can, for example, display the load data created when external components are called.
ICM Monitor	You can use the ICM monitor (transaction SMICM) to monitor and administer the Internet Communication Manager, which receives and sends the requests from or to the Internet (in the server role, for example, the inbound HTTP requests).
Overview of SAP Application Servers Monitoring and Administration of the SAP Message Server Displaying and Controlling Work Processes Displaying and Managing User Sessions Trace Functions Monitoring RFC Resources on the Application Server Using SAP Gateway Monitor in SAP System System Log	The SAP system contains various tools for displaying detailed information on application servers, user sessions, and work processes. If you want to work with these tools, from the SAP initial menu choose  Administration System Administration or transaction S002. The initial screen for system administration appears. The tools are available under Administration and Monitor. There are also programs that you can use at operating system level to monitor the message server or the gateway. For information about other tools for monitoring system components, see these sections.

SAP Netweaver - Overview of Monitoring Architecture

You can display monitoring data for the following components in the central monitoring system (CEN):

• Systems based on SAP Web AS ABAP and Java

• SAP systems with earlier releases (as of SAP R/3 3.0)

• Non-SAP components

The data is transferred to CEN using CCMS agents or ABAP RFC connections. You can display it there directly in the Alert Monitor, or forward the data to external tools or SAP Business Intelligence for additional evaluation.

The elements of the monitoring architecture function largely independently of each other and can, particularly, be further developed and adjusted independently of each other.

The alert monitor also provides the administration methods that you need to monitor the system. These enable you to set threshold values for alerts and add or adapt auto-reaction and analysis methods. Auto-reaction methods react automatically when an alert is triggered; analysis methods enable you to examine the cause of an alert without leaving the alert monitor. The monitoring architecture also contains tools for administering and archiving the alerts.

Program/Application	Description
CCMS agents	CCMS agents are independent processes that connect a monitored component (such as a host, an ABAP instance, or a Java instance) with CEN using RFC.
Operating System Collector SAPOSCOL	SAPOSCOL is a stand-alone program that runs in the operating system background. It runs independently of SAP instances exactly once per monitored host and collects data about operating system resources.
Availability Monitoring with CCMSPING	With this type of monitoring at system or instance level, the CCMSPING agent queries the relevant message server about which instances are reported as active. You can also have the instance availability of ABAP systems monitored using a direct RFC call to the instance itself.
Monitoring with the Generic Request and Message Generator	With this type of monitoring at application level, CEN periodically calls a GRMG application using a URL. The GRMG application performs component-specific checks and returns the result of the checks to CEN.

J2EE Engine : JControl & JCmon

JControl
JControl starts, stops, and monitors the processes of a Java instance - primarily the server and dispatcher processes.
JControl restarts terminated processes, ends hanging processes, and sends a shutdown signal to Java instances.
JControl starts the JLaunch processes, which in turn start Java nodes such as dispatchers or servers.
JControl starts a Java instance bootstrap process with parameters that are defined in the file bootstrap.properties (/usr/sap///j2ee/cluster/bootstrap)

-> Java profiles are stored under \usr\sap\\SYS\profile\DIR_PROFILE

JCmon
The JCmon tool can be used to monitor the JControl process. JCmon is part of the Startup and Control Framework, and is located in the JControl/JLaunch home directory, that is, in the executable directory /usr/sap///j2ee/os_libs.
JCmon can be started with the command JCmon pf=.

J2EE Engine : Restarting a Single Process

 

       1.      Start JCmon

           The system prompts you to choose a command number.

       2.      Choose command 5 "Restart process" (this command restarts a specified process).

           The system prompts to specify the index of the process that you want to restart.

           You can view the process indexes from the table of processes that is displayed every time you execute a command.

           The  indexes are displayed in the first column of the table (Idx).

       3.      Specify the index of the process that you want to restart and confirm your choice.

 

The JCmon restarts the specified process.

J2EE Engine - Checking That All Processes Are Running

 

Procedure

...

       1.      Start JCmon.

         The system prompts you to choose a command number.

       2.      Choose command 11 "Process list" (this command displays the status of the processes).

The result displayed on the command line will be something like this:

------------------------------------------------------------ SAP System Name   : J2E SAP System        : 00 MS Host           : testpc-doc MS Port           : 3601 Process Count     : 3 PID of JControl   : 3108 State of JControl : All processes running State inside MS   : All processes running Admin URL         : ------------------------------------------------------------   |Idx|Name                |Type                |PID     |State               |Err or|Restart|Debug|Debug|Debug | |   |                    |                    |        |                    |Cou nt|Mode   |Prep.|Mode |Port  | |---|--------------------|--------------------|--------|--------------------|--- --|-------|-----|-----|------| |  0|dispatcher          |J2EE Dispatcher     |    2900|Running             |  0|yes    |no   |no   | 50000| |  1|server0             |J2EE Server         |    3580|Running             |  0|yes    |yes  |no   | 50021| |  2|SDM                 |SDM Server          |    3556|Running             |  0|yes    |yes  |no   | 50002| ------------------------------------------------------------     ------------------------------------------------------------ SAP System Name   : J2E SAP System        : 00 MS Host           : testpc-doc MS Port           : 3601 Process Count     : 3 PID of JControl   : 3108 State of JControl : All processes running State inside MS   : All processes running Admin URL         : ------------------------------------------------------------   |Idx|Name                |PID     |State               |Error|Restart| |---|--------------------|--------|--------------------|-----|-------| |  0|dispatcher          |    2900|Running             |    0|yes    | |  1|server0             |    3580|Running             |    0|yes    | |  2|SDM                 |    3556|Running             |    0|yes    | ------------------------------------------------------------     ============================================================ JControl Monitor Program - Administration Menue (Local) Instance : JC_J2E_00_testpc-doc ============================================================ 0  : exit 1  : Refresh list 2  : Shutdown instance 3  : Enable process 4  : Disable process 5  : Restart process 6  : Enable bootstrapping on restart 7  : Disable bootstrapping on restart 8  : Enable debugging 9  : Disable debugging 10 : Dump stacktrace 11 : Process list 12 : Port list 13 : Activate debug session 14 : Deactivate debug session 15 : Increment trace level 16 : Decrement trace level 17 : Enable process restart 18 : Disable process restart ------------------------------------------------------------ 98 : Synchronize instance properties 99 : Extended process list on/off ------------------------------------------------------------ command =>

 

The status of each process is displayed in the corresponding tables above.

 

 

JCmon Menu options (features)

 

The JCmon main menu provides the following functions:

 

0: Exit

Returns back to the main menu.

1: Refresh list

Refreshes the process list and the menu.

2: Shutdown instance

Invokes the shutdown of the specified J2EE instance.

3: Enable process

Enables and starts a process, which is switched off. (Restart == no)

4: Disable Process

Stops a running process and switches off the restart flag.

5: Restart Process

Restarts the specified process.

6: Enable bootstrapping on restart

7: Disable bootstrapping on restart

8: Enable Debugging

Checks if the specified process is running in debug mode. If not and the process is configured for debugging, JControl will restart the process in debug mode.

9: Disable Debugging

If the process is running in debug mode, JControl will restart the process and switch off the debug mode.

10: Dump stack trace

The specified process gets an event to invoke the dump of the stack trace of the Java VM. The stack trace is stored in the stderr<n> output file in the work directory.

11: Process list

Displays the status and additional information about all the processes.

12: Port list

Displays a list with detailed information about the ports used by the J2EE Engine.

13: Activate debug session

Activates the debug session for the specified process. To activate a debug session:

1.      The process must be running in debug mode.

1.      The process must be "Load Balance Restricted".

14: Deactivate debug session

Deactivates the debug session. The process will be restarted or stopped – this depends on the process configuration.

15: Increment trace level

This increments the trace level for the developer trace file of the specified process (dev_<component name>)

16: Decrement trace level

This decrements the trace level for the developer trace file of the specified process (dev_<component name>)

17: Enable process restart

18: Disable process restart

-----

98: Synchronize instance properties

99: Extended process list on/off