CCMS Monitoring Agents - SAPCCMSR (with Option j2ee)

SAPCCMSR agent monitors components on which there is no active SAP instance (such as log files, TREX, stand-alone databases, or operating system components). SAPCCMSR is closely connected with the monitoring central monitoring system.
After its installation, the CCMS agent SAPCCMSR attempts to attach itself to a monitoring
segment in shared memory when it is started. If this segment does not yet exist, the agent creates it. SAPCCMSR always works in a shared memory segment that is independent of running SAP systems. The central monitoring system must have a release status of at least SAP Basis 4.6B.


SAPCCMSR with Option j2ee
The functional principle of SAPCCMSR has been extended in case the SAPCCMSR CCMS agent is monitoring a J2EE Engine. In a case of this type, it must be possible that the monitoring segment of the SAPCCMSR agent does not belong to the central monitoring system. This is achieved by extending the system term to include Java components (such as J2EE Cluster). The
SAPCCMSR agent with the -j2ee option exists for this purpose.
Note :
To use SAPCCMSR with option j2ee, you need a central monitoring system as of SAP Web AS 6.40 Support Package 1.
The monitored J2EE Instance requires at least SAP Web AS 6.30 Support Package 4.

It is easier to understand the other steps if you use the following analogies:
ABAP - ABAP System , Application server , Work process

Java - J2EE Cluster , J2EE Engine , Virtual Machine (VM)

A system is no longer only a quantity of classical application servers with an ABAP runtime environment, but simply a number of associated components that have a common system name.
Combinations of ABAP instances and Java instances can also create a system, if all of these parts
are combined under one system ID.
You specify the system ID and the system number of the monitored Java instance during the registration of the agent using the instance's profile

When monitoring, it should be possible to display the data for the ABAP instances and the Java
instances of the same system in a central CCMS under the system ID of the monitored system. As far as possible, a Java instance should not be different from an ABAP instance; it should also be possible to monitor all instances with the same system ID locally as one system unit.