diff --git a/src/content/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package.mdx b/src/content/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package.mdx new file mode 100644 index 00000000000..df8ee260726 --- /dev/null +++ b/src/content/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package.mdx @@ -0,0 +1,661 @@ +--- +title: "Connect systems and generate data provider configurations" +metaDescription: "Configure New Relic ABAP add-on package." +freshnessValidatedDate: never +--- + +## Menu /NEWR/INSTALL [#menu-newr-install] + +After successfully installing the add-on on the central monitoring system, + + - Ensure the installer has the proper authorization to perform the configuration. + - The new transaction code introduced by the add-on package is listed in **Transaction Code for NRM4SAP installation and configuration**. + - We recommend the installer adds the parameter `/NEWR/*` to the code authorization object(s) in their profile/role. + + If this is your first time installing the New Relic ABAP Add-on, complete all the steps described below. If you are upgrading from a previous version, refer to the **[Upgrade from Previous Version]** section to determine which steps are necessary. + + + 1. Login to the production client of the central monitoring system. + 2. Begin the data provider setup by starting the area **menu /NEWR/INSTALL**. + 3. Navigate to **SAP Easy Access root menu** before starting the area menu by typing `/n/NEWR/INSTALL` in the command field. + + + If you are unsure whether you are at the **SAP Easy Access root menu**, type in `/n` and press **Enter**. + + +## Install New Release and Patch [#new-release-and-patch] + + + Follow the steps to complete the configuration if not yet completed before installation + + + + + + ## Setup HTTP and RFC Destinations + - This option invokes SAP transaction SM59. Use SM59 command to set up RFC destination for each monitored system. + - It verifies that the RFC connections to Monitored Systems and HTTP connections to New Relic Endpoints are set up correctly. + - See [Create RFC destinations for monitored systems](/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package/#create-rfc-destinations-for-monitored-systems) and [Set HTTP Destination to New Relic Cloud](/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package/#http-destination-to-new-relic-cloud) + + + + 1. Select the **ABAP Connections** and click the **Create** icon to set up a new RFC destination. + 2. Enter the following RFC destination information: + - **RFC Destination**: Enter the destination name. We recommend to name the RFC destination as `NR_CLNT`. For example, `NR_SAPSYSCLNT100`. + - **Connection Type**: Select **3** (ABAP Connection). + - **Description**: Provide a brief description of the RFC destination. + 3. Click the **Technical Settings** tab and enter the below options: + - **Target Host**: Enter the fully qualified domain name (FQDN) or IP address of the monitored system. + - **Instance No.**: Enter the instance number of the monitored system. + - **Save as**: Choose either Host or IP based on your entry for the **Target Host**. + - **Gateway Host and Service**: Specify the **Gateway Host** and **Service** if necessary. + A screenshot displaying the how to create RFC destinations for monitored systems + 4. Click on the **Logon & Security** tab. + - **User**: Enter the user created for this ABAP connection, which is NR4SAPDP. + - **Password**: Enter the password for the NR4SAPDP user. + 5. Once enterng all the required information, click the **Save** icon. + 6. Test the connection and authorization to ensure that the RFC destination is functioning correctly: + - **Connection Test**: Select **Utility > Test > Connection Test** or click **Connection Test**. + - **Authorization Test**: Select **Utility > Test > Authorization Test**. + + Ensure that the test results are successful. + + + + + + Step-by-step guide on how to set up HTTP destinations to New Relic cloud using the SAP transaction `SM59`: + + 1. In the SAP GUI, enter the transaction code `SM59` and press **Enter**. + 2. Select **HTTP Connections to External Server** option and click the **Create** option to set up a new HTTP connection. + + Ensure to create individual RFC destination for Events, Logs, Metrics, and Traces separately. + + 3. Enter the following connection details: + - **RFC Destination:** Enter a name for the endpoint, e.g., `NR_API_EVENT`,`NR_API_LOGS`,`NR_API_METRICS`,`NR_API_TRACES`. + - **Connection Type:** Select `G` (HTTP Connections to External Server). + - **Target Host:** Enter the endpoint host, e.g., `insights-collector.newrelic.com`. + - **Service No.:** Enter `443` (see [standard port](#standard-ports) for HTTPS). + - **Path Prefix:** Enter the URL path after the domain, e.g., `/v1/accounts/events`. + 4. If a proxy server is required to connect to the external URL, navigate to the **Technical Settings** tab and enter the following: + - **Proxy Host:** Enter the proxy server's hostname or IP address. + - **Service:** Enter the proxy service port. + - **User:** Enter the proxy user if authentication is needed. + - **Password:** Enter the proxy password if required. + 5. Check the **Active** radio button for **Security Options** to enable **SSL** for secure communication. + A screenshot displaying the connection setup for HTTP destination to New Relic + 6. **SSL Certificate Setup (if needed)** + - If the SSL certificate is not set up yet, download the root certificate from [New Relic](https://one.newrelic.com). + - Add the certificate to the SAP system using transaction `STRUST`. + 7. Use the **Connection Test** feature to test the connection. If a connection is made, you should see a prompt to **Enter Logon Data**. + 8. Click **Cancel**, an HTTP response code **4xx** is displayed. This indicates that the connection is successful, even though the response code is an error (expected due to lack of authentication). + 9. If the connection test times out, it is likely that the connection is blocked by a firewall. Check with your network team to ensure that access to New Relic domains is open. + + + + ### US Region + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ **RFC Destination** + + **Conn. Type** + + **Target Host** + + **Service No.** + + **Path Prefix** + + **Description** +
+ NR_API_EVENT + + G + + insights-collector.newrelic.com + + 443 + + /v1/accounts/events + + Event API Endpoint +
+ NR_API_LOG + + G + + log-api.newrelic.com + + 443 + + /log/v1 + + Log API Endpoint +
+ NR_API_METRIC + + G + + metric-api.newrelic.com + + 443 + + /metric/v1 + + Metric API Endpoint +
+ NR_API_TRACE + + G + + trace-api.newrelic.com + + 443 + + /trace/v1 + + Trace API Endpoint +
+ +### EU Region + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ **RFC Destination** + + **Conn. Type** + + **Target Host** + + **Service No.** + + **Path Prefix** + + **Description** +
+ NR_API_EVENT_EU + + G + + insights-collector.eu01.nr-data.net + + 443 + + /v1/accounts/events + + Event API Endpoint +
+ NR_API_LOG_EU + + G + + log-api.eu.newrelic.com + + 443 + + /log/v1 + + Log API Endpoint +
+ NR_API_METRIC + + G + + metric-api.eu.newrelic.com + + 443 + + /metric/v1 + + Metric API Endpoint +
+ NR_API_TRACE + + G + + trace-api.eu.newrelic.com + + 443 + + /trace/v1 + + Trace API Endpoint +
+ + + + + A screenshot displaying the SAP install new release and patch + + + + + ## Setup Connection to Remote Database + - This option invokes SAP Transaction **DBACOCKPIT**. + - It verifies that connections to remote HANA DBs are set up correctly. + - Create one DB Connection for each remote **HANA** database you want to monitor. + - See [**Create Database Connection**](/docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package/#create-database-connection) for detailed instructions. + + + + Step-by-step guide on how to define remote HANA DB connections using the SAP transaction `DBACOCKPIT`: + + 1. In the left pane, double-click on **Database Connections** to open the section where you can manage database connections. + 2. Click **Add** to create a new database connection. + 3. Enter the database details: + - **Connection Name:** Enter a name for the connection, preferably the same as the SAP system id for easy identification. + - **Database System:** Select **HANA Database** from the dropdown menu. + - **Database User ID:** Enter the user id of your HANA database. It is recommended to use `NRAGENT`. + - **Password:** Enter the password for the database user id. + - **Confirm Password:** Re-enter the password to confirm it. + - **Database Host:** Enter the hostname or IP address of the HANA database server. + - **SQL Port:** Enter the SQL port number for the HANA database. + A screenshot displaying the SAP HANA database installation + 4. Click **Save**. + 5. To verify the connection, click **Test**. Ensure that the connection test is successful to confirm that the database connection is correctly configured. + + + + + + ## Configure Connections to NR API Endpoints [#configure-connections] + Select this option to complete the connection to New Relic API endpoints. + + 1. Click **New Entries** to add the following details: + - **New Relic Account ID**: Specify the **New Relic Account ID** (optional to prefix it with SAP-) + - **API Ingest Key**: Enter the API key for the New Relic account. + - **Metric Endpoint**: Enter the Metric Endpoint for the New Relic account. + - **Event Endpoint**: Enter the Event Endpoint for the New Relic account. + - **Log Endpoint**: Enter the Log Endpoint for the New Relic account. + - **Trace Endpoint**: Enter the Trace Endpoint for the New Relic account. + + A screenshot displaying the SAP HANA database new entry + 2. Click **Save**. + + Enter them separately along with the API Ingest Key, also multiple accounts can be configured here. + + + + + + ## Copy Template Tables from Client 000 [#copy-template-tables] + Execute this option to copy the table from client 000. + + 1. Click the clock indicator in New Relic icon. + 2. Confirm the successful copy with the success message. + + + + ## Define the Monitored Systems [#define-monitored-systems] + Use this option to define the monitored systems. + + 1. Click **New Entries** and enter the following details: + - **SAP System ID**: Enter the SAP system ID. + - **Client**: Enter the client number. + 2. In the **Data Provider installating information** section, enter the following details: + - **Destination**: Enter the RFC destination for the SAP system. + - **Software Component**: Select the SAP software version from the drop-down. + - **Database Vendor**: Enter the database vendor. + - **Db Connection Name**: Enter the database connection name. (Currently only supports HANA database) + 3. Click **Monitoring Group**. + + A screenshot displaying the SAP HANA database new entry + 4. Click **Yes** on the dialoge box, to specify the **Monitoring Group**. + 4. Select the required monitoring groups for the system, then click generate icon in New Relic when completed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Monitor Group + + Included Data Providers + + Applied to the System Type + + Special Notes +
+ BIZ_DOC + + Change document event for business objects + + ECC systems and S/4 HANA + +
+ DB_KPI + + Key Performance Indicators for databases, such as availability, space, etc. + + All Systems, except HANA Database + +
+ HANA_DB + + HANA Database data providers connect directly to the HANA DB + + All HANA databases + + Requires Database Connection +
+ HOST + + Host metrics such as CPU, Memory, Disk Usage + + All ABAP Systems + +
+ IDOC + + IDOC events + + ECC systems and S/4 HANA + +
+ MAXDB + + Metrics for MAXDB database + + Systems with MAXDB + +
+ MS_SQL + + Metrics for Microsoft SQL Server database + + Systems with Microsoft SQL Server + +
+ Oracle + + Metrics for Oracle Database + + Systems with Oracle Database + +
+ SAP_APPL + + Events, Logs, Metrics, and Traces for SAP Application Monitoring such as RFCs, Jobs, Transactions, etc. + + All ABAP Systems + +
+ SAP_SYSTEM + + Metrics for SAP System and application server instances, monitoring such as User, System Performances, etc. + + All ABAP Systems + +
+ CUSTOM + + Any data provider added by the customer + + +
+ + + + + Maintain the list of Monitoring Groups by navigating to **Expert Mode > Installation Setups > Monitoring Group Maintenance**. + + 5. Once entries are saved, click **BACK** or the **F3** key to go to the next step. + + + + ## Check RFC Destinations [#check-rfc-destinations] + 1. Use this menu option to test the RFC destinations for each of the Monitored Systems and NR API endpoints. + 2. Note that RFC destinations ‘NONE’ are not tested. + + + + ## Generate Configurations for New Data Providers [#generate-configurations] + - Use this menu option to generate all the new data providers related to the new release/patch. + - For a fresh install, all Data Providers (DP) are generated in this step. + - When executing this option, confirm the release and patch to be installed on the first screen. + - If the installation release and patch number is empty, it means the configuration has already been generated. + - If the configuration needs to be re-generated, use the **Re-generate Data Provider Configurations** in the **Maintain Monitored Systems** folder. + + A screenshot displaying the SAP maintain monitored systems + - Alternatively, use the menu option **Reset Installation Flag (to re-install only)** to reset the installation flag and re-generate the configurations. + + + + + ## Verify Installation Completeness [#verify-installation-completeness] + 1. Click **Verify Installation Completeness** to ensure everything is **OK**. + 2. If any item shows a red light, click on the execution button in the **Action Needed** column. + + + + ## Configuration Verification + 1. To verify that data providers are correctly configured, select the **Data Provider Registry Maintenance** folder. + 2. Click **Data Provider Registry**, or use transaction `/n/NEWR/REGISTRY`. + 3. Select any **Data Provider Name** and click **Configure** to verify the configuration parameters. + 4. Click the **TestDP** to test the data provider. + + A screenshot displaying the SAP data provider registry + + + + \ No newline at end of file diff --git a/src/content/docs/sap-solutions/configuration/schedule-jobs.mdx b/src/content/docs/sap-solutions/configuration/schedule-jobs.mdx new file mode 100644 index 00000000000..88c03bbdd26 --- /dev/null +++ b/src/content/docs/sap-solutions/configuration/schedule-jobs.mdx @@ -0,0 +1,76 @@ +--- +title: "Schedule Jobs" +metaDescription: "Efficiently schedule critical jobs for New Relic SAP monitoring with our guide. Ensure optimal data flow with tailored frequencies for RFC checks, data collection, and error handling to maintain continuous system insights." +freshnessValidatedDate: never +--- + +The data collection program `/NEWR/ABAP_COLLECTION_MANAGERN` is the main program that collects data and sends it to New Relic. To ensure efficient data collection, it's recommended to separate data providers into three groups and schedule them as separate jobs. + +## Recommended data provider groups + +### TRACE group + +This group focuses on performance database (STAD) related data providers. It's designed to run efficiently with parallel processing in background RFC processes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Data Provider Name + + Description +
+ `NR.SAP.TRANSACTION` + + Trace Data Provider +
+ `NR.SAP.TRANSACTION.COMPLETE` + + Complete Performance Database Collection with parallel background RFC process. +
+ `NR.SAP.SYSTEM.PROCESS` + + System Process Data Provider. Note that this data provider is suspended after SP02. +
+ NR_SAP_PROGRAM + + Program Data Provider. Note that this data provider is suspended after SP02. +
+ NR_SAP_WORKLOAD_COMPLETE + + Complete Workload Data Provider +
+ NR.SAP.WORKLOAD.COMPLETE + + Workload Data Provider +
diff --git a/src/content/docs/sap-solutions/configuration/visualization-setup-for-new-relic-platform.mdx b/src/content/docs/sap-solutions/configuration/visualization-setup-for-new-relic-platform.mdx new file mode 100644 index 00000000000..297f6e735fb --- /dev/null +++ b/src/content/docs/sap-solutions/configuration/visualization-setup-for-new-relic-platform.mdx @@ -0,0 +1,106 @@ +--- +title: "Visualization setup for New Relic platform" +metaDescription: "A detailed reference on how to setup the New Relic Platform for the SAP environment" +freshnessValidatedDate: never +--- + +New Relic monitoring for SAP includes a list of out-of-the-box feature components. Follow the instructions below to locate and install them. To perform these tasks, you must have New Relic Admin privileges on the account. + + + + + ## Locate SAP monitoring components + + 1. Ensure you have New Relic Admin privileges on the account. + 2. Log in to [one.newrelic.com](https://one.newrelic.com). + 3. If the user has access to multiple accounts, select the sub-account where SAP data is ingested. + 4. Select **+ Integrations & Agents** from the menu, then select the **Apps & Visualizations** link. + 5. Enter **SAP** in the search bar. Review the list of dashboards, alert policies, and apps related to SAP monitoring. + + + + ## Install out-of-the-box SAP dashboards + + ### Install dashboards + + 1. Go to the Dashboards tab in the search results. + 2. Install the following dashboards: + - SAP Dashboards + - SAP Cockpit + - SAP Data Collection Monitoring + - SAP Data Ingestion Estimate + 3. Click each dashboard and select the account to install. The dashboard is created for you. + + ### Add filtering to dashboards + + 1. Access dashboards via the **Dashboards** menu. + 2. Enable facet linking for filtering: + - Click the ellipsis (…) on the widget’s upper right corner. + - Select **Edit** to open the edit screen. + - Toggle the **Filter the current dashboard** switch. + 3. Facet linking can be enabled for Tables, Pie Charts, and Bar Chart widgets to filter by SAP system, instance, IDOC status, jobs, etc. + + + + ## Create lookup table (SAP cockpit only) + + - Create a CSV file with SAP system IDs and environments. + - Example: + + ```sql + SYS_ID Env + GD1 DEV + SD2 DEV + AQ1 Testing + AQ2 Testing + SP1 Prod + SP2 Prod + ``` + + + + ## Steps to create the lookup table on New Relic + + 1. Navigate to **Log > Lookup Table**. + 2. Click **Add a table** and name it **NR_LKUP_SYSTEM**. +Upload the CSV file. + + +1. Select the menu Log -> Lookup Table. +2. Press the "Add a table" button, enter the table name "NR_LKUP_SYSTEM", and upload a CSV file containing the relationship between the environment and the systems. +3. Check the SAP Cockpit dashboard to see if the first page shows the correct system status. + + + + + + +### Install the Out-of-the-box Alerts Policies + +1. Select the Alerts tab. One alert policy is available to install. +2. Click on the "New Relic Monitoring for SAP Solutions" alert policy. Select the account to install, and the alert policy will be installed. +3. Navigate to Alerts & AI -> Alert conditions (Policies) -> Nr4sap default alert policy. Turn on the switch on the right side for each alert condition you’d like to enable. + +### Install IDOC Nerdlet + +1. Select the “App & Visualizations” tab. One App, "IDOC Explorer," is available to install. +2. Select the "IDOC Explorer," click on “Manage access,” then select the account you’d like to access the app. The IDOC Explorer will be visible when viewing IDOC entities. + +### Setup System Workload + +1. Navigate to All entities -> Workloads, click on “+ Create a workload” on the top right corner. +2. Enter the name for the workload, enter the condition `sap.system = {SAP System SID}` on the filter bar, click the “+ Add this query” button to add the query to the workload definition. +3. Click the “Create workload” button to create the workload. The workload will be visible on the “All entities” UI and includes all the entities tagged with the SAP System. + +### Upgrade from Previous Version + +#### Install Upgrade Package + +When upgrading from a previously installed version of New Relic Monitoring for SAP Solutions, pay attention to the packages used, as upgrade packages are often specific to the current version installed. + +1. Use SAP transaction SAINT in client 000 to update the ABAP Add-on. +2. To find out the currently installed version, use the menu path System -> Status. Then click on the button. Look for the product “NEWR” for the version. + +#### Backup the Configuration Template + +If data provider configurations are changed or custom data providers are created, save them to the configuration template to prevent them from being overridden by the new version. Save any configuration changes BEFORE \ No newline at end of file diff --git a/src/content/docs/sap-solutions/installation/install-new-relic-sap-abap-add-on-package.mdx b/src/content/docs/sap-solutions/installation/install-new-relic-sap-abap-add-on-package.mdx new file mode 100644 index 00000000000..3d2d3c3529c --- /dev/null +++ b/src/content/docs/sap-solutions/installation/install-new-relic-sap-abap-add-on-package.mdx @@ -0,0 +1,128 @@ +--- +title: "Install New Relic SAP ABAP add-on package" +metaDescription: "This section applies to both initial installation and upgrade installation." +freshnessValidatedDate: never +--- + +## Add-on installation file [#add-on-installation-file] + +- **Initial installation**: Download the add-on file `K-xxxAOIINNEWR.SAR` file to a folder on your local PC. +- **Upgrade from previous version**: Use the file named `K-xxxAOUINNEWR.SAP`. + +## Install SAP add-on file [#install-sap-add-on-file] + +The ABAP component of NRM4SAP is packaged as a SAP add-on and can be installed using transaction **SAINT**. The following add-on installation must be performed on **client 000**: + + + + + Login to **client 000**. + + **Client 000** in SAP is the default client used for configuration and system administration tasks, and it contains the standard settings provided by SAP. + + + + + Type the transaction code `SAINT` in the SAP GUI command field and press **Enter**. + + + + Go to **Installation Package** > **Load Packages**. + + + + Choose any method to load add-on files: + + + + 1. Navigate to the location of the unzipped files. + 2. Select the appropriate installation file and click **Open** + 3. In the **Content of the compressed file `K-xxxAOIINNEWR.SAR`** popup, click **Decompress**. + A screenshot displaying the Content of the compressed file + 4. The **File K-xxxAOIINNEWR.SAR sucessfully transferred, decompressed and deleted** message appears. + + + + + + 1. Ensure there is a download directory under the trans directory on the application server (`/usr/sap/trans/download`). + 2. Copy the add-on file to this directory. + + + + + + + 1. Untar the SAR file into the PAT file first. Execute the following command on the OS (Linux in this case): + ```sql + cd /usr/sap/trans + cp /tmp/K-300AOIINNEWR.SAR /usr/sap/trans + SAPCAR -xvf K-300AOIINNEWR.SAR + ``` + 2. In the popup, **Do you want to upload OCS Packages from the EPS inbox?**, select **Yes**. Ensure the OCS file is uploaded without errors. + + + + + + + Click **Start** to begin the installation. + + + + Select the package in the **Installable Add-on packages for your system** and click **Continue**. + + + + When prompted with the question, **Do you want to add Modification Adjustment Transports to the queue?**, click **No**. + A screenshot displaying question, Do you want to add Modification Adjustment Transports to the queue? + + Only click **Yes** if adjustment transports are provided in the packaging list with instructions. + + + + + Click the green check button button, to proceed to the next screen. + + If the **Errors during Disassembling OCS Packages** page appears, click **Ignore**. + + + + + Once the package is installed, click **Finish**. The **Sending the runtime analysis** popup appears, you may choose: + - **Send**: this opens a feedback form with the runtime analysis data in a local browser window. You can use this form to send data to SAP. + - **Display**: this would display the runtime analysis first and then send the feedback form in a local browser window. + - **Do not send**: this would leave the dialog without sending the runtime analysis data. + + + + In the **Installed Components** tab, you can verify that the installation was successful. + + + + Logout from **Client 000**. + + You may type **/nex** in the SAP GUI command field to log out of the system. + + + + \ No newline at end of file diff --git a/src/content/docs/sap-solutions/installation/prepare-for-the-installation.mdx b/src/content/docs/sap-solutions/installation/prepare-for-the-installation.mdx new file mode 100644 index 00000000000..1d6ba769912 --- /dev/null +++ b/src/content/docs/sap-solutions/installation/prepare-for-the-installation.mdx @@ -0,0 +1,699 @@ +--- +title: "Prepare for the installation" +metaDescription: "How to install the SAP and alert ecosystems with New Relic" +freshnessValidatedDate: never +--- + +## Prerequisites + +Before you can start, you'll need to sign up for a New Relic account. For New Relic Monitoring for SAP Solutions to function correctly, ensure the following are met: + + - A New Relic [account ID](/docs/accounts/accounts-billing/account-setup/account-id). + - A New Relic . + - Region: [Choose your data center (US or EU)](/docs/accounts/accounts-billing/account-setup/choose-your-data-center/) + - SAP Systems with the required software component release level, as specified by New Relic Monitoring for SAP Solutions. + - Connectivity between the Central Monitoring System and the New Relic cloud. + - Connectivity between the Central Monitoring System and the monitored systems/databases. + + + Approval and/or configuration assistance from your security or network teams may be required to meet these prerequisites. Ensure these steps are completed before starting the installation and filling out the [Checklist for installation readiness](/docs/sap-solutions/installation/prepare-for-the-installation/#checklist-for-installation-readiness) to confirm all environments are correctly set up. + + + + + - Do you already have a New Relic Account for SAP systems monitoring? + - If yes, which New Relic data center is it connected to (US or EU)? + - If not, create a new account connected to one of the data centers. + - List of SAP Systems to be Monitored + - For each monitored system, provide the following: + - System ID and clients + - Database vendor and version + - SAP Release and Patch Level of the following software components: + - SAP_BASIS + - Kernel + - Specify one SAP system to be used as the Central System where NRM4SAP will be installed: + - System ID and client where the ABAP component and configuration will be installed. + - Host name and port of the Proxy Server (if used), including any relevant proxy server policies for access to the New Relic One platform. + + + + + + + + + + + +
+ System ID + + Client + + Database Vendor and Version + + SAP_BASIS Version + + Central System +
+ +**Monitored Systems**: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ **System ID** + + **Client** + + **Database Vendor and Version** + + **SAP_BASIS Version** +
+ System 1 + + + +
+ System 2 + + + +
+ System 3 + + + +
+ +**Optional**: Proxy Hostname and Port + + + + - New Relic Account Info + - NR Account ID + - License/Ingestion Key + - Region + - Login Credential + + + + + + + + + + +
+ NR Account ID + + License/Ingestion Key + + Region + + Login Credential +
+ + - Monitored Systems Info + - System ID (SID) + - Client + - Domain name/IP + - RFC User Name + - RFC User Credential + + + + + + + + + + + +
+ System ID + + Client + + Domain Name/IP + + RFC User Name + + RFC User Credential +
+ + - HANA DB Monitoring Info + - System ID (SID) + - Host Domain/IP + - Tenant Port + - DB User Name + - Accessible from Central Server Tested + + + + + + + + + + + +
+ System ID + + Host Domain/IP + + Tenant Port + + DB User Name + + Accessible from Central Server Tested +
+ + + + - Ensure the firewall is not blocking HTTPs traffic to New Relic. + - Proxy Server Required (if applicable): + - Proxy Server Domain + - Proxy Port + - Authentication Required + - Proxy Username + - Proxy User Password + + + + + + + + + + + +
+ NR Account IProxy Server Domain + + Proxy Port + + Authentication Required + + Proxy Username + + Proxy User Password +
+ + + + +## Download software + +Installation package is available upon request. Please ask your New Relic Account Executive for the link to download the software. + +The downloaded package should contain the following files. The final list of files are listed in **Packing_List.txt** + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 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 +
+ + + The downloaded file is in a zip format, we recommend you to Unzip it to expose the above files. + + +## Monitored systems [#monitored-systems] + +Our agentless architecture allows for the monitoring of SAP systems without the need to install any agents on these systems. The telemetry data is retrieved via RFC connections. To ensure secure and stable connections, SAP system users must be created with specific authorization profiles for these RFC connections. + + + + + Ensure the following SAP components have compatible versions: + + + + + + + + + + + + + + + + + + + + + + +
+ SAP Component + + Compatible Version +
+ SAP_BASIS + + Release 740 and above +
+ Kernel + + Release 753 Patch 602 and above +
+ ST-PI + + Release 740 SP 14 and above +
+ + + + + Upload Authorization Role [`NEWR_DATA_PROVIDER`](/docs/sap-solutions/installation/prepare-for-the-installation/#authorization-objects-used-in-role). + + + See [Upload Authorization Role](/docs/sap-solutions/installation/prepare-for-the-installation/#upload-authorization-role) to know how to upload the authorization role. + + + + + + Create a system type ID with the uploaded role for RFC connection. See [Create New Relic RFC User ID]. + + + + If the monitored database is **HANA**. + - Create SQL Access to be used for monitoring: + - 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. + + + + For monitored databases other than **Hana database**: + - Use the standard **CCMS Database KPI** to monitor database performance. This may need to be activated by running the **ABAP** program **RSDBKPIMON**. + - Use the monitored system ID (e.g., SQ2) as the parameter. Once finished, you should receive the message **Finished creating the nodes** on the status bar. + + + + + + + 1. Use **SAP Transaction PFCG** and go to **Role** > **Upload** to upload the file **_NEWR_DATA_PROVIDER.SAP** from the installation package. + 2. When prompted, confirm that the role `/NEWR/DATA_PROVIDER` should be loaded. + A screenshot displaying the authorization role upload + 3. After it is loaded, select the change icon in SAP icon. + 4. Go to the **Authorizations** tab and select change icon in SAP **Change Authorization Data**. + A screenshot displaying the authorization tab and Change Authorization Data in SAP upload + 5. Select the activate activate icon in SAP button to activate the profile. + 6. If SAP suggests a profile name, select the green check icon to proceed. + 7. Ensure the message **Profile(s) were updated** appears on the status bar. + + + + The following authorization objects are configured with display-only authorization: + + - S_BGRFC + - S_RFC + - S_RFC_ADM + - S_TCODE + - /SDF/E2E + - S_ADMI_FCD + - S_BTCH_ADM + - S_DBCON + - S_SRT_ELOG + - S_SRT_MONI + - S_TABU_DIS + - S_TABU_NAM + - S_TOOLS_EX + - S_XMB_MONI + - S_APPL_LOG + + + + +## Central monitoring system [#central-monitoring-system] + +The central monitoring system is where the New Relic monitoring for SAP solutions is installed. The telemetry data is collected, transformed, and transmitted to the New Relic One platform for analysis and visualization. + + 1. On the Central monitoring system, ensure the following component versions are installed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ 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 SAP version is not listed above, please contact your New Relic account executive. They will provide a supplementary package tailored for your version. + + 2. Ensure the Central Monitoring System is configured with: + - At least 20 Dialog Work Processes. + - At least 10 Background Work Processes. + 3. Ensure outbound HTTPS access to the New Relic data center is allowed from the central monitoring server. + - For more details regarding connection to the US and EU data center, keep reading below table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Connection + + US data center + + EU data center endpoint +
+ 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 +
+ - If a proxy server is required, ensure the proxy policy conditions are adjusted accordingly for accessing New Relic. + - Make note of the following proxy settings: + - Server domain name/IP address and port. + - Proxy access credentials (if authentication is required). + - If HTTPS traffic to New Relic is blocked by a firewall, adjust the firewall policy to allow it. + + + The above connections can be set in the **Central Monitoring System** using **SAP Transaction SM59** and tested. For detailed instructions, see [Set HTTP Destination to New Relic Cloud](). + + 4. For each monitored system specified, create a **RFC Destination**. Use Transaction `SM59` and the remote system ID to create and test the connections. For detailed instructions, see C**reate RFC Destinations for Monitored Systems**. + 5. Ensure the following for monitoring remote HANA databases: + - The Central Monitoring System should have access to the HANA Server and the 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. See the **Create DB Connection** section for detailed instructions. \ No newline at end of file diff --git a/src/content/docs/sap-solutions/new-relic-monitoring-for-sap-solutions.mdx b/src/content/docs/sap-solutions/new-relic-monitoring-for-sap-solutions.mdx new file mode 100644 index 00000000000..f2b135ef1a7 --- /dev/null +++ b/src/content/docs/sap-solutions/new-relic-monitoring-for-sap-solutions.mdx @@ -0,0 +1,34 @@ +--- +title: "New Relic monitoring for SAP solutions" +metaDescription: "Introduction to New Relic monitoring for SAP solutions." +freshnessValidatedDate: never +--- + +New Relic Monitoring for SAP Solutions (NRM4SAP) is a solution that provides telemetry data from SAP systems to the New Relic One platform. It is an agentless solution that collects telemetry data from SAP systems and sends it to the New Relic One platform. The telemetry data includes performance metrics, alerts, logs and taces from the SAP systems. + + A screenshot displaying the SAP agentless architecture + +## Central Monitoring System vs. Monitored Systems [#cms-vs-ms] + + - The SAP systems where the telemetry data are collected are called **Monitored Systems**. The SAP system, where **NRM4SAP** is installed to collect, transform, and transmit the telemetry data is called the **Central System**. + - Normally, **NRM4SAP** needs to be installed on only one SAP system, such as the **SAP Solution Manager (SolMon)**. It uses the standard SAP data provided such as **ST_PI**, **MTE**, and the **performance database**, so no additional agent needs to be installed on all the monitored systems. + + A screenshot displaying the SAP private cloud + +## Data Flow Architecture [#data-flow-architecture] + + SAP telemetry data is pulled into the central system by RFC calls. It is then pushed to the ABAP Enterprise Connector and sent to New Relic One TDP Platform via HTTPS. + +## Components to be installed [#components-to-be-installed] + + Starting from version 3.0, **NRM4SAP** requires the ABAP components, which are installed on the Central Monitoring System. + + As part of the installation process, RFC destinations to the Monitored System are configured with the required authorization. Necessary configurations are also required to secure the HTTPS connection between **NRM4SAP** and **New Relic One** platform. diff --git a/src/nav/root.yml b/src/nav/root.yml index e6031683839..87383c06642 100644 --- a/src/nav/root.yml +++ b/src/nav/root.yml @@ -29,6 +29,8 @@ pages: path: network-performance-monitoring - title: OpenTelemetry path: opentelemetry + - title: SAP Solutions + path: sap-solutions - title: Serverless Monitoring path: serverless-function-monitoring - title: Synthetic Monitoring diff --git a/src/nav/sap-solutions.yml b/src/nav/sap-solutions.yml new file mode 100644 index 00000000000..796e069702b --- /dev/null +++ b/src/nav/sap-solutions.yml @@ -0,0 +1,19 @@ +title: SAP Solutions +path: /docs/sap-solutions +pages: + - title: New Relic monitoring for SAP solutions + path: /docs/sap-solutions/new-relic-monitoring-for-sap-solutions + - title: Installation + pages: + - title: Prepare for the installation + path: /docs/sap-solutions/installation/prepare-for-the-installation + - title: Install New Relic SAP ABAP add-on package + path: /docs/sap-solutions/installation/install-new-relic-sap-abap-add-on-package + - title: Configuration + pages: + - title: Configure New Relic ABAP add-on package + path: /docs/sap-solutions/configuration/configure-new-relic-abap-add-on-package + - title: Schedule Jobs + path: /docs/sap-solutions/configuration/schedule-jobs + - title: Visualization setup for New Relic platform + path: /docs/sap-solutions/configuration/visualization-setup-for-new-relic-platform \ No newline at end of file diff --git a/static/images/activate-option.webp b/static/images/activate-option.webp new file mode 100644 index 00000000000..9d38852464c Binary files /dev/null and b/static/images/activate-option.webp differ diff --git a/static/images/agentless-architecture.webp b/static/images/agentless-architecture.webp new file mode 100644 index 00000000000..5a613ccf125 Binary files /dev/null and b/static/images/agentless-architecture.webp differ diff --git a/static/images/authorisation-role.webp b/static/images/authorisation-role.webp new file mode 100644 index 00000000000..a4831f4978c Binary files /dev/null and b/static/images/authorisation-role.webp differ diff --git a/static/images/change-icon.webp b/static/images/change-icon.webp new file mode 100644 index 00000000000..4158dd4b2e3 Binary files /dev/null and b/static/images/change-icon.webp differ diff --git a/static/images/configure-newrelic.webp b/static/images/configure-newrelic.webp new file mode 100644 index 00000000000..2c5d36c7af5 Binary files /dev/null and b/static/images/configure-newrelic.webp differ diff --git a/static/images/content-of-compressed-file-1.webp b/static/images/content-of-compressed-file-1.webp new file mode 100644 index 00000000000..b5519ed36ea Binary files /dev/null and b/static/images/content-of-compressed-file-1.webp differ diff --git a/static/images/data-provider-registry-1.webp b/static/images/data-provider-registry-1.webp new file mode 100644 index 00000000000..90b50f8a5fe Binary files /dev/null and b/static/images/data-provider-registry-1.webp differ diff --git a/static/images/details-of-added-entry.webp b/static/images/details-of-added-entry.webp new file mode 100644 index 00000000000..60e7d13e7ad Binary files /dev/null and b/static/images/details-of-added-entry.webp differ diff --git a/static/images/generate.webp b/static/images/generate.webp new file mode 100644 index 00000000000..f1c905e7e3d Binary files /dev/null and b/static/images/generate.webp differ diff --git a/static/images/green-tick-button.webp b/static/images/green-tick-button.webp new file mode 100644 index 00000000000..4d554e11581 Binary files /dev/null and b/static/images/green-tick-button.webp differ diff --git a/static/images/http-destination-to-new-relic.webp b/static/images/http-destination-to-new-relic.webp new file mode 100644 index 00000000000..3eaa1812d97 Binary files /dev/null and b/static/images/http-destination-to-new-relic.webp differ diff --git a/static/images/maintain-monitored-systems.webp b/static/images/maintain-monitored-systems.webp new file mode 100644 index 00000000000..2da73e6045b Binary files /dev/null and b/static/images/maintain-monitored-systems.webp differ diff --git a/static/images/modify-adjustement-transports.webp b/static/images/modify-adjustement-transports.webp new file mode 100644 index 00000000000..d1cd368da81 Binary files /dev/null and b/static/images/modify-adjustement-transports.webp differ diff --git a/static/images/new-entry-1.webp b/static/images/new-entry-1.webp new file mode 100644 index 00000000000..6acaf9b87dd Binary files /dev/null and b/static/images/new-entry-1.webp differ diff --git a/static/images/new-relic-sap-abap-collection.webp b/static/images/new-relic-sap-abap-collection.webp new file mode 100644 index 00000000000..2601827a7c1 Binary files /dev/null and b/static/images/new-relic-sap-abap-collection.webp differ diff --git a/static/images/new-relic-sap-clock.webp b/static/images/new-relic-sap-clock.webp new file mode 100644 index 00000000000..c32a892998e Binary files /dev/null and b/static/images/new-relic-sap-clock.webp differ diff --git a/static/images/rfc-destination-1-1.webp b/static/images/rfc-destination-1-1.webp new file mode 100644 index 00000000000..cf404bb48a2 Binary files /dev/null and b/static/images/rfc-destination-1-1.webp differ diff --git a/static/images/sap-authorization-1.webp b/static/images/sap-authorization-1.webp new file mode 100644 index 00000000000..821ec0669e2 Binary files /dev/null and b/static/images/sap-authorization-1.webp differ diff --git a/static/images/sap-hana-database.webp b/static/images/sap-hana-database.webp new file mode 100644 index 00000000000..87f198e0826 Binary files /dev/null and b/static/images/sap-hana-database.webp differ diff --git a/static/images/sap-private-cloud.webp b/static/images/sap-private-cloud.webp new file mode 100644 index 00000000000..3b6e9ff4cc4 Binary files /dev/null and b/static/images/sap-private-cloud.webp differ