Additional configuration

Complete these configuration tasks for each monitored system.

Upload authorization role

Use SAP transaction PFCG.
Go to Role > Upload and upload the file _NEWR_DATA_PROVIDER.SAP from the installation package.
Confirm that the role /NEWR/DATA_PROVIDER loads.
Select the icon after the role loads.
On the Authorizations tab, select Change Authorization Data, and then activate it using the icon.
If a profile name is suggested, select the green check icon.
Verify that Profile(s) were updated appears on the status bar.

Create New Relic RFC user ID

After you activate the authorization profile, use transaction SU01 to create a new RFC user ID (for example, 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.

Select ABAP Connections and then select the Create icon to set up a new RFC destination.
Enter a descriptive RFC Destination name. We recommend: NR_<SYSID>CLNT<CLNT#>
Set Connection Type to 3 - ABAP Connection.
On the Technical Settings tab, enter:
- Target Host (fully qualified domain or IP) and Instance No.
- Gateway Host and Service if necessary.
On the Logon & Security tab, enter the RFC user (NR4SAPDP) and password.
Select Save.
Go to Utility > Test > Connection Test and Authorization Test.
- Expected result: Both tests show successful status.

Set HTTP destination to New Relic cloud

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

Important

Create individual RFC destinations for Events, Logs, Metrics, and Traces separately.

Enter a Destination Name (for example, NR_API_EVENT).
Set Connection Type to G (HTTP Connections to External Server).
Enter Target Host, Service No. as 443 (see standard port for HTTPS), and Path Prefix (see installation readiness checklist for details).
If you need a proxy, configure it on the Technical Settings tab.
On the Security Options tab, select the Active option for SSL.
If needed, download the root certificate from New Relic and add it to SAP using transaction STRUST.
Select Connection Test to verify the connection.
- Expected result: A successful connection prompts you to enter logon data.
- If test times out: Check your firewall settings.
Repeat this procedure for all New Relic API endpoints.

Create BTP/CloudALM authentication endpoint

Follow the instructions below based on the service:

Note the clientId, clientsecret, and tokenurl from the downloaded Service Key.
Go to tokenurl in a web browser and download the necessary certificates (Digicert root, global, and SAP on demand).
Use transaction STRUST to upload the three certificates one by one, then select Add to Certificate List.
Select Save.
Use transaction SMICM and go to Administration > ICM > Exit Soft > Global to restart all ICM processes.
Use transaction SM59 to create a new RFC connection under HTTP Connections to External Server.
Split the tokenurl into the host and path prefix, then append the path prefix with ?grant_type=client_credentials.
Set Service No. to 443.
On the Login & Security tab, select Basic Authentication and enter clientId and clientsecret as the username and password.
Set Secure Protocol status to Active and save the configuration.
Select Connection Test.

Note the clientId, clientsecret, and url from the downloaded Service Key.
Go to the url in a web browser and download the Digicert root, global, and SAP on demand certificates.
Use transaction STRUST to upload the three certificates one by one, then select Add to Certificate List.
Select Save.
Use transaction SMICM and go to Administration > ICM > Exit Soft > Global to restart all ICM processes.
Use transaction SM59 to create a new RFC connection.
Enter the url as Target host and set Service No. to 443. Set Path Prefix to /oauth/token?grant_type=client_credentials.
On the Login & Security tab, select Basic Authentication and enter clientId and clientsecret as the username and password.
Set Secure Protocol status to Active and save the configuration.
Select Connection Test.

Create database connection

Use transaction DBACOCKPIT to define the remote HANA Database connections.

Double-click Database Connections and select Add.
Enter a Connection Name (preferably the same as the SAP system ID).
Select HANA Database as the Database System.
Enter Database user ID (for example, NRAGENT) and password.
Enter Database Host and SQL Port.
Select Save, and then select Test to verify the connection.
- Expected result: Connection test shows successful status.