cancel
Showing results for 
Search instead for 
Did you mean: 

hostctrl vs sapccmsr for stand alone database host of monitored ABAP system

Former Member
0 Kudos

Dear all, in the good old world we registered simply the sapccmsr agent with j2ee option on remote database host with ABAP targed of the related ABAP instance host and also the central monitoring system. Now I have to register the host in RZ21 'create remote monitoring system entry'. If the system is assigend to the CEN system, the monitoring segment is attached to the wrong system (CEN system); so I tried to assign it 'Host' to the correct remote ABAP system. Now the local monitoring segment is correctly assigned to the correct related ABAP system. The monitoring objects now are also displayed in the CEN system for the correct <SID>. But the central autoreactions are not assigned for the local monitoring segment of the remote system. What I have to do, to register the DB Host correctly as local monitoring segement locally on the related ABAP stack and also as remote monitoring segment on the CEN system?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Is this correct?:

Solman 7.0 EHP1

Monitored Systems up to 7.0 EHP 1

J2EE > instance agent > sapccmsr -j2ee

ABAP > instance agent > sapccm4x

J2EE stand alone > instance agent > sapccmsr -j2ee

DB/TREX > host agent > sapccmsr without -j2ee option

Monitored Systems from 7.0 EHP 2

J2EE > instance agent > sapccm4x

ABAP > instance agent > sapccm4x

J2EE stand alone > instance agent > SMD Agent

DB/TREX > host agent > sapccmsr without -j2ee option

With Solman 7.1

without sapccm4x or sapccmsr; all with Hostcontrol and RZ21 'remote monitoring entry' and/or SMD Agent for J2EE stand alone?

But, we registered in past the Host agent for stand alone DB instances like J2EE instance agent registration to have an attached local monitoring segment to the correct CI and the remote monitoring segment to the CEN system.

Former Member
0 Kudos

Hallo Rene,

There are many changes at agent registration up to kernel: 71X

With a 720 kernel it is forbidden to start the SAPCCMSR -j2ee agent because with the 720 kernel we only do have one monitoring segment in which the ABAP and J2EE monitoring structure and data is stored.

Please also be sure that you correctly disabled the new SAPSTARTSRV SAPCCM4X agent, as described in note #1368389  because it is not allowed to start both of the SAPCCM4X agent at the same time.

#1022502 - CCMS agent in sapstartsrv: Composite note

All CCMS agents can copy data from the SAPOSCOL shared memory segment to

the CCMS monitoring segment and transfer it to a central monitoring

system. This means that the data is visible in the CCMS monitoring

architecture and is displayed both in the familiar transactions ST06

/OS07 and in the Alert Monitor (transaction RZ20).

If no ABAP instance is installed on a server and an SAP systems wants to

read data from the SAPOSCOL segment which is located on this so called

standalone server, an SAPCCMSR agent needs to be installed on the same

server as the server on which the SAPOSCOL program is running.

#1068204 -  New monitor template for database monitoring

I would like to suggest some online dokumentation:

Installing/Registering the CCMS Agents for Experts

http://help.sap.com/saphelp_nw70/helpdata/en/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

Monitoring Operating System Data with CCMS Agents:

http://help.sap.com/saphelp_nw70/helpdata/en/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

RB

Tamas