Adding a Monitored System to the NWA
In this task, you perform the necessary configuration steps to monitor a remote system with the NWA for landscape-wide monitoring and administration. Perform this task in the central system for each monitored logical system.
This procedure is part of the process Wizard-Based Configuration of the NWA. Note the prerequisites specified there.
...
1. You have started the Configuration Wizard in the NWA of the CEN, and have chosen NWA Add Managed System as the scenario.
2. Start the execution of the task by choosing the Start button.
3. Decide whether you want to select the Typical or Custom configuration mode. You should normally choose Typical, which represents a configuration with typical settings.

This section describes both configuration modes; if setting options only exist in Custom mode, this is noted.
Choose Next.
4. On the User data of the central system page, enter the following data:
Input Field |
Meaning |
ABAP administrator |
User name and password of an ABAP administrator in CEN |
Java administrator |
User name and password of a Java administrator in CEN |
Master Password for configuration |
· In Custom mode: Password that is assigned for all newly created users. · In Typical mode: Password that is used as a default value for all newly created users. |
Choose Next.
5. Enter the following data in this step:
¡ In Choose logical system type to be added, you can select whether you want to monitor a Java, ABAP, or double-stack system.
¡ Enter the system ID of the desired system in the System ID input field.
Choose Next.
6. In this step, you can select from all systems with the system ID that you just entered for the desired system. The system searches in the connected SLD for connected systems with the corresponding system ID, and displays a list, in which each entry contains the system ID and the database host in the format <SysID> on <Host>.
Choose Next.
7. In this step, enter an administration user of the monitored system.

Note that you need to perform the task for each client for ABAP systems.
The same administration user is used in the destinations created by the wizard. These destinations are used for connections to the managed system from the central system.
In the case of monitored systems with an ABAP stack, you also require the user CSMREG on this system. Enter the password of this user.
Choose Next.
8. In this step, you enter the required data for availability monitoring with CCMSPING. This is:
Input Field |
Meaning |
CCMSPING RFC destination in central system |
RFC destination of the CCMSPING agent in CEN; by default, this has the naming convention CCMSPING.<Host>.00, where <Host> is the host on which CCMSPING is running. |
System Description |
Short description of the monitored System. |
Message server host |
For monitored ABAP systems, enter the host and port of the ABAP message server here. |
CS Host |
For monitored Java systems, enter the host and port of the Central Services (CS) message server here. |
Router string or CS Router |
Enter the host
and port of the SAProuter in the format |
Choose Next.
9. In this step, you can choose whether to perform the configuration for the following functional units:
¡ Configure Business Intelligence (see next point)
¡ Configure CCMS
Perform the CCMS configuration to add the monitored system to the monitoring infrastructure. Within the NWA, you require this data in the NetWeaver Status Overview and in the Central Reports. Since this configuration is required for central monitoring, ensure that you select this indicator.
¡ In the case of a monitored Java system, Configure GRMG (see Configuring the GRMG for Java-Based Components)
Choose Next.
10. If you have selected the Configure Business Intelligence indicator, and if you are monitoring a system with an ABAP stack, you can enter the user required for this in the step Setting up BI System:
Input Field |
Meaning |
Central system user to run the data loads standard |
The user ALEREMOTE is used in the source system for communication with the BI and for data extraction (see also User Administration). |
Password of the central system user |
|
Local system user to run the data loads standard |
|
Password of the local system user |
Choose Next.
11. In this step, you add the monitored system to the monitoring infrastructure. Depending on the type of the monitored system, enter the displayed connection data for that system.
12. If the NetWeaver management agents from the selected system are not yet registered with CEN, select the Allow Agent Configuration indicator, and enter the following connection data for the agent:
Input Field |
Meaning |
Agent Configuration Details |
Enter the connection data for the CSMREG user in CEN, which you created in Configuring the NWA. Specify the standard client of CEN as the client. |
User data for agent configuration |
Enter an operating system user on the host of the monitored system here. In the case of an SAP NetWeaver component, this is the user <SysID>adm., for a host, it is sapadm. |
Choose Next.
13. You have performed the task. If the task was performed without problems, the list of tasks shows the message root process execution finished successfully in the State column.
14. To check whether the monitored system was correctly assigned to the selected administration landscape, log on to the SLD (http://<host>:<port>/sld), authenticate yourself, and choose Landscapes. For Landscape Type, choose the entry Administration, select the administration landscape, and check on the Systems tab page whether the monitored system is displayed in the list.
15.
For a monitored
ABAP system, check whether the CSMREG user was correctly created. Log on to
the system, start transaction SU01, enter CSMREG in the User input field, and choose
(Display). On the Roles tab page, check whether the user has the role
SAP_BC_CSMREG.
16. For a monitored Java system, check whether the NWADMIN user was correctly created. Log on to the user administration of the system (http://<host>:<port>/useradmin), enter the name NWADMIN in the User field, and choose Go. On the Assigned Roles tab page, check whether the user has been assigned a role with the suffix nwa_superadmin.
17. To check whether monitoring with CCMSPING was correctly set up, log on to the ABAP stack of CEN, start transaction RZ21, and choose Technical Infrastructure → Availability Monitoring → Configure CCMSPING Availability Mon..
18. If you have performed the CCMS configuration, log on to the ABAP stack of CEN, start transaction RZ21, and display the System Overview (Topology group box). The system should be included in the list of monitored remote systems.