User Guide

Page 1 of 39

Table of contents

1 Introduction ........................................................................................................ 2

2 Configuration ...................................................................................................... 2 2.1 Configuration of SAP Instances .............................................................. 2

2.1.1 Adding a SAP Instance with an ABAP stack ........................................................7 2.1.2 Adding a SAP Instance with a JAVA stack ........................................................ 10 2.1.3 Adding a SAP Instance with an ABAP+ JAVA stack ......................................... 13 2.1.4 Activate Monitoring of SAP Instance ................................................................. 17

3 Functionality ..................................................................................................... 17 3.1 Alerting ................................................................................................. 17 3.2 KPI ....................................................................................................... 18 3.3 Monitoring ............................................................................................. 23

3.3.1 User/Security Monitoring .................................................................................... 23 3.3.2 Background Job Monitoring ............................................................................... 23 3.3.3 Workload Analysis ............................................................................................. 24 3.3.4 Change Monitoring ............................................................................................. 25 3.3.5 Concurrent Users ............................................................................................... 25

3.4 Task List ............................................................................................... 25 3.5 Reports ................................................................................................. 28

4 Appendix .......................................................................................................... 28 4.1 Glossary ............................................................................................... 28 4.2 DB Configuration for Alerts and KPIs .................................................... 32 4.3 Registering of Java Instance into an ABAP Instance ............................ 33

4.3.1 CCMS Configuration .......................................................................................... 33 4.3.2 Remote DB Configuration .................................................................................. 37

Page 2 of 39

1 Introduction

Thank you for downloading the demo version KaarWatch 2.1 KaarWatch is a web based basis monitoring tool for monitoring and managing SAP Systems. It provides real time monitoring, automated system checks, and messaging functionalities for SAP systems on any OS/DB platform. Important SAP parameters on both the ABAP and Java Platform are monitored and deviations communicated well before it becomes an issue. Each infrastructure component that would affect the availability and performance of the system is monitored – Network, Operating System, Database, SAP Application. For most up to date information, please visit www.kaarwatch.com

2 Configuration

2.1 Configuration of SAP Instances

A SAP instance can be configured into KaarWatch in three simple steps by the administrator.

1. Login as Administrator from the Home screen. (Username: admin, Password: admin)

Once the administrator is logged in, an icon to “Add New Instances” is presented on the Home page. The administrator has privileges to add, edit or delete SAP instances.

Page 3 of 39

2. After logging in, check the system settings by clicking on the link “Click here to test your

settings for configuring new Instances”. If the screen shows the error message shown

below, follow instructions in Step a-d. If the screen shows a message that reads “Your

settings are fine”, then proceed to Step 3.

Step :a Go to the path C:\inetpub\wwwroot Right click on KaarWatch Properties Security IIS_IUSRS and allow full control

Page 4 of 39

Step :b Go to the path C:\inetpub\wwwroot Right click on KaarWatch Properties Security Users and allow full control

Page 5 of 39

Step :c Right click on the folder KaarWatch Properties Uncheck Read-only

Page 6 of 39

Step :d Redo the test now by clicking on the link “Click here to test your settings for configuring new Instances” on the KaarWatch admin page. The message below confirms that the system is ready for configuration.

Page 7 of 39

3. Click on “Add New Instance”

4. Choose the type of Instance in the pop up (Instance with an ABAP stack, ABAP+JAVA

stack or JAVA Stack) and click „Go‟.

a. Follow section 2.1.1 to add a SAP Instance with an ABAP stack

b. Follow section 2.1.2 to add a SAP Instance with a Java stack

c. Follow section 2.1.3 to add a SAP Instance with an ABAP+Java stack

2.1.1 Adding a SAP Instance with an ABAP stack

1. Select the type of instance as „ABAP‟ and click „Go‟.

Page 8 of 39

2. Choose the application (select the ECC radio button for R3 Enterprise Edition, ECC5.0 &

ECC6.0) and server type (Development, Quality, Production, Training, Sandbox). An ABAP

instance is configured in KaarWatch with the following details – IP Address and instance

number of the central instance, ABAP client, RFC user ID, and RFC password. The RFC user

ID is the user that is used by KaarWatch to remotely login into SAP. Create a RFC user ID in

the SAP system with the profile S_A.SYSTEM before starting the configuration of the SAP

instance in KaarWatch. This RFC user should have the same time zone as the system time.

3. Click on „Test Connection‟. The connectivity to the instance with the given ABAP

