Configuring NWA for Landscape-wide Monitoring
and Administration
In this task, you perform the configuration steps to set up the NWA for landscape-wide monitoring and administration on a double-stack system. The necessary steps to configure central monitoring are performed as part of this.
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 Configure NWA as the task.
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 default 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. In this step, you define the administration landscape for which this system is to act as the central system. You have the following options:
¡ You can use the current landscape, shown under Current Administration Landscape name (radio button Select current Administration Landscape).
¡ You can use another existing landscape (radio button Choose from existing Administration Landscapes); in this case, you can select the desired landscape from the existing landscapes in the next step.
¡ You can create a new landscape (radio button Create a new Administration Landscape); in this case, you need to enter the desired name in this step.
Choose Next.
6. In this step, you create two users in CEN, for which you need to define the passwords:
¡
The
CSMREG communication
user; a communication user with greatly restricted rights, for example,
for data collection in the monitored systems and data push from monitored
systems.
¡ The administration user NWADMIN, which has all necessary authorizations to use the NWA for lansdcape-wide monitoring and administration.
Choose Next.
7. In this step, you can optionally perform the configuration for the following functional units:
¡ Adaptive Controlling Controller (see Configuring the Adaptive Controlling Infrastructure)
¡ DB Admin Cockpit(see Configuring the DB Admin Cockpit)
¡ Embedded Support Setup
No additional manual entries are required here; the required RFC destinations between the ABAP and Java stacks of CEN are created.
¡ GRMG Setup (see Configuring the GRMG for Java-Based Components)
Choose Next.
8. 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.
9. To check whether the administration landscape was correctly created, log on to the SLD (http://<host>:<port>/sld), authenticate yourself, and choose Landscapes. For Landscape Type, choose Administration and check whether the administration landscape that you created in the task is displayed.
10.
To check whether
the CSMREG user was correctly created, log on tot he ABAP stack of CEN, 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.
11. To check whether the NWADMIN user was created correctly, log on to the user administration of the central 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.
12. To check whether the configuration for Embedded Support was performed: in the NWA, choose Configuration Management → Security Management → Destinations, and ensure that the EMBEDDED_SUPPORT destination exists. In the NWA, also choose Configuration Management → Infrastructure Management → JCo RFC Destinations, and ensure that the destination SAP_SPR_J2EE exists.