Showing posts with label CCMS. Show all posts
Showing posts with label CCMS. Show all posts

Setting Up the CCMS

The Computing Center Management System (CCMS) is shipped to every customer site pre-configured so that all internal functionality is intact. The consistency and/or accuracy of this functionality depends heavily on how the customer first configures the operation mode environment.

If operation modes, instances, or the timetable are not correctly defined, the CCMS will not display meaningful data. For example, the Job Scheduling Monitor will not be able to determine where background processes are running, the Alert Monitor may report improper operation of modes.

Before you can work with the CCMS, it must be set up correctly. You must define at least one operation mode.

To set up the CCMS:

From the main R/3 menu select Tools ® CCMS ® Configuration ® OP Modes/Servers.

Alternatively, use transaction code RZ04 .

The screen CCMS: Maintain Operation Modes and Instances is displayed. From this screen, you can create and change operation modes and instances.


If no operation modes have been defined, the test operation mode DUMMY will be displayed. This operation mode is configured automatically so that system functions such as the Control Panel and background job scheduling can be used.

The operation mode DUMMY cannot be used for operation mode switching.

Existing operation modes are listed as they were previously defined. For example, you may see one or more operation modes for daytime operation and one or more for nighttime operation.

To ensure the data accuracy of the system being monitored, you must define at least one operation mode and maintain the timetable.


  1. Define an operation mode

  2. Define the instances for the operation mode

  3. Maintain the timetable

What are the Authorization to Use the CCMS

To work with the CCMS, you require the authorization S_RZL_ADM .

S_RZL_ADM 1 gives you administrator authorization

S_RZL_ADM 3 gives you display authorization

Starting the CCMS Agent

Under Microsoft Windows NT the CCMS agent is automatically started, as the system starts the
associated service. If you have registered the CCMS agent under UNIX, the agent has not yet
been started. Start it using the appropriate command:


Agent Start Command
SAPCCMSR sapccmsr –DCCMS [pf=]
SAPCCM4X sapccm4x –DCCMS pf=
SAPCM3X sapcm3x –DCCMS [pf=]


Under UNIX, you must also ensure yourself that the CCMS agent is automatically started after a
restart of the server (for example, by entering the start command in INITTAB).


Computing Center Management System (BC-CCM) PDF Free download


Computing Center Management System (BC-CCM)

How to Use CCMS free downloads

How to Use CCMS
CCMS Agent Installation
CCMS Monitoring
CCMS rule Based Monitors Configuration Guide For Dummies
CCMS Rule Based Monitors Configuration Guide
CCMS SSNP TRAPS
CCMS Alert Management

Enabling security audit alert in CCMS

In this blog I'll show how to configure security audit alerts in CCMS, with security audit alerts you can keep close eye on security related issues of your system.

Following is step by step approach to enable security audit alerts in CCMS

  • Goto RZ20->SAP CCMS Monitoring Templates and copy Security template to your custom monitoring node (if you configured any), refer to above mention blog for reference.
  • To enable alerts in CCMS you need to activate security audit in your system.
  • Goto SM19 -> dynamic configuration.
  • Select Audit Class for alerts like "Dialog logon", "RFC/CPIC logon", "RFC call" etc.
  • Chose Events when you want alert:
    • All: on all events
    • Severe and Critical: only for important and critical events.
    • Only Critical: you want alert only for critical events.

SM19

  • Click on "Detail configuration" to see detail of important, critical and non-critical events.

Detail of events...

  • Activate configuration (don't forget to click on "Filter Active" checkbox).

  • Goto CCMS and security template and refresh it now.

Security alert in CCMS

Other important transactions related to Security Audit:

  • - SM18 - delete old audit logs
  • - SM20 - analysis of audit log.