• /
  • EnglishEspañolFrançais日本語한국어Português
  • EntrarComeçar agora

Prepare for the installation

Complete these prerequisites before installation:

Prerequisites checklist

New Relic account

  • Account ID: Obtain your account ID
  • License Key: Get a New Relic for authentication and data access
  • Data Center Region: Choose your data center location (US or EU) and configure your account

SAP system requirements

  • Software versions: Verify your SAP systems meet the required software component release levels. See Data providers reference for system-specific requirements
  • Monitored systems: SAP_BASIS 740+, Kernel 753 Patch 602+, ST-PI 740 SP16+
  • Central monitoring system: SAP_BASIS 740+, ST-PI 740 SP14+

Network access

  • HTTPS access to New Relic endpoints (see endpoint URLs)
  • Firewall rules configured
  • Proxy settings configured (if required)

BTP monitoring (if applicable)

If monitoring BTP accounts, ensure one of the following:

  • CloudALM account configured for BTP monitoring
  • Process Integration Runtime service subscription (required for integration monitoring)

Importante

You may need approval or configuration assistance from your security or network teams. Complete these steps before installation and review the installation readiness checklist.

Network endpoints

You'll need these endpoint URLs when configuring HTTP destinations in transaction SM59.

Connection

US data center

EU data center

Metrics

https://metric-api.newrelic.com/metric/v1

https://metric-api.eu.newrelic.com/metric/v1

Events

https://insights-collector.newrelic.com/v1/accounts/events

https://insights-collector.eu01.nr-data.net/accounts/event/v1

Logs

https://log-api.newrelic.com/log/v1

https://log-api.eu.newrelic.com/log/v1

Traces

https://trace-api.newrelic.com/trace/v1

https://trace-api.eu.newrelic.com/trace/v1

Dica

Set and test these connections using SAP transaction SM59. See Set HTTP destination to New Relic.

Prepare monitored systems

The agentless architecture uses RFC connections to retrieve data.

Version requirements

Verify the required software versions:

  • SAP_BASIS: Release 740 or above
  • Kernel: Release 753 Patch 602 or above
  • ST-PI: Release 740 SP16 or above

User configuration

HANA database setup (if applicable)

If monitoring a HANA database, create a HANA database user NRAGENT with Catalog Read and Monitoring access:

CREATE ROLE NR_AGENT_ROLE;
GRANT CATALOG READ TO NR_AGENT_ROLE;
GRANT MONITORING TO NR_AGENT_ROLE;
CREATE USER NRAGENT PASSWORD 'Xxxxxxxx' NO FORCE_FIRST_PASSWORD_CHANGE;
GRANT NR_AGENT_ROLE TO NRAGENT;

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

Other databases

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

Prepare central monitoring system

Importante

Verify your central monitoring system has SAP_BASIS 740+ and ST-PI 740 SP14+.

Verify version compatibility

SAP_BASIS Version

SAP_ABA Version

ST-PI Version

740

n/a

740 SP14+

750

750

740 SP14+

750

75A

740 SP14+

751

75B

740 SP14+

752

75C

740 SP14+

753

75D

740 SP14+

754

75E

740 SP14+

755

75F

740 SP14+

756

75G

740 SP14+

757

75H

740 SP14+

758

75I

740 SP14+

If your version is not listed, contact your New Relic account executive for a supplementary package.

System requirements

  • At least 20 dialog work processes and 10 background work processes
  • Outbound HTTPS access to the New Relic data center (see endpoint URLs above)

Network configuration

  • Proxy settings (if required):

    • Server domain name/IP address and port
    • Proxy access credentials (if authentication is necessary)
  • Firewall policies: Allow HTTPS traffic to New Relic endpoints

RFC destinations

For each monitored system, use transaction SM59 and the remote system ID to create RFC destinations and test connections. See Create RFC destinations for monitored systems.

Importante

The RFC user must have the /NEWR/DATA_PROVIDER role assigned.

Remote HANA database monitoring (if applicable)

To monitor remote HANA databases:

  • Ensure the central monitoring system has access to the HANA server and tenant DB port
  • For non-S4HANA central monitoring systems, install one of these components:
    • HANA Client v2.0 (compatible with the HANA DB version)
    • HANA Client Lib file:
      • libSQLDBCHDB.so (Linux)
      • libSQLDBCHDB.dll (Windows)
      • Locate the library in the SAP Kernel folder and assign ownership to the SID Admin ID (e.g., sd1adm)
  • For each remote HANA database, use transaction SAP DBACOCKPIT to create a DB connection. See Create DB connection

Prepare BTP monitoring (if applicable)

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. See How to retrieve service keys.

Use service keys to create external HTTP destinations and as the API host for API data providers.

Download installation package

Download the installation package (provided by your New Relic account executive).

File inventory

File Title

File Name

Remarks

Packing List

NRM4SAP<version>.txt

File inventory list

ABAP Add-on

K-xxxAOIINNEWR.SAR

Archive file for SAP Add-on

ABAP Add-on Upgrade Pkg

K-xxxAOUINNEWR.SAP

Archive file for SAP Add-on Upgrade

Authorization Roles

_NEWR_DATA_PROVIDER.SAP

Authorization Role for NR RFC users

Copyright © 2026 New Relic Inc.

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