Installing an Agent on a Java Instance (SAP NetWeaver04/7.0 Dual-Stack)

The monitoring data for the J2EE Engine is transferred to central monitoring system (CEN) using the CCMS agent SAPCCMSR. The agent is part of the installation package of the Engine; you only need to register the agent for the relevant Engine with CEN and to start the agent.

This procedure describes the registration of a CCMS agent that is to monitor a J2EE Engine that is part of a dual-stack system of ABAP and java instance.

In the case of a dual-stack system, the agent must be registered with two systems: primarily with the local ABAP system, and secondarily with CEN. Although the agent must run on every instance of the monitored Java system, the distribution is performed automatically through the registration in the Visual Administrator, meaning that you only have to register and start the agent once for each system with CEN.

• There is a CSMREG communications user in CEN and in the local ABAP system.
• You have created the CSMCONF start file for CCMS agents in CEN.

The way in which you can fulfill the prerequisites is described in Installing CCMS Agents for SAP NetWeaver Components.

1. Log on to the host of J2EE Engine of the system as <SID>adm.
2. Copy the CSMCONF start file to the following directory:

   Microsoft Windows:    [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\sapccmsr

   UNIX:                /usr/sap/ccms/<SysID>_<Inst. No.>/sapccmsr

   Note

   You can save the start file to any directory that you can access from your local host. In this case, you need to specify during the registration of the agent where you saved the file. To do this, select the Change …button in the Monitoring service of the Visual Administrator (more information below), and specify the path of the start file. The file is then automatically copied to the above directory.

3. Start the Visual Administrator by calling the start script go (UNIX) or go.bat (Microsoft Windows), and log on with your user as the J2EE Engine administrator.
4. In the navigation bar, choose Cluster → <SysID> → Dispatcher → Services → Monitoring, and choose the CCMS Agent Configuration tab page.
5. If you want to monitor multiple systems with the same system ID, select the Long SID indicator, and enter in this input field an identifier for the system that is unique in your monitored system landscape. This "long system ID" must fulfill the following conditions:
   • The first three characters must be the system ID.
   • The name can be a maximum of eight characters long.
   • The name must not contain an underscore (_).
6. Since you want to register the agent with two systems, you require access data for two users for each of these systems, one of which is an administration user, and the other being the communication user CMSREG.
7. Specify the access data of these users for the local ABAP system by making all entries for the Local Administration User and Local CSMREG User rows. If necessary, you can overwrite the predefined values.
8. Specify the access data of these users for CEN by making all entries for the CENAdministration User and CENCSMREG User rows. If necessary, you can overwrite the predefined values. The CENAdministration User is the user with administration authorizations with which you created the CSMCONF start file.
   Note

   If necessary, you can use the Information button to answer the following questions:

   • Is the instance profile of the instance to be monitored valid?
   • Is the CMSCONF start file to be used valid?
   • What is the version of the CCMS agent SAPCCMSR?
9. Choose the Register button. The registration log is displayed; errors are highlighted in red.
10. Under UNIX, the agent is automatically started by the startsap script when you start the J2EE Engine. Under Microsoft Windows, you need to start the associated service (which was created during the installation of the J2EE Engine) yourself.

    To do this, on the Microsoft Windows host on which the agent is running, choose Start → Settings → Control Panel → Administrative Tools → Services, and choose the service SAPCCMSR.<Instance No.> by double-clicking it. Set the Start Type to Automatic, and choose Start.

All Java instances of the system are now registered with the local ABAP system and with CEN; the corresponding monitoring data of both systems is displayed in the Alert Monitor.

The Customizing destination has also been automatically created for all Java instances, so that you can also change the threshold values for the monitoring data from the Alert Monitor (more information: Creating a Customizing Destination for SAPCCMSR -j2ee).

 CCMS Agents start page