SAP System

To add a new SAP system in the central monitoring system, see the chapter Adding a New SAP System.

NOTE For more information about the central monitoring system, see the chapter Installing CrystalBridge® Monitoring.

Prerequisites for Remote SAP System Monitoring

If you want to monitor any remote SAP system, the following prerequisites must be fulfilled:

  1. Create an RFC destination of type 3 on the central system where the connection to the remote SAP system is required. Here, the connection test in transaction SM59 must be successful.

  2. We recommend creating a new RFC user on the remote SAP system to handle the communication between the central and remote SAP systems:

    1. This user must be a system user with no password expiration. If this user is not a system user, there is a risk of password expiration. If the password expires, the monitoring might not work as expected.

    2. This user must be assigned the authorization role /DVD/MON_SATELLITE. This authorization role contains all the required authorizations for RFC communication between central and remote SAP systems. For more information about authorizations on the page Users and Authorization Roles.

    3. This user must be defined in the Logon & Security tab for the created RFC destination in step 1.

Adding a New SAP System

Proceed as follows to add a new SAP system:

  1. Start transaction /DVD/MON.

  2. In the main toolbar, click Add system (Shift+F1).

  3. Select the main system type SAP system.

  4. Click Confirm.

  • The screen SAP system for monitoring appears.

  1. In the Destination field, enter an RFC destination with the connection type 3 (ABAP connections). You can also click Maintain RFC to create a new ABAP connection.

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

    2. To monitor remote system(s), enter a valid RFC destination that has been configured for this remote system. Note that this RFC destination must already have a defined username and password in the Logon & Security tab as described in the chapter Prerequisites for Remote SAP System Monitoring.
  2. Once you have entered an RFC destination, click Check RFC.

  3. Optional: You can change the option Maximum time for RFC PING in seconds in order to set the maximum time for the RFC ping. The recommended value for the RFC ping is at least 10 seconds (also for fast connections).

    If the system does not respond after the maximum time set here, a red light icon is displayed in the list of monitored systems. This icon indicates that the system is not accessible.

    The additional information about the system is automatically prefilled.

  4. Optional: Change the System description.

  5. Optional: Change the System name.

  6. Click Confirm.

    A screen appears with the auto-detected application and database server(s) for the monitored system.

NOTE

If you add a new SAP system with the Oracle database as its primary database, after confirming the setup, the report Generating KPIs Specifically for Oracle Database Monitoring is automatically executed. Furthermore, additional KPIs for Oracle system metrics are automatically generated before determining the list of all available servers.

If any unexpected error occurs while executing the report to generate Oracle system metrics, the error text is displayed in the spool output of the executed report. In this case, the additional KPIs for Oracle system metrics monitoring are not generated as expected and are not available for the monitoring. You can generate these KPIs manually later as described in the chapter Generating KPIs Specifically for Oracle Database Monitoring.

  1. Ensure that the Monitor flag is selected.

  2. Click Confirm.

    The system automatically detects the IP address for all application servers, which is used as the full network address of this server. If necessary, you can adjust this address in the system settings.

    If any application servers exist in a passive state, they are also detected in the list of servers. However, these servers are not monitored by default.

  • The SAP system has been added.

  • You can start the monitoring by clicking Start default monitoring in the menu bar.

NOTE If the added SAP system has a HANA or Oracle database set as its standard database, the additional collector jobs are automatically scheduled when default monitoring is started. This concerns collector jobs with HDB* profiles for a HANA database and ORA* profiles for an Oracle database. If all KPIs from these additional DB-specific profiles are already being monitored by any default profile, the specific job is not scheduled because all its KPIs are already being monitored.

Additional Monitoring for SAP Systems

Once you have added an SAP system successfully, you might want to start 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

For more information about scheduling new collector jobs for the above-mentioned monitoring profiles, see the chapter Creating and Scheduling Collector Jobs.

Adding a Hadoop System to the Monitoring

Setting up a Hadoop Connection to an SAP System

Proceed as follows to set up a Hadoop connection:

  1. Start transaction RZ21 on the system from which the Hadoop external servers will be monitored.

In the Topology area, click Display Overview.

  1. Click Create Entry.

  2. In the drop-down menu Instance type to be monitored, select Host.

  3. In the Host Name field, enter a host name for the installed SAP host agent.

  4. In the Password field, enter the correct password for monitored host. This is the same password as the one you specified during the installation of your SAP host agent on your non-SAP system.

  5. Click Save.

  • The Hadoop connection has been set up.

NOTE You can find detailed information about how to install and set up the SAP host agent on a remote server on the official SAP website.
Setting up Hadoop Monitoring in CrystalBridge® Monitoring

Proceed as follows to set up Hadoop monitoring:

  1. Start transaction /DVD/MON.

  2. Click Add system.

  3. Select the system type SAP system.

  4. Set up the SAP system for monitoring:

    1. In the Destination field, enter NONE.

    2. Click Check RFC. The values are automatically filled out.

    3. In the System description field, enter Hadoop.

    4. In the System name field, enter HADOOP.

    5. Click the Monitoring areas field, press F4, clear all the options and select only Operating system.

    6. Click the External server types for monitoring field and press F4.

    7. Select the server types WSSAPOSCOL and RFSAPOSCOL. These are the server types that are relevant for SAPOSCOL.

  1. Click Confirm.

  2. In the Monitor column, select the servers that you want to monitor.

  3. Click Confirm.

  • The Hadoop monitoring has been set up.

Monitoring

Proceed as follows to set up the monitoring:

  1. Start transaction /DVD/MON.

  2. In the menu bar, click Settings > System settings.

  3. Select the row of the system under which you created the server connection.

  4. Under Dialog Structure, double click Server maintenance > Server list.

  5. In the Don’t monitor column, deselect the option for the server that you want to monitor.

  6. Click Save.

  • CrystalBridge® Monitoring will now monitor the server as well as collect the KPIs at the operating system level.