CCMS Configuration

Central system Monitoring with Solution Manager

Doc Name CCMS Conf igurati on Doc
Version 1.0
Number N/A
Author Suraj Kumar Gond



Table of Contents
1 DOCUMENT OVERVIEW ............................................................................................................................... 3
1.1 Document Purpose ...................................................................................................................................... 3
1.2 Document Scope ............................................................................................ Error! Bookmark not defi ned.
1.3 Audience ........................................................................................................ Error! Bookmark not defi ned.
2 INTRODUCTION .......................................................................................................................................... 4
2.1 Components of Monitoring ............................................................................................................................ 4
3 OVERVIEW OF THE CONFIGURATION STEPS ...................................................................................... 6
4 CONFIGURATION STEPS IN DETAIL ..................................................................................................... 7
4.1 Adjusting the Central Monitoring System (CEN) ............................................................................................. 7
4.2 Monitoring ABAP Instances .......................................................................................................................... 9
4.3 Monitoring J ava Instances .......................................................................................................................... 10
4.4 Checking the CCMS Agent ( Installed ) ........................................................................................................ 10
4.5 Configuring the System to be monitored ...................................................................................................... 11
4.6 Defining & Assigning Autoreaction (for sending e-mail for an alert) ................................................................ 13


1 Document Overview
1.1 Document Purpose
The purpose of this document is to outline the Central system monitoring configuration using CCMS in
Solution Manager


2 Introduction
With the monitoring architecture of the CCMS (Computing Center Management System),
SAP provides a flexible and universally-usable infrastructure with which we can monitor
our entire IT landscape centrally, and which reports problems quickly and reliably.
The concept of the monitoring architecture is to make all required information available
in a central monitoring system (CEN), and therefore to make the administrators work
easier.
2.1 Components of Monitoring
2.1.1 Alert Monitor
The alert monitor is the central tool with which we can efficiently administer and monitor
distributed SAP solutions or client-server systems. The alert monitor displays problems quickly
and reliably.
2.1.2 CCMS Agents
CCMS agents are independent processes with an interface using RFC to a central monitoring
system and an interface to the shared memory. These agents have the following properties:
A connection to CEN using RFC, to ensure greater downtime security and general
availability
Use of the push technology to optimize performance when reading and writing
monitoring attributes and alerts
Inclusion of the operating system collector SAPOSCOL to monitor processes at
operating system level.
Connection to systems with no SAP NetWeaver Application Server
Monitoring of any log files

There are various CCMS agents, including:

Agent Task
SAPCCMSR Monitoring of components on which no SAP ABAP instance is
active, such as the J2EE Engine or SAP IPC
SAPCCM4X
Monitoring of SAP ABAP systems as of SAP Basis 4.X

We download the ccmagent_<version>.sar file from service marketplace with the following path and
uncar the file place in a directory (/tmp)

http://service.sap.com/swdc --> Download Support Packages and Patches Entry by Application
Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER 04 ABAP Server SAP
KERNEL 6.40 32/64-BIT <operating system> Database Independent.







3 OVERVIEW OF THE CONFIGURATION STEPS
This section lists the configuration steps required for the different SAP NetWeaver
components. First perform the following steps:

In CEN: Adjusting the Central Monitoring System (CEN)
For every instance of a J2EE Engine: Registering a CCMS Agent SAPCCMSR
For every ABAP instance: Registering a CCMS Agent SAPCCM4X


4 CONFIGURATION STEPS IN DETAIL
4.1 Adjusting the Central Monitoring System (CEN)
4.1.1 Activating Background and Central System Dispatching
To execute an auto-reaction in CEN for alerts from remote systems, central system dispatching
needs to be activated in all monitored ABAP systems in client 000.
Background dispatching is performed by the job SAP_CCMS_MONI_BATCH_DP.

RZ21 Choose Technical Infrastructure Local Method Execution Activate
Background Dispatching.

Activate central system dispatching in CEN: Central system dispatching is performed by the job
SAP_CCMS_CENSYS_DISPATCHER

RZ21 Choose Technical Infrastructure Configure Central System Activate Central
System Dispatching.

4.1.2 Creating the CSMREG User
Create the CSMREG user from RZ21








Password: - n0tthot1
4.1.3 Creating the CSMCONF Start File for CCMS Agents
Generate the ccmconf file from OP1 and put it in the same location where ccms agent is kept.






4.2 Monitoring ABAP Instances
4.2.1. Registering a CCMS Agent SAPCCM4X
Copy the CSMCONF start file to the following directory :
/usr/sap/<SysID>/<inst.dir.>/log/sapccm4x

Run the following command to register the CCMS agent
sapccm4x R pf=<profile path>.
e.g. sapccm4x -R pf=/usr/sap/ED1/SYS/profile/ED1_DVEBMGS00_ud1sap01ed1

Provide the parameter information accordingly while registering the agent.
Meanings of the parameters:
Parameter Meaning
R/3 system ID System ID of CEN
client Valid client in CEN
user Valid user in CEN
language Language (such as en =English, de =German)

hostname of message server Host name of the message server in CEN
use Load Balancing Should load balancing be used [Y/N]?
group Logon group (only for load balancing)
hostname of message server Host name of an application server in CEN (only
without load balancing)
system number Instance number of the above application server
(only without load balancing)
route string Host and port of the SAProuter in the format
/H/<Router Host>/S/<Router Port>/H (only if the
connection to the central monitoring system
goes through a router)
trace level Set your trace level (0,1,2,3)
Hostname of gateway Host of the gateway, usually the message
server of CEN
System number Instance number
password Password of the above user; the password is
not stored, it is used only once for the logon
The same information to be provided for CSMREG user as well.

4.3 Monitoring Java Instances
4.3.1. Registering a CCMS Agent SAPCCMSR

Copy the CSMCONF start file to the following directory :
/usr/sap/ccms/<SysID>_<Inst. No.>/sapccmsr

run the following command to install CCMS Agent
sapccmsr R j2ee pf=<profile path>.
e.g sapccmsr -R -j2ee pf=/usr/sap/BD2/SYS/profile/BD2_J C01_ud1sap01bd2
4.4 Checking the CCMS Agent ( Installed )
In solution Manager (OP1) t-code os07

In solution Manager (OP1) t-code rz21


4.5 Configuring the System to be monitored

Explore the Client Specific Monitoring Node and add your system by clicking add new.
4.5.1.1 Define Auto-reaction Methods need to be monitored.




4.5.1.2 Define the threshold values.


for each maintenance function, we define the Threshold values.


Alert can be seen be selecting open alerts


4.6 Defining & Assigning Autoreaction (for sending e-mail for an alert)
4.6.1 Define Central AutoReaction (Method Name)
t-code RZ21
Copy the existing Method with a new name as z_...

Maintain the parameters in the method definition.

4.6.2 Assign Central AutoReaction
t-code : RZ21

Select System ID, MTE Class, Defined Central Autoreaction Assign Central Autoreaction.

Now, when an alert come, the alert mail is sent to specified mail ID.

Here is one sample mail for File System alert.