--- title: Prepare for the installation source: https://docs.newrelic.com/docs/sap-solutions/before-you-begin --- Complete these prerequisites before installation: ## Prerequisites checklist ### New Relic account - **Account ID**: [Obtain your account ID](https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/account-id) - **License Key**: Get a New Relic license key for authentication and data access - **Data Center Region**: [Choose your data center location (US, EU, or Japan)](https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/choose-your-data-center/) and configure your account ### SAP system requirements - **Software versions**: Verify your **SAP systems** meet the required software component release levels. See [Data providers reference](https://docs.newrelic.com/docs/sap-solutions/monitor/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](#network-endpoints)) - **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) > #### ⚠️ IMPORTANT > > You may need approval or configuration assistance from your security or network teams. Complete these steps before installation and review the [installation readiness checklist](https://docs.newrelic.com/docs/sap-solutions/reference/pre-installation-checklist/#checklist-for-installation-readiness). ## Network endpoints [#network-endpoints] You'll need these endpoint URLs when configuring **HTTP destinations** in transaction `SM59`. | Connection | US data center (default) | EU data center | Japan data center | | ----------- | ------------------------------------------------------------ | ---------------------------------------------------------------- | -------------------------------------------------------------- | | **Metrics** | | | | | **Events** | | | | | **Logs** | | | | | **Traces** | | | | > #### 💡 TIP > > Set and test these connections using **SAP transaction** `SM59`. See [Set HTTP destination to New Relic](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#set-http-destination-to-new-relic-cloud). ## 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 - [Upload the authorization role](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#upload-authorization-role) `NEWR_DATA_PROVIDER` - [Create a system user](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#create-rfc-user-id) with the uploaded role for **RFC connections** ### HANA database setup (if applicable) If monitoring a **HANA database**, create a **HANA database user** `NRAGENT` with **Catalog Read** and **Monitoring** access: ```sql CREATE ROLE NR_AGENT_ROLE; GRANT CATALOG READ TO NR_AGENT_ROLE; GRANT MONITORING TO NR_AGENT_ROLE; ``` ```sql 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 > #### ⚠️ IMPORTANT > > 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 [Standard RFC Destination](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#standard-rfc-destination). > #### ⚠️ IMPORTANT > > 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](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#create-database-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](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/obtain-service-key/process-integration-runtime). Use **service keys** to create [external HTTP destinations](https://docs.newrelic.com/docs/sap-solutions/install-and-configure/additional-configuration/#cloud-btp-rfc-destination). The service key `url` value also provides 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.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** |