(DI-2308) SAP System

1. Created RFC destination with type '3' on the central system where the connection to the remote SAP system is working (the Connection test in transaction SM59 must be successful).

2. It is recommended to create a new RFC user on the remote SAP system through which is done the communication between the central and remote SAP systems

   1. This user should be a system user (no password expiration). If this user is not a system user, there is a risk of password expiration and in the future when the password expires, the monitoring might not be working as expected.

   2. This RFC user should have been assigned an authorization role /DVD/MON_SATELLITE. This authorization role contains all needed authorizations for RFC communication between central and remote SAP systems. You might find more details about authorizations on the page Users and Authorization roles.

   3. This user should be defined in the Logon and Security part for created RFC destination in step 1.

Add a new SAP System

1. Select the main system type SAP system.

   Open

   

2. Following screen appears for System information.

   Open

   

3. Enter Destination (destination with connection type '3' (ABAP Connections) needs to be entered. You might press Maintain RFC to create a new ABAP Connection).

   1. To monitor the central system itself, enter destination “NONE“.

   2. To monitor remote system(s), enter a valid RFC destination configured for this remote system (please note that this RFC Destination should already have set a user name and password in the Logon & Security tab as described in the section above (DI-2308) SAP System).

4. When the destination is entered, press Check RFC.

   1. If any error occurred, the RFC Destination is not configured correctly. You might check and maintain the RFC Destination by clicking the button Maintain RFC or by calling transaction SM59.

5. (Optional) You might change the Maximum time for RFC PING in the seconds to set the maximum time for RFC PING.

   1. When the system does not respond after the maximum time set here, then a red light icon in the monitoring pool is displayed (not accessible).

   2. Recommended value for RFC PING is at least 10 seconds (also for fast connections).

6. The additional information about the system is automatically pre-filled.

7. (Optional) You might change the System description

8. (Optional) You might change the System name

9. Confirm setup

10. The following screen appears with the auto-detected application and database server(s) for the monitored system. Make sure that the Monitor flag is selected and press Confirm.

    1. There is automatically detected the IP Address for all application servers, which is used as a full network address of this server. This address might be adjusted in System settings.

    2. If any application servers in the Passive state exist, there are also detected in the list of servers, but those servers are not monitored by default (more details can be found in (DI-2308) Monitoring Tabs).

11. SAP System was added. You can start the monitoring by clicking the button Start default monitoring in the menu bar.

Additional monitoring for the SAP system

When the SAP system is added successfully, you might consider also starting some additional collector jobs for further monitoring outside of the default monitoring scope (other than DEF* profiles).

• Profiles starting with BW* - for Business Warehouse SAP systems

• Profiles starting with HDB* - for SAP HANA-based SAP Systems

• Profiles starting with ORA* - for SAP Oracle-based SAP Systems

• Profiles starting with FS* - Monitoring of specific Housekeeping statistics

• Profile IDOC_1HOUR - IDoc Monitoring

• Profile GRC_1DAY - Governance, Risk, and Compliance checks

You might find some additional details about scheduling new collector jobs for the above-mentioned monitoring profiles in the chapter Create and schedule a Collector job.