Registering SAPCCMS with the Option -j2ee 

Use

The CCMS agent SAPCCMSR with Option j2ee has been especially conceived for monitoring the J2EE Engine. The monitoring segment of the agent in this case belongs to the local system of the J2EE Engine, and not to the central monitoring system.

Note that this agent type requires a current status of the Java Monitoring API to monitor the J2EE Engine. This status must be at least Patch Level 7.

You can download the JMonAPI from the SAP Service Marketplace. The archive is in the same path as the archive for the CCMS agents (see Downloading the CCMS Agents). You can identify the status from the file name of the archive (JMON_<Patchlevel>_..).

Registering SAPCCMS with the Option -j2ee in Dialog

During the registration of the CCMS agent with the option -j2ee, you must first answer the questions of whether there is at least one ABAP instance in the agent’s system (parameter SAPSYSTEMNAME of the Profile File of the CCMS Agents), and whether there is a central monitoring system in your system landscape. The various options are described in SAPCCMSR with Option j2ee.

The system ID and system number of the agent’s local system are specified with the profile parameters SAPSYSTEM and SAPSYSTEMNAME, meaning that you no longer have to specify this information in the registration in dialog.

After you have entered this information about your system landscape, perform the rest of the registration as described in Registering the CCMS Agents in Dialog.

Dialog-Free Registration of SAPCCMS with the Option -j2ee

If you want to install SAPCCMSR with the option -j2eedialog-free, note that if there is an ABAP instance in the agent’s local system, the local system is formally its primary central monitoring system (see Dialog-Free Registration of the CCMS Agents and Registering with Multiple Central Monitoring Systems). The CSMCONF start file therefore contains information about the ABAP instance of the agent’s local system in the following sections:

·        CEN_CONFIG

·        CEN_ADMIN_USER

·        CEN_GATEWAY

·        CEN_CSMREG_USER (as of SAP Web AS 6.10)

The data about the actual central monitoring system is therefore in the sections with the prefix CEN2.

In detail, the various cases in the CSMCONF start file are as follows:

Situation	CSMCONF
No ABAP instance, CEN exists	Prefix CEN: Central monitoring system Prefix CEN2 – CEN5: secondary central systems (optional)
ABAP instance exists, no CEN exists	Prefix CEN: Agent’s local system
ABAP instance exists, CEN exists	Prefix CEN: Agent’s local system Prefix CEN2: Central monitoring system Prefix CEN3 – CEN5: Secondary central systems (optional)

Creating a Customizing Destination

After the registration, you must also create a Customizing destination (see Creating a Customizing Destination for SAPCCMSR -j2ee).

 CCMS Agents start page, Installing and Registering CCMS Agents