Configuring NWA for Landscape-wide Monitoring
and Administration
...
1. The user must have the SAP_J2EE_ADMIN and SAP_XI_RWB_SERV_USER roles assigned to execute the templates.
2. You need to activate the service nodes by performing the following:
a. Run the transaction SICF and choose Execute.
b. Navigate to the following service nodes and activate:
§ /default_host /sap/bc/srt
§ /default_host /sap/public/icman
§ /default_host/sap/bc/webdynpro
§ /default_host/sap/public/bc/ur
§ /default_host/sap/public/bc/icons
§ /default_host/sap/public/bc/icons_rtl
§ /default_host/sap/public/bc/webicons
§ /default_host/sap/public/bc/pictograms
§ /default_host/sap/public/bc/webdynpro/
§ /default_host /sap/public/myssocntl
§ /default_host/sap/bc/webdynpro
3. You need to choose activate and then execute the report program RSXMB_AGG_XPI_ADMIN using the transaction SE38. For more information, refer the SAP Note: 1031773.
4. You need to configure the ABAP systems (central or managed) to create and accept SSO Certificates by setting the profile parameters as follows:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
The profile parameters are stored in a file on the server and its path is: <SystemDrive>:\usr\sap\<SID>\SYS\profile
5. Install the CCMSPING agent on the CENsystem by performing the following steps:
a. The CSMREG user has to be created manually before the CCMSPING registration. If the CSMREG user does not exist, the Configure NWA wizard displays a warning message.
To check if CSMREG user exists, perform the following steps:
i. Log on to the ABAP stack of the central system and execute the transaction su01.
ii. Search for the user CSMREG.
■ If the user exist, check whehter the role SAP_BC_CSMREG is assigned to the user.
■ If the user does not exist, create the user CSMREG with the type as Communication and assign the role SAP_BC_CSMREG.
b.
You need to install
the CCMSPING agent using the -push option. More information:
Installing
Availability Agent CCMSPING

For further information related to pre-requisites see SAP Notes 1160261 and 1124553.
...
1. Start the Configuration Wizard in the central SAP NetWeaver Administrator, and choose Configure NWA as the task.
2. Choose Start or Re-Execute.
3. Select either the Typical or Custom configuration mode and choose Next.

Typical configuration automatically applies the default values and enables the functional units for the usage types you handle.
Custom configuration allows you to choose the value for each parameter for the Adaptive Computing Controller functional unit, including the configurations performed in the typical mode.
4. Enter credentials for both the ABAP and the Java Stacks of the Central System.
Choose Next.
Input Field |
Meaning |
ABAP administrator |
User name and password of an ABAP administrator in CEN for default client
|
Java administrator |
User name and password of a Java administrator in CEN |
Master Password for configuration |
Password used for NWADMIN user |
5. In this step, you define the administration landscape that is monitored by this CEN system. You have the following options:
¡ You can use the current landscape, shown under Current Administration Landscape name (radio button Continue with Current Administration Landscape)
¡ You can use another existing landscape (radio button Choose from existing Administration Landscapes)
In this case, you should select the desired landscape from the existing landscapes in the next step only.
¡ 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 select the functional unit Process Integration (PI) for setting up the PI monitoring. In addition you can also choose the following functional units as required:
¡ Adaptive Controlling Controller
More information: Configuring the Adaptive Controlling Infrastructure
¡ DB Admin Cockpit
Here you can select one of the remote databases to do DBACockpit monitoring in
the Central ABAP stack. For example, setting up an Oracle database.
On entering the correct remote database data and clicking next DBACockpit setup
is performed.
More information: 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
In GRMG screen available scenario for GRMG are displayed in a drop down box.
To check if the components running on CEN are available, select one option and
choose Next.
More information: Configuring the GRMG for Java-Based Components
○ NetWeaver Status Overview
Choose the checkbox Netweaver Status Overview (NWSO) to setup NWSO monitoring on the central system.
¡ Enable additionally central IT Reporting
Choose the check box “Enable additionally central IT Reporting” to setup the technical BI reporting on the Central NWA system
7. If you have selected NWSO, PI, or Enable additionally centrally IT reporting in the above step, CCMS configuration steps would follow:
a. Choose the appropriate CCMS agent information from the dropdown box.
b. In this step, you select 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 |
8. Choose Next.