• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

Additional configuration

This section provides additional instructions for setting up the system.

Upload authorization role

  1. Use SAP transaction PFCG.

  2. Go to Role > Upload and upload the file _NEWR_DATA_PROVIDER.SAP from the installation package.

  3. Confirm the role /NEWR/DATA_PROVIDER is to be loaded.

    A screenshot displaying the authorization role upload
  4. Click the change icon in SAP icon once loaded.

  5. In the Authorizations tab, select change icon in SAP Change Authorization Data, and activate using activate icon in SAP icon.

    A screenshot displaying the authorization tab and Change Authorization Data in SAP upload
  6. If a profile name is suggested, click the green check icon.

  7. Verify that the message Profile(s) were updated appears on the status bar.

Create New Relic RFC user ID

After activating the authorization profile, use transaction SU01 to create a new RFC user ID (e.g., NR4SAPDP). Set the user type to System or Communication and add the role /NEWR/DATA_PROVIDER.

A screenshot displaying the creation of a new RFC user in SAP

Create RFC destinations for monitored systems

Use transaction SM59 to create an RFC destination for each monitored system.

  1. Select the ABAP Connections and click the Create icon to set up a new RFC destination.

  2. Enter a descriptive RFC Destination name. We recommend to name the RFC destination as NR_<SYSID>CLNT<CLNT#>

  3. Set Connection Type to 3 - ABAP Connection.

  4. On the Technical Settings tab, enter the:

    • Target Host (fully qualified domain or IP) and Instance No.
    • Specify the Gateway Host and Service if necessary.
    A screenshot displaying the how to create RFC destinations for monitored systems
  5. On the Logon & Security tab, enter the RFC user (NR4SAPDP) and password.

  6. Click the Save.

  7. Go to Utility > Test > Connection Test and Authorization Test to confirm a successful connection.

    Importante

    Ensure that the test results are successful.

Set HTTP destination to New Relic cloud

Use transaction SM59 to set up HTTPS connections to the New Relic API endpoints.

Importante

Ensure to create individual RFC destination for Events, Logs, Metrics, and Traces separately.

  1. Enter a Destination Name (e.g., NR_API_EVENT).
  2. Set Connection Type to G (HTTP Connections to External Server).
  3. Enter the Target Host, Service No. as (443) (see standard port for HTTPS), and Path Prefix (see installation readiness checklist for details).
  4. If a proxy is required, configure it on the Technical Settings tab.
  5. On the Security Options tab, check the Active radio button for SSL. A screenshot displaying the connection setup for HTTP destination to New Relic
  6. If needed, download the root certificate from New Relic and add it to SAP using transaction STRUST.
  7. Use Connection Test to verify the connection. A successful connection will prompt to Enter Logon Data. If the test times out, check your firewall settings.
  8. Repeat this procedure for all New Relic API endpoints.

Create BTP/CloudALM authentication endpoint

Follow the instructions below based on the service:

Create database connection

Use transaction DBACOCKPIT to define the remote HANA Database connections.

  1. Double-click Database Connections and click Add.

    A screenshot displaying the Database Connection
  2. Enter a Connection Name (preferably the same as the SAP system ID).

  3. Select HANA Database as the Database System.

  4. Enter the Database user ID (e.g., NRAGENT) and password.

  5. Enter the Database Host and SQL Port.

    A screenshot displaying the SAP Connection Name
  6. Save the data and click Test to verify the connection.

Copyright © 2025 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.