Start of Content Area

Procedure documentation Registering SAP NetWeaver Components and Hosts in CEN  Locate the document in its SAP Library structure

Use

To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in CEN. You can do this in two ways:

●      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 dual-stack system to be monitored.

●      If you want to register a host without an SAP NetWeaver component in CEN, install the SAP NetWeaver management agents on that host (for more information, see Downloading and Installing the SAPHOSTAGENT Package).

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

Note

You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 EhP1 with CEN using CCMS agents.

Caution

If you want to centrally monitor any system with a central monitoring system with release SAP NetWeaver 7.0, this procedure is not applicable. In this case, follow the procedure described in the newest Monitoring Setup Guide for SAP NetWeaver 7.0 instead. You can obtain the Monitoring Setup Guide at the Internet address service.sap.com/operationsnw70 in the Monitoring area.

Procedure

...

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

       2.      Choose Technical Infrastructure → Configure Central System → Create Remote Monitoring Entry.

       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

Dual-Stack

●      System ID

●      Message server

●      Logon Group; the  SPACE group, 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 This graphic is explained in the accompanying text (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 Installing TREX Monitoring Functions by Script).

●      Host

●      Host name

Register only hosts without SAP NetWeaver components here. Ensure that the SAP NetWeaver management agents are installed on the host (see Downloading and Installing Package SAPHOSTAGENT).

       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.

Note

You require this authentication since the Web service call for registering a component in CEN is protected.

       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).

Note

To deregister a component again, call the topology display (see Technical Topology of the Monitoring Architecture).

This graphic is explained in the accompanying text Infrastructure of the SAP NetWeaver Management Agents Start Page

 

End of Content Area