Start of Content Area

Background documentation Monitoring Information Not Available in CCMS (RZ20)  Locate the document in its SAP Library structure

Problem Description

No monitoring information is displayed in the CCMS Alert Monitor (transaction RZ20) of the central monitoring SAP Web AS ABAP system. However, monitoring information is available in the Visual Administrator of the J2EE server, for example status information in the J2EE status monitors.

Scenario Type:

Error analysis

NetWeaver Component:

Web AS Java: J2EE Engine (BC-JAS)

Validity:

J2EE Version >= 6.30 on Windows and Unix platforms and a Web Application Server >= 6.40 SP1

Decision Roadmap

Main Tools

     CCMS configuration transaction RZ21

     Visual Administrator

Analysis

The following graphic gives you an overview of the analysis process. The numbers refer to the different steps of the analysis process described in detail below.

This graphic is explained in the accompanying text

1.   Checking Agent Status

You start by checking the status of the agent in the central monitoring system (CEN). To do so, open the customizing transaction of the CCMS Alert Monitor RZ21, and choose Agents for Remote Systems   Display Overview. In the Communication Status column, you can see if the agent is running:

     If the Agent status is OFFLINE, you can switch the agent on manually in the same screen by choosing ONLINE in the context menu. Make sure that you are in Change mode:

This graphic is explained in the accompanying text

     If the Agent status is ONLINE, SHUTDOWN, or Communication Failure status, continue with step 2 ‘Network Connection Check’.

Note

If there is no agent at all, you can register one. For more information, see Installing an Agent on a Java Instance (Java Standalone System).

2.   Network Connection Check

In CEN, check the network connection to the host. To do so, choose Connection test.

     If there is no connection error, you can continue the analysis with step 3 ‘Log File Analysis in CEN’.

     If there is a connection error as shown in the picture below, continue with the step 4 ‘Checking if the Agent Is Running on J2EE Host’.

This graphic is explained in the accompanying text

3.   Log File Analysis in CEN

If the agent is generally available and the connection test was successful, you should check the log file sapccmsr.log from CEN. To check this log file in RZ21, choose Agent working directory and open sapccmsr.log. In the log file, consider especially all problems concerning RFC and the gateway.

This graphic is explained in the accompanying text

If you cannot find the problem in the log file, reregister the agent as described in step 7 ‘Reregistering Agent’.

 

4.   Checking if Agent Is Running on J2EE Host

If the network connection check is negative, you should check if the agent is running on the J2EE host:

On a Windows platform, go to the system services and make sure the service SAPCCMSR.<Instance number> is started:

This graphic is explained in the accompanying text

On a Unix platform, check the availability of the SAPCCMSR process using command

ps –ef | grep sapccmsr:

UID      PID  PPID C STIME TTY TIME  CMD

<sid>adm 176  1    0 Dec 19    0:39  /usr/sap/<sid>/SYS/exe/run/sapccmsr –DCCMS –j2ee pf=<INST_DIR>/SYS/profile/<SYS_ID>_<instance name>_<hostname>

If the agent is running, continue with step 6 ‘Checking Agent Log Files on Host’.

If the service is not running, continue with step 5 ‘Restarting the Agent’.

5.   Restarting the Agent

If the agent is stopped on the J2EE host, try to start it as follows:

     On Windows platforms, start service SAPCCMSR.<Instance number> from system services.

     On Unix platforms, execute command

/usr/sap/<sid>/SYS/exe/run/sapccmsr –DCCMS –j2ee pf=<INST_DIR>/SYS/profile/<SYS_ID>_<instance name>_ <hostname> 

If starting the agent does not solve the problem, check the agent log files on the host as described in step 6.

6.   Checking Agent Log Files on Host

If the agent process is running, you should analyze the following agent trace and log files on the host:

     <INST_DIR>/CCMS/<SYS_ID>_<INST_NUMBER>/sapccmsr.log

     <INST_DIR>/CCMS/<SYS_ID>_<INST_NUMBER>/dev_rfc.trc

The following problems may have occurred:

     Incorrect logon data for the CSMREG user:

>TS> Thu Dec 18 16:30:21 2003

T:688 ======> User not authorized. Session terminated

T:688 <* RfcReceive [10] : returns 3:RFC_SYS_EXCEPTION

In this case, reinstall the agent providing correct logon information for the CSMREG user according to step 7 ‘Reregistering Agent’.

     CSMREG user is locked:

>TS> Thu Dec 18 16:31:21 2003

T:688 ======> User is locked. Please notify the person responsible

T:688 <* RfcReceive [11] : returns 3:RFC_SYS_EXCEPTION

Log on to the CEN system and unlock the user CSMREG.

This graphic is explained in the accompanying text

     CSMREG user does not have required permissions:

WARNING: RFC client functionality configured, but logon failed for  [SOL:001:CSMREG] ==> pushing data into CCMS cache disabled.

Cause: Missing permission (RFC permissions for e. g. function group SCSM*)

In transaction SU01, make sure that the role SAP_BC_CSMREG was assigned to the user CSMREG.

This graphic is explained in the accompanying textIf you cannot find any problem in the log file on the host, reregister the agent according to step 7.

7.   Reregistering Agent

To reregister the agent, use the appropriate service in the Visual Administrator:

...

       1.      Choose Cluster <SysID> Dispatcher Services Monitoring.

       2.      Choose the CCMS Agent Configuration tab.

       3.      Choose Unregister and then proceed as mentioned in the following procedure: Installing an Agent on a Java Instance (Java Standalone System).

Additional Information

CCMS Agents

 

End of Content Area