credentials is checked and a „Success‟ message is displayed. Click „Next‟

Page 9 of 39

4. The central instance and the application servers that are available for this instance are

listed. Select the application servers that should be included for monitoring. Click „Next‟.

5. On the Confirmation screen, click „Save‟. The selected instances of the SAP system are

added to KaarWatch with a standard set of monitoring parameters. The user may

activate/de-activate monitoring parameters for the selected instances from the

administration menu.

Page 10 of 39

The configured SAP instance(s) get listed on the home screen of KaarWatch and on the Listener.

This completes the addition of a SAP instance with an ABAP stack in KaarWatch. Activate the monitoring of the SAP Instance by following instructions in Section 2.1.4

2.1.2 Adding a SAP Instance with a JAVA stack

A SAP instance with a JAVA stack will have to be registered to report its values into a SAP instance with an ABAP stack. Please refer to Section 4.3 to complete the registration before adding the Java instance in KaarWatch.

1. Select the Type of instance as „JAVA‟ and click „Go‟

Page 11 of 39

2. Choose the application (EP for Enterprise Portal and NWD for NetWeaver Development

Infrastructure) and server type (Development, Quality, Production, Training, Sandbox. A

JAVA instance is configured with the following details – IP Address and the instance

number of the SCS, J2ee user ID, and J2ee password. Test the connection. Select „Yes‟ to

denote that the configuration of the Java stack has been completed as specified in Section

4 of this document. Click „Next‟.

3. Provide the details of the ABAP instance where the Java instance is configured. The

following details of the ABAP instance is required - IP address and instance number of the

Page 12 of 39

ABAP instance, ABAP client, RFC user ID, and RFC password. The RFC user ID is the

user that is used by KaarWatch to remotely login into SAP. Create a RFC user ID in the

SAP system with the profile S_A.SYSTEM before starting the configuration of the SAP

instance in KaarWatch. This RFC user should have the same time zone as the system

time. Test the connection and click on „Next‟ after you receive the „Success‟ message

4. The SCS and the application servers that are available for this SAP system are listed.

Select the application servers that should be included for monitoring. Click „Next‟.

Page 13 of 39

5. On the Confirmation screen, click „Save‟. The selected instances are added to KaarWatch

with a standard set of monitoring parameters. The user may activate/de-activate

monitoring parameters for the selected instances from the administration menu.

The instance that has been added shows up on the home page of KaarWatch and the Listener. This completes the addition of a SAP Instance with a Java stack in KaarWatch. Activate the monitoring of the SAP instance by following instructions in Section 2.1.4

2.1.3 Adding a SAP Instance with an ABAP+ JAVA stack

The JAVA stack of a SAP instance with an ABAP+JAVA stack will have to be registered to report its values to the ABAP stack of the same SAP instance. Please refer to Section 4.3 to complete the registration before adding the SAP instance in KaarWatch.

1. Select the Type of instance as „ABAP+JAVA‟ and click „Go‟.

Page 14 of 39

2. Choose the application and server type. An ABAP+ JAVA instance is configured with the

following details – IP Address and instance number of the ABAP central instance, ABAP

client, RFC user ID, and RFC password, J2ee user ID of the JAVA stack and the J2ee

password. The RFC user ID is the user that is used by KaarWatch to remotely login into

SAP. Create a RFC user ID in the SAP system with the profile S_A.SYSTEM before

starting the configuration of the SAP instance in KaarWatch. This RFC user should have

the same time zone as the system time. Test the connection and ensure the connection is

successful. Select „Yes‟ to denote that the configuration of the Java stack has been

completed. Click „Next‟.

Page 15 of 39

3. The central instance and the application servers that are available for this instance are

listed. Select the application servers that should be included for monitoring. Click „Next‟.

Page 16 of 39

4. On the Confirmation screen, click „Save‟. The selected instances are added to KaarWatch

with a standard set of monitoring parameters. The user may activate/de-activate

monitoring parameters for the selected instances from the administration menu.

Page 17 of 39

This completes the addition of a SAP Instance with an ABAP+ Java stack in KaarWatch. The instance that has been added shows up on the home page of KaarWatch and the Listener. Activate the monitoring of the SAP Instance by following instructions in Section 2.1.4

2.1.4 Activate Monitoring of SAP Instance

The administrator can activate the monitoring of the configured SAP instance in two ways –

1. From the Web Application Home page - Click on the „Activate‟ link against each instance.

Changes to the Instance status are transferred to the Listener.

(or)

2. From the Listener, select the instance under “Configured SAP Systems” and move it to

the right (“Monitored SAP Systems”)

The instance should be deactivated before deleting an instance. The KaarWatch Listener starts monitoring the activated instance and reports data to the various modules.

2.1.5 XMI logs in SAP

Every login of the RFC Userid from KaarWatch to SAP gets logged in the SAP table (TXMILOG and TXMILOGRAW). SAP has provided a standard job to delete obsolete entries in the XMI log tables. On the SAP systems that are monitored by KaarWatch, schedule the program RSXMILOGREORG to be executed weekly with suitable variants.(Refer OSS Note: 16083) The XMI logs can also be deleted manually from transaction RZ15.

3 Functionality

The modules in KaarWatch 2.0 are:

1. Alerts 2. KPI 3. Monitoring -

a. User/Security Monitoring b. Background Job Monitoring c. Workload Monitoring d. Change Monitoring e. Concurrent Users

4. Basis Daily Task List 5. Reporting

a. Alerts b. KPI

3.1 Alerting

When a SAP Instance is configured, the tool assigns a standard set of monitoring parameters to the instance (central instance and application servers, if any). The user has the option to activate /deactivate monitoring parameters by logging in as administrator and editing the monitoring parameters of each instance. Notification has been enabled for certain monitoring parameters.

Page 18 of 39

The notification occurs when a threshold is crossed (eg. green to yellow, yellow to red). The monitored parameters are grouped into three categories – OS, DB and SAP. A graphical display of the percentage of alerts in each category/sub-category is provided. The graphs/charts for each category displays the distribution of the alerts in the various objects in that category. Clicking on various pieces of the pie, displays the alerts in that sub-category. The latest unaccepted alert in the last 7 days for each monitored parameter is displayed on the Alerts page. The history of the alerts for each monitoring parameter is available. Clicking on “View” in the history column displays the history of the alerts for that monitoring parameter. The user can filter the history based on the alert creation date and time. One or more alerts can be accepted by the administrator which causes the alert to be removed from the display. The accepted alert gets added to the history of the alert for that monitoring parameter. The status of the alert also gets updated in SAP. The user can switch between instances using a dropdown provided in each screen. Note: If DB Alerts are not available for any instance – please refer Section 4.2

3.2 KPI

The health of a SAP Instance is measured by studying its Key Performance Indicators. When an instance is selected, the KPI tree gets generated depending on the instance selected. The identified KPIs are categorized to report on the health of the operating system, the database and the SAP application. The KPI screen reports on the values of the identified KPIs up to 10 hours. After selecting an instance, the user may click on the KPI to view the performance of that KPI for the selected duration. To view KPI values oprior to the last 10 hours, the user may choose the Reports menu. Given below is the definition of each the KPIs in KaarWatch. Note: If DB KPIs are not available for any instance – please refer Section 4.2 CPU Utilization Category: OS, Utilization The average utilization of all the CPUs in the host system is displayed. This utilization includes both user and system usage of the CPU. The graph is plotted with the CPU utilization percentage against the time axis. CPU I/O Waiting Category: OS, Utilization CPU I/O Waiting shows the input output performance of the CPU while communicating to external interfaces. The graph is plotted with the CPU I/O waiting percentage against the time axis. Free Memory Category: OS, Performance The physical free memory available in MB is shown. The graph is plotted with the free space in MB against the time axis. State Category: OS, Exception Situations The SAP program SAPOSCOL should be running on every host of the System. This value displays the availability of this program User Utilization Category: OS, Utilization The average utilization of all the users in the host system is displayed. This utilization includes the user usage of the CPU. The graph is plotted with the user utilization percentage against the time axis.

Page 19 of 39

System Utilization Category: OS, Utilization The average utilization of all the resources in the host system is displayed. This utilization includes the system usage of the CPU. The graph is plotted with the system utilization percentage against the time axis. Response Time Category: SAP-ABAP, Performance The dialog response time is the processing time in the SAP application server consumed for a dialog step including database processing time. The graph is plotted with the response time in ms against the time axis. Users Logged In Category: SAP-ABAP, Security The users logged in displays the number of users logged on to a particular application server against a time axis PrivMode Utilization Category: SAP-ABAP, Utilization Private mode is where the heap memory data gets exclusively allocated to the user and is no more shared across the system. PrivMode Utilization is an indicator of the usage of the extended memory. The graph is plotted with the PrivMode utilization percentage against the time axis. Background Utilization Category: SAP-ABAP, Utilization Background utilization reports on the utilization in percent of the background work processes in the SAP system.. The graph is plotted with the background work process utilization percentage against the time axis. Dialog Steps Category: SAP-ABAP, Performance A dialog step is the processing needed to get from one screen to the next. It includes all processing that occurs after the user issues a request, up to and including the processing needed to display the next screen. The graph is plotted with the number of dialog steps against the time axis. DB Request Time Category: SAP-ABAP, Performance A large portion of the execution time of a dialog is due to the reading or changing of data in the underlying database. This value shows the database processing time. The graph is plotted with the DB request time in ms against the time axis. Spool Utilization Category: SAP-ABAP, Utilization Spool Utilization reports on the utilization in percent of the spool work processes in the SAP system. The graph is plotted with the spool utilization percentage against the time axis. R3Paging Used Category: SAP-ABAP, Utilization Paging enables the roll area to be extended at ABAP runtime when a large dataset is handled. R3Paging area used percentage is displayed here. The graph is plotted with the R3Paging used percentage against the time axis.

Page 20 of 39

Program Directory Used Category: SAP-ABAP, Utilization Program buffer contains the compiled SAP programs. Program directory used is the utilization of this directory in percentage. The graph is plotted with the directory used percentage against the time axis. Table Definition Directory Used Category: SAP-ABAP, Utilization Table definition buffer directory contains the table definitions from the SAP repository, which are stored in table DDNTT. Table definition directory used is utilization of this directory in percentage. The graph is plotted with the directory used percentage against the time axis. Timeout Category: SAP-JAVA, Exception Provides the timeouts frequency per minute of the java sessions for the dispatcher and server nodes TotalLogFilesSize Category: SAP-JAVA, Exception Provides the size of log file for the dispatcher and server processes Requests Performance

Component calls Category: SAP, Performance Provides the number of component calls received by the server node Average response time Category: SAP, Performance Provides the average response time of the j2ee server node.

Request Category: SAP-JAVA, Utilization capacity Provides the number of requests to the j2ee server node. Session Category: SAP-JAVA, Utilization capacity Reports the number of http sessions and security sessions established on the j2ee server node. Threads Category: SAP, Utilization capacity Application threads are involved in the processing of customer requests. System threads are used for internal tasks. Provides the thread counts for the dispatcher and server nodes. Counters Category: SAP, Exception Reports the number of http sessions and security sessions established on the j2ee server node. Communication Category: SAP, Utilization capacity Provides the cluster communication between J2EE nodes Memory Category: SAP, Utilization capacity The memory service on SAP provides data for the memory usage in Java Virtual Machine.

Page 21 of 39

SQL batches Category: Database-SQL Server, Performance The number of transact SQL command batches received by SQL server per second is displayed. CPU Used by SQL Category: Database-SQL Server , Utilization capacity The average utilization of all the SQL queries in the host system is displayed. This utilization indicates the part of usage of the CPU. Data Hit Ratio Category: Database-SQL Server, Utilization capacity The data hit ratio is the percentage of pages found in the cache without having to read from the disk. The ratio shows the average percentage. Millisecs/access for templog.ldf Category: Database-SQL Server, Performance This displays the frequency at which the database log file is accessed. Days since last backup Category: Database-Oracle, Performance The definition of a backup being too old is dependent on the type of system involved. This shows the backup frequency of the systems. Last succ. update statistics Category: Database-Oracle, Performance Update statistics are run to make sure that the database statistics are up-to-date, so improving database performance. Buffer cache Category: Database-Oracle, Utilization capacity The database buffer cache is the area of the system global area(SGA) used to hold copies of data blocks read from the disk. User processes cannot read data directly from data files, which is why all data must first be read into this buffer cache. The percentage of times when the data is found in the buffer cache is displayed Library cache Category: Database-Oracle, Utilization capacity The Library cache is a piece of memory within the system global area that Oracle uses in order to store SQL Statements. Whenever a Process issues a SQL Statement, the text of the statement goes into the library cache where the statement is parsed and validated. Redo log buffer Category: Database-Oracle, Performance The redo log buffer is a RAM area that works to save changes to data, in case something fails and Oracle has to put it back into its original state. When Oracle SQL updates a table, redo images are created and stored in the redo log buffer. Last succ. complete database backup Category: Database-Oracle, Performance The definition of a backup being too old is dependent on the type of system involved. This shows the backup frequency of the systems.

Page 22 of 39

Log directory Category: Database-Oracle, Utilization capacity Log directory comprises of archive logs which is critical for a database. Log files are managed by log archiving. The size of the log directory is displayed. Automatic Data Storage Category: Database-DB2, Utilization capacity An automatic storage database is one in which table spaces can be created and whose container and space management characteristics are completely determined by the database manager. Catalog cache quality Category: Database-DB2, Utilization capacity The catalog cache is referenced whenever a table, view or alias name is processed during the compilation of an SQL statement. Catalog cache size indicates the maximum amount of database heap space that the catalog cache can use. Deadlocks Category: Database-DB2, Performance A deadlock occurs when two or more application processes each hold locks on resources that the others need. Last successful backup Category: Database-DB2, Performance The definition of a backup being too old is dependent on the type of system involved. This shows the backup frequency of the systems. Free Data Space Category: Database-MaxDB, Performance Provide the free data space in MB Free Log Space Category: Database-MaxDB, Performance Size of the log segments also includes size of log area that is not backed up. This displays the free space of the log files over the database. Data Cache Hit rate – total Category: Database-MaxDB, Utilization capacity The data hit ratio is the percentage of pages found in the cache without having to read from the disk. The ratio shows the average percentage of data pages found in the cache since DB was started. The graph is plotted with the utilization percentage against the time axis. Log Queue Overflows Category: Database-MaxDB, Utilization capacity The main memory area required for logging is called the log queue. The size of a log queue is determined by database parameter and is reported here. Last successful Complete Data Backup Category: Database-MaxDB, Performance The definition of a backup being too old is dependent on the type of system involved. This shows the backup frequency of the systems.

Page 23 of 39

3.3 Monitoring

3.3.1 User/Security Monitoring

User data in SAP is client specific. Hence the credentials for each client will have to be maintained in KaarWatch. The ABAP credentials for each SID/client can be maintained after logging in as Administrator. („Maintain ABAP credentials‟). A communication userid with authorization S.A_SYSTEM and its password should be entered, tested and saved in the screen „Maintain ABAP credentials‟. Once this is done, the User/Security monitoring module can be used. For a selected SID and client(for which the user credentials are maintained), KaarWatch reports on the percentage of expired users, locked users and also the category of users in pie charts and also in a grid. Users can be locked/unlocked from KaarWatch.

LOCKED / EXPIRED USERS:

USER DETAILS:

3.3.2 Background Job Monitoring

When the user selects the SID, KaarWatch provides a pictorial overview of the Background jobs for that day in the selected SID. The run time of the jobs can be viewed from the scheduler. The background job overview for a different date/time can also be obtained. The jobs can be filtered on the status, job name and/or username.

Page 24 of 39

3.3.3 Workload Analysis

A graphical representation of the workload statistics for a selected time range for each SID and/or instance is provided. This includes the User profile and the Transaction profile. User may switch between a graphical and grid format.

USER PROFILE:

TRANSACTION PROFILE:

Page 25 of 39

3.3.4 Change Monitoring

Changes to key basis objects are displayed. This includes changes to client settings and changes to the instance profile files. The client details are provided along with the last change date. The profiles parameters and their values for the current version and for all previous versions can be viewed. Any system locks older than 24 hours is also displayed.

The following additional functionality will be available in the licensed version.

Delete locks

Notification to the user when changes to client and/or profile settings occur

3.3.5 Concurrent Users

A list of concurrent users for the selected SAP system / instance(s) is provided in a grid. The grid provides the login client of the user, the terminal he is logged in from and time of the last dialog step performed by the user.

3.4 Task List

For each configured instance, KaarWatch provides a task list of all the checks that need to be performed on that instance. The task list is generated by KaarWatch and has tasks specific to the SAP Application. This assists the Basis administrator in ensuring routine tasks are performed and logged.

Page 26 of 39

Each basis administrator should have a KaarWatch userid with the SAP instance assigned to him. A light weight java application is downloaded on each of the basis administrators‟ desktop to perform the daily tasks. This may be downloaded by clicking on the link in the Daily Tasks page. Each of these desktops should have the SAPGUI and Java run time environment 1.4.2 or higher installed. The following environment variables are set in the administrators‟ desktops - SAPGUI_URL and KW_URL. eg. SAPGUI_HOME = C:\Program Files\SAP\FrontEnd\SAPgui KW_URL = http://<IP address of the KaarWatch server>/KaarWatch Double click KaarWatchTaskList.jar file (or) type java -jar KaarWatchTaskList.jar in command prompt to launch the application. Each administrator logs in with his KaarWatch userid into the application.

The instances that have been assigned to the user is available in the dropdown in the next screen. The basis admin should save his SAP dialog userid and password in KaarWatch.(Administration > Configure Daily Tasks). This enables KaarWatch to login to the transaction that the user clicks on in the java application. The user selects the instance for which daily checks are to be performed and clicks on the transaction code to check the SAP system and logs his comment in the comments section.

Page 27 of 39

The user then submits the tasks to KaarWatch. The tasks may be performed any number of times. The comments and the date and time the tasks have been performed are saved in KaarWatch. The basis administrator may then create a report of the tasks performed from the Daily tasks page.

Page 28 of 39

3.5 Reports

A report of the KPI and alerts for a selected SAP instance over a period of time can be obtained from the Reports menu. User selects the instance from the dropdown. The relevant KPIs get listed in the tree. The user then selects the KPI and the date/time range. A report gets generated based on the selection.

4 Appendix

4.1 Glossary

SID - An SAP system is identified by its SAP System ID, which consists of three letters or digits (e.g. PRD, P10, etc.) Host Name - Name of the computer on a network containing resources, which can be accessed by other computers on the network. IP Address - Unique number given to the computer Hardware where SAP System is installed. System Type - A function of a system in the SAP system group from the point of view of the landscape Instance number -Two digit number that identifies the SAP instance. Each instance of the SAP application server requires its own instance number. (e.g. 00, 01, etc.) ABAP Client - Three digit number assigned to the SAP system, which represents a Separate Organizational unit. Response Time - Average Response time to process the Dialog Step

Page 29 of 39

Frontend Response Time - Average time taken from SAP frontend to the application server.

Queue Time - The average time an unprocessed dialog step waits in the dispatcher queue for a free work process. Load+GenTime - Average time required to load and generate objects Roll Time - Time taken to allocate the Sequential memory allocation to the work Process DBRequestTime - Average time for processing logical database requests Utilization - Average usage of dialog work processes of an application server PrivMode Utilization - Percentage of dialog work processes in PRIV mode Number Of WpDIA - Number of dialog work processes Errors In WpDIA - Number of errors in dialog work processes Queue Length - Average usage of dispatcher wait queue for dialog work processes Program Errors - ABAP program terminations in dialog work processes Dialog Steps - Average number of dialog steps per minute Users Logged In - Number of logged-on users in Application server Utilization - Percentage of work process load in Spool Number Of WpSPO - Number of spool work processes Errors In WpSPO - Number of errors in spool work processes Queue Length - Percentage of Utilized area of dispatcher queue Gateway Clients - Percentage of the Current Clients in the Gateway Gateway Connections - Percentage of the Current Gateway Connection Version - Current Version of the Internet Communication Manager No Of Threads - Current number of threads in the Internet Communication Manager Utilization - Average percentage usage of background work processes of a Server Number Of WpBTC - Number of background work processes Errors In WpBTC - Number of errors in background work processes Ended WpBTC - Number of completed background work processes

Page 30 of 39

Program Errors - Program error when executing background jobs Aborted Jobs -Terminated jobs on an application server Response Time - Average response time per dialog step Queue Time - Average wait time in dispatcher queue Utilization - Percentage load for update task work process Number Of WpUD1 - Number of update1 work processes Errors In WpUD1 - Number of errors in update 1 work processes Response Time - Average response time per dialog step Queue Time - Average wait time in dispatcher queue Utilization - Percentage load for update task work process Number Of WpUD2 - Number of update2 work processes Errors In WpUD2 - Number of errors in update 2 work processes Abap Error In Update - Update requests with errors Enqueue Freq - Enqueue operations (logical data locks) per minutes that are coming from another instance to the central instance Utilization Owner Names - Maximum number of lock owner IDs that can be stored in the lock

table. Lock owner IDs are assigned to a user context or to an update request.

Utilization Granule Argument - Maximum number of different lock arguments that the lock table can contain; locks of different owners or with different lock modes, but with the same lock argument occupy one entry Utilization Granule Entries - Maximum number of elementary locks that the lock table can Contain Queue Length - Length of the enqueue queue as a percentage of its maximum Length Errors In WpENQ - Number of errors in the enqueue work processes since the monitoring segment was created Peak No Of Threads - Max. number of threads reached No Of Connections - Current number of open connections MPI Size Total - Message Passing Interface Total Size Cache Size MB - Configured HTTP Server Cache Size

Page 31 of 39

Cache Size Used - Memory Used of the HTTP Server Cache (in Percent) Max Cache Entries - Maximum number of HTTP Server Cache Entries Cache Entries Used - Current number of HTTP server cache entries in use (in percent) Cache Accesses - Number of cache accesses Cache Hits - Number of hits in the HTTP cache (in percent) Max Ufo Entries - Maximum Number of HTTP UFO Cache Entries R3 Developer Trace - Developer traces are records of the SAP work processes that contain technical information for finding errors. R3 System Trace -The system trace records internal SAP system activities. It provides system monitoring and simplifies error correction R3 Paging SizeKB - Current size of paging area R3 Paging Used - Currently used paging area [%] R3 Paging Used MaxKB - Maximum paging area load [KB] since system start R3 Roll SizeKB - Current size of roll area [KB] R3 Roll Used - Currently used roll area [%] R3 Roll Used MaxKB - Maximum Load of roll area [KB] since system start Es Total - Total size of extended memory Es Peak - Extended memory: high-water mark since startup Heap Total - Extended memory: high-water mark since last query Heap Peak - Heap memory: High-water mark since startup WpDia Restart - No. of dialog WP restarts since startup WpNonDia Restart - No. of batch WP restarts since startup Syslog Freq - Frequency of system log messages in SAP application server Short Dumps - Show the Status for the ABAP error. Short Dump Frequency - Frequency of Short Dump in the System. Free space - Hard disk space availability Percentage Used - Usage of the available storage space for the file system as a Percentage

Page 32 of 39

CPU Utilization - Average usage of the CPU in a host system; the value shows how intensively the CPU is used and how much processing capacity is still available 5minLoadAverage - Average number of processes in a host system that are ready for execution but must wait to be processed by the CPU Idle - Idle time for all CPUs in the system CPU I/O Waiting - CPU wait is the amount of time spent on hardware IO, It is a technique in which a process repeatedly checks to see if a condition is true, such as whether keyboard input is available, or if a lock is available. Spinning can also be used to generate an arbitrary time delay, a technique that was necessary on systems that lacked a method of waiting a specific length of time. User Utilization - The amount of CPU utilization in a host system by maximum no. of users should not affect the performance of the system, System Utilization - System utilization is generally measured in terms of the utilization of individual system components and the overlap of activities of two or more system components. Number of CPUs - No. of CPUs available, Memory availability, disk with highest response time, Swap History etc. Free Memory - The amount of unused RAM available in the Server. Configured Memory - The amount of application data that occupies the available RAM space in the Server. Page In - Average number of page-ins per second; a page-in occurs if a process must access a data page that is not available in the main memory. Before the process can be continued, the operating system must retrieve the page from the paging file Page Out - Average number of page-outs per second (page-out occurs if a page is stored out of the main memory to make room for the pages required by other processes) State - Information about the operating system is running on a system or stopped due to some reasons Collisions - Collisions in the LAN, in which two stations transport a packet at the same time on the same channel; this leads to the destruction of both packets and means that they must be sent again

4.2 DB Configuration for Alerts and KPIs

If Alerts and/or KPIs are missing for the DB component, then ensure the job SAP_CCMS_MONI_BATCH_DP has been scheduled to run periodically on the SAP instance. This job is required to report on alerts and KPIs for the DB. This is a standard SAP job and should

Page 33 of 39

have been scheduled during the post-installation tasks. If this job is running successfully, then the alerts should be available in DB02> Alerts

4.3 Registering of Java Instance into an ABAP Instance

KaarWatch reads the alerts and KPI for SAP instances that have an ABAP stack, Java Stack

and ABAP+Java Stack. To be able to read the Alerts and KPI for a SAP instance that has a

Java stack, the Java stack will have to report its values into an ABAP stack with WEBAS 6.40.

For an Instance that has an ABAP+Java stack, the Java stack will have to report into

the ABAP stack with the same SID

For an Instance that has only a Java Stack, it can report into any ABAP stack with

WEBAS 6.40

For this reporting to happen, SAP provides an agent called sapccmsr. The executable

(sapccmsr) is available in the exe directory of the SAP Instance. The sections below list the

steps to be performed to activate this agent. Follow the steps in Section 1 for Instances with

ABAP+Java stack and Instances with only a Java Stack (eg. NWDI, EP systems). Follow the

steps in Section 2 for Instances with only a Java Stack. This will ensure that the database

parameters of the Java Stack are reported into the ABAP stack.

4.3.1 CCMS Configuration

Steps 1-3 are performed in the ABAP System (CEN) into which the JAVA stack will report the alerts.

1. RZ21> Technical Infrastructure> Configure Central System >Create CSMREG Service

User

Page 34 of 39

2. RZ21> Technical Infrastructure> Configure Central System > Generate Configuration file

for agent

Page 35 of 39

3. In the hosts file of the CEN system, make an entry to represent the hostname and IP

address of the Java stack system

Steps 4 - 14 are performed in the Java host on which the SAP Java stack is installed

4. Log on to the host as <SID>adm.

Copy the CSMCONF start file created in Step 2 to the following directory on

the host of the Java Stack SAP Instance.

On Microsoft Windows: [SAP Application Drive

]:\usr\sap\ccms\<SysID>_<Inst. Nr.>\sapccmsr

On Unix : /usr/sap/ccms/ SysID>_<Inst. Nr.>\sapccmsr

5. In the services file of the Java Stack system, make an entry for the SID and Instance

number of the CEN System.

sapms<SID> 36<Inst.No.>

eg: sapmsECP 3600, where SID is the SID of the CEN System and

Inst.No. is the Instance number of the CEN system

6. In the hosts file, make an entry to represent the hostname and IP address of the CEN

System

7. Change directory to prfclog from the command prompt

On Microsoft Windows: [SAP Application Drive ]:\usr\sap\prfclog

On Unix : /usr/sap/ccms/prfclog

8. Execute the following command to register the CCMS of the Java Stack

sapccmsr.exe –j2ee –R pf=”path of the Instance Profile”

Page 36 of 39

9. On the welcome screen , enter „n‟ for the question – “additional CENTRAL system y/n?”

10. Enter the details of the CEN system as shown below. ( SID, client, any communication

user in the CEN System with Profile SAP_ALL , default login language of CEN System,

hostname of the CEN message server and password for the communication user )

11. Enter the gateway info of the CEN system

12. Enter the details of the communication user (created in Step 2) of CEN system

13. Register the service SAPCCMSR.00 at Windows Service Control Manager: ( Enter start

type of service as auto, <sidadm> userid and password of the CEN system

Page 37 of 39

\

This completes the CCMS configuration of the SAP Instance with a Java stack into the CEN system.

4.3.2 Remote DB Configuration

Perform the following steps in the SAP system that has a Java Stack only to register the alerts of the database into an ABAP system. This step need not be performed if you are configuring a SID with an ABAP+Java Stack into KaarWatch.

1. Call the DBA Cockpit in the Java SID

The screen DBA Cockpit: System Configuration Maintenance appears. It displays a list of all systems available with a Stop, Go, or Inactive icon, which shows the current system status.

When you start the DBA Cockpit for the first time, the local system is automatically added to the list of all systems available. At least one system entry is displayed.

2. Choose Add.

The screen Configuration: System Administration – Add System Entry appears.

3. Specify the connection data as follows:

a. In the System field, enter the name of the system you want to monitor.

This name is a unique ID and does not need to be the SAP system ID. You can choose any name except the SAP system ID of the local system, which is reserved for the local system entry.

Except for the local system entry, Remote Database is already selected.

b. Select Database Connection.

c. Enter the name of the database connection. If the database connection does not yet exist, you are directed to the System Administration Details screen where you can specify all relevant data for the new connection.

After you have saved your entries, you are redirected to the screen DB Connections: Add Connection Entry.

Page 38 of 39

Note: The test user is a database user and is created in the DB of the JAVA system.

After the connection data has been completed, it is displayed on the System Data tab page. You can enter additional data on the Administration Data tab page as follows:

Enter a description of your system.

Depending on the database platform select the options for how you want to collect monitoring data:

If alerts are to be provided for the RZ20 alert monitor, select Collect Alert Data.

If data about the performance or the size of database objects is to be collected, select Collect History Data.

If the task of collecting monitoring data is running on the remote system, select Data Collection by Remote System.

If data for the central planning calendar is to be provided, select Collect Central Planning Calendar Data.

4. Save your changes.

If you get an error as shown below, do the following steps:

Page 39 of 39

1. Save the Connection

2. Select the Saved the Java System Database

3. Click the execute scripts with standard Set and then Test the Connection.