Skip to content

Commit 6930ac0

Browse files
Merge pull request #306648 from MartinPankraz/enhance-prereq-checker
clarify prereq checker guidance
2 parents 1a4fce2 + f7bb251 commit 6930ac0

2 files changed

Lines changed: 8 additions & 5 deletions

File tree

articles/sentinel/includes/sap-agentless-prerequisites.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,9 @@ ms.topic: include
99
**To run the tool**:
1010

1111
1. Open the integration package, navigate to the artifacts tab, and select the **Prerequisite checker** iflow > **Configure**.
12-
1. Set the target RFC destination to the SAP system you want to check.
13-
1. Deploy the iflow as you would otherwise for your SAP systems. For example, use the following sample PowerShell script, modifying the sample placeholder values for your environment:
12+
1. Set the target destination name for the remote function call (RFC) to the SAP system you want to check. For example, `A4H-100-Sentinel-RFC`.
13+
1. Deploy the iflow as you would otherwise for your SAP systems.
14+
1. Trigger the iflow from any REST client. For example, use the following sample PowerShell script, modifying the sample placeholder values for your environment:
1415

1516
```powershell
1617
$cpiEndpoint = "https://my-cpi-uri.it-cpi012-rt.cfapps.eu01-010.hana.ondemand.com" # CPI endpoint URL
@@ -37,4 +38,6 @@ ms.topic: include
3738
Write-Host $response.RawContent
3839
```
3940
40-
Make sure that the prerequisites checker runs successfully before connecting to Microsoft Sentinel.
41+
Make sure that the prerequisites checker runs successfully (status code 200) with no warnings on the response output before connecting to Microsoft Sentinel.
42+
43+
If any findings, consult the response details for guidance on remediation steps. Legacy SAP systems often require extra SAP notes. Furthermore, see the [troubleshooting section](../sap/sap-deploy-troubleshoot.md) for common issues and resolutions.

articles/sentinel/sap/preparing-sap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -203,11 +203,11 @@ This procedure has steps both in Microsoft Sentinel and your SAP system, and req
203203
1. Download the [integration package](https://aka.ms/SAPAgentlessPackage) and upload it to your SAP Integration Suite. For more information, see the [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/importing-integration-packages).
204204
1. Open the package and go to the **Artifacts** tab. Then select the **Data Collector** configuration. For more information, see the [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/importing-integration-packages).
205205
1. Configure the integration flow with the **LogIngestionURL** and the **DCRImmutableID**.
206-
1. Deploy the i-flow using SAP Cloud Integration as the runtime service.
206+
1. Deploy the iflow using SAP Cloud Integration as the runtime service.
207207

208208

209209
## Run the prerequisite checker
210-
1. The **Prerequisite checker** iflow is included in the package. We recommend running this iflow before continuing to the next step to ensure that your SAP system meets the system prerequisites.
210+
1. The **Prerequisite checker** iflow is included in the package. We recommend running this iflow **manually** before continuing to the next step to ensure that your SAP system meets the system prerequisites before attempting integration from Microsoft Sentinel.
211211

212212
[!INCLUDE [sap-agentless-prerequisites](../includes/sap-agentless-prerequisites.md)]
213213

0 commit comments

Comments
 (0)