SAPCCMSR with Option j2ee
Definition
The functional principle of the CCMS agent SAPCCMSR has been extended in case SAPCCMSR 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.
It is easier to understand the other steps if you use the following analogies:
ABAP |
Java |
ABAP System |
J2EE Cluster |
Application Server |
J2EE Engine |
Work process |
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 in its profile file (see Profile File of the CCMS Agents).
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.
Example
Monitored System with no ABAP Instances
SAPCCMSR monitors an instance of a Java system and registers itself with a central system CEN. The connection to CEN is also the primary RFC connection.
Monitored System with Java and ABAP Instances
SAPCCMSR monitors an instance of a system in which there is still at least one ABAP instance. In this case, the agent must be primarily registered with the local system, so that the system can be monitored locally as one unit.
Monitored System with Java and ABAP Instances, and a CEN
In addition to the case described above, the local system, to which the Java instance belongs, can be monitored by a central monitoring system CEN:
CCMS Agents start
page