(NEW) NR-331473 : New Relic monitoring for SAP

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.
+
+      <table>
+        <thead>
+          <tr>
+            <th style={{ width: "200px" }}>
+                Data Provider Name
+              </th>
+              <th>
+                Description
+              </th>
+            </tr>
+        </thead>
+          <tbody>
+            <tr>
+              <td>
+                `NR.SAP.TRANSACTION`
+              </td>
+              <td>
+                Trace Data Provider
+              </td>
+            </tr>
+            <tr>
+              <td>
+                `NR.SAP.TRANSACTION.COMPLETE`
+              </td>
+              <td>
+                Complete Performance Database Collection with parallel background RFC process.
+              </td>
+            </tr>
+            <tr>
+              <td>
+                `NR.SAP.SYSTEM.PROCESS`
+              </td>
+              <td>
+                System Process Data Provider. Note that this data provider is suspended after SP02.
+              </td>
+            </tr>
+            <tr>
+              <td>
+                NR_SAP_PROGRAM
+              </td>
+              <td>
+                Program Data Provider. Note that this data provider is suspended after SP02.
+              </td>
+            </tr>
+            <tr>
+              <td>
+                NR_SAP_WORKLOAD_COMPLETE
+              </td>
+              <td>
+                Complete Workload Data Provider
+              </td>
+            </tr>
+            <tr>
+              <td>
+                NR.SAP.WORKLOAD.COMPLETE
+              </td>
+              <td>
+                Workload Data Provider
+              </td>
+            </tr>
+          </tbody>
+        </table>

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.
+
+<Steps>
+
+  <Step>
+    ## 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.
+  </Step>
+
+  <Step>
+    ## 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.
+    </Step>
+
+    <Step>
+    ## 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
+            ```
+    </Step>
+
+    <Step>
+    ## 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.
+
+  </Step>
+</Steps>
+
+
+
+### 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

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 <DNT>**SAINT**</DNT>. The following add-on installation must be performed on **client 000**:
+
+<Steps>
+
+  <Step>
+    Login to **client 000**.
+  <Callout variant="important">
+    **Client 000** in SAP is the default client used for configuration and system administration tasks, and it contains the standard settings provided by SAP.
+  </Callout>
+  </Step>
+
+  <Step>
+    Type the transaction code `SAINT` in the <DNT>SAP GUI command field</DNT> and press **Enter**.
+  </Step>
+
+  <Step>
+    Go to <DNT>**Installation Package** > **Load Packages**</DNT>.
+  </Step>
+
+  <Step>
+    Choose any method to load add-on files:
+
+  <CollapserGroup>
+    <Collapser
+      id="sar-archive-from-frontend"
+      title="SAR Archive from Frontend"
+    >
+      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**.
+      <img
+          title="Content of the compressed file"
+          alt="A screenshot displaying the Content of the compressed file"
+          src="/images/content-of-compressed-file-1.webp"
+          width=""
+          />
+      4. The **File K-xxxAOIINNEWR.SAR sucessfully transferred, decompressed and deleted** message appears.
+    </Collapser>
+  </CollapserGroup>
+
+  <CollapserGroup>
+    <Collapser
+      id="sar-archive-from-application-server"
+      title="SAR Archive from application server"
+    >
+      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.
+
+    </Collapser>
+  </CollapserGroup>
+
+  <CollapserGroup>
+    <Collapser
+      id="eps-files-from-application-server"
+      title="EPS Files from Application Server"
+    >
+      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, <DNT>**Do you want to upload OCS Packages from the EPS inbox?**</DNT>, select **Yes**. Ensure the OCS file is uploaded without errors.
+
+    </Collapser>
+  </CollapserGroup>
+  </Step>
+
+  <Step>
+    Click **Start** to begin the installation.
+  </Step>
+
+  <Step>
+    Select the package in the **Installable Add-on packages for your system** and click **Continue**.
+  </Step>
+
+  <Step>
+    When prompted with the question, **Do you want to add Modification Adjustment Transports to the queue?**, click **No**.
+      <img
+          title="Do you want to add Modification Adjustment Transports to the queue?, Click No"
+          alt="A screenshot displaying question, Do you want to add Modification Adjustment Transports to the queue?"
+          src="/images/modify-adjustement-transports.webp"
+          width="700"
+          />
+  <Callout variant="important">
+    Only click **Yes** if adjustment transports are provided in the packaging list with instructions.
+  </Callout>
+  </Step>
+
+  <Step>
+    Click the <img src="/images/green-tick-button.webp" class="inline" style={{height: "25px", width: "30px"}} alt="green check button" title="Green check button" /> button, to proceed to the next screen.
+  <Callout variant="tip">
+    If the **Errors during Disassembling OCS Packages** page appears, click **Ignore**.
+  </Callout>
+  </Step>
+
+  <Step>
+    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.
+  </Step>
+
+  <Step>
+    In the **Installed Components** tab, you can verify that the installation was successful.
+  </Step>
+
+  <Step>
+    Logout from **Client 000**.
+    <Callout variant="tip">
+      You may type **/nex** in the SAP GUI command field to log out of the system.
+    </Callout>
+  </Step>
+
+  </Steps>