Registering SAP NetWeaver Components and Hosts in CEN 
By default, the Alert Monitor monitors the system in which you start it. However, you can centrally monitor multiple systems with a single Alert Monitor. To do this, you make one system your central monitoring system (CEN).
To centrally monitor remote systems or hosts, you need to register the corresponding component in CEN. This procedure is described here.
There is a CSMREG user in CEN.
There is also a CSMREG user on the ABAP or double-stack system to be monitored.
The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.1.
Note
You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 and hosts without SAP NetWeaver components using CCMS agents.
To monitor an additional system or host, call transaction RZ21.
Choose .
Choose which component type you want to register in CEN.
In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.
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 |
|
If you want to monitor an ABAP system up to release SAP NetWeaver 7, first choose , and in the Tasks to Be Executed group box, select the Create Only RFC Connection to System entry. |
Java |
|
|
TREX |
|
More information about monitoring TREX: Monitoring TREX with CCMS. |
Choose
(Continue (Enter))
If you want to monitor a component as of release SAP NetWeaver 7.1, enter the password for an administrative user at operating system level in the group box Operating System User on the Host of the Monitored System. This is the <SysID>adm user.
Note
You require this authentication since the Web service call for registering a component in CEN is protected.
Save your entries.
Note
If you have registered an ABAP system up to release SAP NetWeaver 7.0 in CEN, you still need to register the SAPCCM4X agent with CEN (more information: Installing an Agent on an ABAP Instance).