Adding a Monitored System to the NetWeaver Administrator  

Use

You use this procedure to perform the necessary configuration steps to monitor a remote system by the central SAP NetWeaver Administrator that is configured on a double stack system. The remote system can be a Java system, ABAP system, or a double stack system.

If you are adding a double stack system as a managed system, then you need to perform this procedure once for the Java System, and then repeatedly for every ABAP client of the ABAP system.

If the managed system is a double stack having multiple ABAP clients, using this template, the Java stack, and all the clients of the ABAP stack are configured as managed system in the NetWeaver Administrator at a time.

Prerequisites

...

       1.      The user must have the SAP_J2EE_ADMIN and SAP_XI_RWB_SERV_USER roles assigned to execute the template.

       2.      You have ensured that the managed system is added to the central System Landscape Directory as a technical system.

       3.      If you are adding an ABAP system or a double stack system as the managed system, then you have ensured that the ABAP user on the central SAP NetWeaver Administrator has the composite role SAP_NWA_FULL.

 

If the central system is NetWeaver 7.1 SP1 or SP2, you need to assign the role RBAM_ALL to the ABAP administrator user. Additionally, transaction RZ30 must be added to the role SAP_NWA_FULL by performing the following activities:

                                                  i.       Execute the transaction PFCG.

                                                ii.       The role SAP_BC_BASIS_ADMIN is a part of the collective role SAP_NWA_FULL. Hence, enter SAP_BC_BASIS_ADMIN in the Role Field.

                                               iii.       Choose Change.

                                               iv.       On the Authorizations tab page, choose Change Authorization Data.

                                                 v.       Select Cross-application Authorization Objects, and choose Expand.

                                               vi.       In the entry Authorization check for transaction start, choose Change.

                                              vii.       For S_TCODE in the field Authorization check for transaction start, enter the transaction RZ30.

                                            viii.       Choose Generate.

        In addition, the administration user for the managed system requires the  J2EE_ADMIN_ALL role.

       4.      If you are adding a Java system as a managed system, and this Java system is used for PI monitoring and is required to access the payloads in Message Monitoring, then ensure that the Java user of the managed system has the role SAP_XI_ADMINISTRATOR_J2EE.

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

Procedure

...

       1.      Log on to the central SAP NetWeaver Administrator using the URL http://<host>:<port>/nwa, as an administrator.

<Host> and <Port> are the values of the AS Java of the central system (CEN) on which you have configured the SAP NetWeaver Administrator.

       2.      Choose Configuration Management  → Scenario Configuration, and choose Configuration Wizard.

       3.      Select the NWA Add Managed System configuration wizard, as the scenario.

If you are adding a double stack system, you need to execute this wizard once for the Java system, and then once for each client of the ABAP system that is to be monitored.

The wizard should be executed from the beginning every time.

       4.      Choose Start or Re-execute.

       5.      Decide whether you want to select the Typical or Custom configuration mode. You should normally choose Typical, which represents a configuration with typical settings.

          Choose Next.

       6.      On the User data of the central system page, enter the following data:

Input Field	Meaning
ABAP administrator Administrator user name Administrator password	User name and password of an ABAP administrator in CEN. While adding ABAP systems, the ABAP User should have the roles SAP_NWA_FULL and RBAM_ALL assigned.
Setting for a J2EE Administrator User Administrator password	Password of a Java administrator in CEN.

The user and password entries on this screen are for the central SAP NetWeaver Administrator system, and not for the managed system.

The ABAP administrator field defaults to DDIC. However, a different user having DDIC authorization is advisable.

Choose Next.

       7.      Enter the system ID of the system you want to add, in the SID input field.

         Choose Next.

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

You can also search the system that you want to add in the landscape, by entering * in the SID field.

In the Select a system to add to the Administration Landscape section, perform the following activities:

                            a.      Select the system you want to add as the managed system.

If the system is double stack, you need to execute the wizard once for the Java system, and then for every client of the ABAP system.

                            b.      (Optional) Select the Perform only SLD related configuration checkbox, to add the system to the default System Landscape Directory (SLD) and to avoid the monitoring configurations on the system.

We recommend that you do not select the checkbox Perform only SLD related configuration. If you select this checkbox, the managed system will not be configured for monitoring.

Choose Next.

       9.      In this step, enter an administration user of the monitored system.

¡        If the selected managed system is Java, you need to enter the Java user credentials.

If the Java system you are adding is used for PI monitoring and is required to access the payloads in Message Monitoring, then ensure that the Java user of the managed system has the role SAP_XI_ADMINISTRATOR_J2EE.

If the selected managed system is ABAP, you need to execute this wizard for each client of the ABAP system.

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.

   Choose Next

   10.      In this step, you select the functional unit Process Integration (PI). In addition you can also choose the other functional units as required.

Choose Next.

   11.      If you have selected either NWSO or PI, or both, the CCMS configuration steps would follow.

                            a.      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
System Description	Short description of the monitored System.
Message server host Message server port	For monitored ABAP, the host and port of the ABAP server is displayed.

You can verify the information from the SLD. The host is the central service instance host, and the port is the msgHttpPort in the SLD.

Choose Next

                            b.      Enter the system details of the managed system and agent configuration details of the managed system as shown below:

For Double Stack System:

A system is treated as Double Stack if the selected system has entry of both Java and ABAP stack maintained in SLD. For a double stack configuration of CCMS , make sure that the check box Add as Double Stack system to CCMS is checked.

Select a valid logon group for the managed system (transaction SMLG).

Choose Next.

   12.      If you have selected the Business Intelligence option, perform the following activities:

                            a.      Enter the BWREMOTE password of the central system.

                            b.      Enter the ALEREMOTE password of the managed system.

                            c.      If the selected managed system is Java, you need to enter the Java user credentials.

If the Java system you are adding is used for PI monitoring and is required to access the payloads in Message Monitoring, ensure that the Java user of the managed system has the role SAP_XI_ADMINISTRATOR_J2EE.

Choose Next

   13.      If you have selected the GRMG option, select one or more of the scenarios for GRMG that is displayed in the dropdown box

...

   14.      Choose Next.

Result

You have performed the task. After 5 minutes of completing this task, you can see the PI Overview displaying the status details on the integration engine( if the integration engine is the default client of the ABAP system).

...

Trouble Shooting Tips

S.No	Problem	Tips/Notes	Valid Release
1	Agents not getting created for the managed systems	Note 1113090	SP3, SP4
2	The system tries to perform superfluous inserts and this increases the runtime unnecessarily. In addition, necessary inserts may not occur. When you execute a consumer proxy, the system displays the error message: "Object CLASS_NAME ... is not a proxy object". This happens when you try to manually create the agent.	Note 1105141	710 and above
3	Agents are always shut down on RZ21	Note 1130394	710 – 711
4	Admin user changes password	Change password directly in destinations. More information: Manually Maintaining NWA Configuration
5	CCMS agent registration failure	Note: 1131569