Registering SAP NetWeaver Components and Hosts in CEN

Use

To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in CEN. There are two ways of doing so:

  • If you are using the SAP NetWeaver Administrator (NWA), we recommend that you configure the monitored components using the Configuration Wizard.

  • If you are using the Alert Monitor, register the desired component in the configuration transaction for the Alert Monitor (transaction RZ21). This procedure is described here.

Prerequisites

  • There is a CSMREG user in CEN.

  • There is also a CSMREG user on the ABAP or double-stack system to be monitored.

  • If you want to register a host with no SAP NetWeaver components in CEN, install the host agent on that host.

  • The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0 EhP2.

Procedure

  1. To monitor an additional system or host, call transaction RZ21.

  2. Choose Start of the navigation pathTechnical Infrastructure Next navigation step Configure Central System Next navigation step Create Remote Monitoring EntryEnd of the navigation path.

  3. Choose which component type you want to register in CEN.

  4. In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.

  5. Depending on the type of component to be monitored, enter the following system and connection data for the component to be monitored:

    Type

    Input Data

    More Information

    ABAP

    Double-Stack

    • System ID

    • Message Server

    • Logon Group; the SPACE, which always exists, is set as the default

    • Password of CSMREG on the monitored system

    The connection to the monitored system is tested with user CSRMREG when you save (or if you choose the Test button in the RFC Connections to Remote Component) group box. The monitored component is only added and the RFC destinations (see below) are only created if the test is performed successfully.

    Java

    • System ID

    • Message Server

    • HTTP port of the message server

    TREX

    • System ID

    • Server

    • Instance number

    You require the user at operating system level to execute a configuration script on the TREX host (see TREX documentation).

    • Host

    • Host Name

    Register only hosts without SAP NetWeaver components here. Ensure that the host agent is installed on the host.

  6. In the Operating System User on the Host of the Monitored System group box, enter the password of an administration user at operating system level. For an SAP NetWeaver component, this is the user <SysID>adm., for a host, it is sapadm.

  7. Save your entries.

Technical Background

  • To monitor an ABAP or dual-stack system centrally, the system creates two RFC destinations in that system:

    • <SysID>_RZ20_COLLECT reads monitoring data for the monitored system; the connection uses the CSMREG user.

    • <SysID>_RZ20_ANALYZE is the destination with which you as an administrator can execute an analysis method in the monitored system. The destination is created without a user, meaning that you need to authenticate yourself in the monitored system.

  • A Customizing destination between the CEN and the relevant Java Engine is required, so that you can change the properties of the monitoring data of the Java Engine (such as threshold values) from the Alert Monitor. This is automatically created under the name SAP.CCMS.J2EE.<SysID> when adding a Java system, where <SysID> is the system ID of the Java system to be monitored.

Result

You can now monitor the corresponding with the Alert Monitor or with the NWA. If you are using rule-based monitors for monitoring, the new system is automatically added to your monitors. Otherwise, add the new system to your monitors or create a new monitor (see Creating and Changing Monitors).

More Information