Prepare for the installation

Before you start using New Relic Monitoring for your SAP solutions, ensure the following prerequisites are met:

• New Relic Account ID: Obtain your account ID to identify your New Relic account.

• License Key: Secure a New Relic chave de licença needed for authentication and data access.

• Data Center Region: Decide on your preferred data center location (US or EU) and configure your account accordingly.

• SAP System Requirements: Confirm that your SAP systems meet the required software component release levels specified by New Relic Monitoring for SAP Solutions.

• Monitoring BTP Accounts: If BTP accounts are part of your monitoring setup, one of the following should be available:

  • CloudALM Account: A CloudALM account should be configured to monitor your BTP accounts.
  • Process Integration Runtime Service: Ensure a subscription to the Process Integration Runtime service on your monitored BTP accounts, which is required specifically for integration monitoring.

  Importante

  You may need approval or configuration assistance from your security or network teams to meet these prerequisites. Ensure these steps are completed before starting the installation and check out the Checklist for installation readiness to confirm that all environments are correctly set up.

Download software

You can obtain the installation package from your New Relic account executive. The downloaded .zip package contains the following files:

Monitored systems

Our agentless architecture uses RFC connections to retrieve data. To ensure secure connections, you must create an SAP system user with a specific authorization profile for these connections.

• Verify that SAP_BASIS is Release 740 or above, Kernel is Release 753 Patch 602 or above, and ST-PI is Release 740 SP 16 or above.

• Upload the authorization role NEWR_DATA_PROVIDER.

• Create a system user with the uploaded role for RFC connections. Refer to Create New Relic RFC user ID.

• If you're monitoring a HANA database, create a HANA database user NRAGENT with Catalog Read and Monitoring access using the following SQL commands:

  CREATE ROLE NR_AGENT_ROLE;
    GRANT CATALOG READ TO NR_AGENT_ROLE;
    GRANT MONITORING TO NR_AGENT_ROLE;

  Copiar

  CREATE USER NRAGENT PASSWORD 'Xxxxxxxx' NO FORCE_FIRST_PASSWORD_CHANGE;
    GRANT NR_AGENT_ROLE TO NRAGENT;

  Copiar

• Collect the HANA server host and tenant DB port for SQL connection.

• For other databases, activate the standard CCMS database KPIs by running the ABAP program RSDBKPIMON.

Central monitoring system

On the central monitoring system, confirm the following component versions are installed. For versions not listed, contact your New Relic Account Executive for a supplementary package.

• If your SAP version is not listed, contact your New Relic account executive for a supplementary package tailored to your version.
• The central system must have at least 20 dialog work processes and 10 background work processes.
• Ensure outbound HTTPS access to the New Relic data center is allowed.

• Adjust proxy server policies for accessing New Relic if required. Ensure proxy settings are configured:

  • Server domain name/IP address and port.
  • Proxy access credentials, if authentication is necessary.

• Modify firewall policies to allow HTTPS traffic to New Relic if blocked.

  Dica

  These connections can be set in the Central Monitoring System using SAP Transaction SM59 and tested. Refer to the Set HTTP Destination to New Relic Cloud for more details.

• For each monitored system specified, use transaction SM59 and the remote system ID to create RFC Destination and test connections. Refer to the Create RFC destinations for monitored systems for more details.

  Dica

  Ensure the RFC user has the /NEWR/DATA_PROVIDER role assigned.

• Ensure the following for monitoring remote HANA databases:

  • The central monitoring system should have access to the HANA Server and tenant DB port.
  • If your central monitoring system is not an S4HANA system, ensure one of the following components is installed:
    • HANA Client v2.0 (version needs to be compatible with the HANA DB)
    • HANA Client Lib file:
      • libSQLDBCHDB.so (Linux)
      • libSQLDBCHDB.dll (Windows)
      • The library should be located in the SAP Kernel folder and owned by the SID Admin ID (e.g., sd1adm).
  • For each remote HANA database, use transaction SAP DBACOCKPIT to create a DB Connection. Refer to [Create DB connection] for details.

Monitor BTP account

To monitor a BTP account, you need either a CloudALM instance set up to monitor the BTP account, or a subscription to the Process Integration Runtime service (applicable only to integration monitoring). Service keys are required for connection authentication. For more information, see How to retrieve the service keys.

Service keys are also used to create External HTTP destinations and serve as the API host for API data providers.