Merge pull request #290066 from batamig/json-ii

removing mention of the json file

Author: Jill Grant

articles/sentinel/sap/cross-workspace.md

@@ -66,7 +66,7 @@ To do this, use the following steps:
 
 - **Use Log Analytics in Azure Monitor to manage access to data by resource**. For more information, see [Manage access to Microsoft Sentinel data by resource](../resource-context-rbac.md).
 
-- **Associate SAP resources with an Azure resource ID**. Specify the required `azure_resource_id` field in the connector configuration section on the data collector that you use to ingest data from the SAP system into Microsoft Sentinel. For more information, see [Connector configuration](reference-systemconfig-json.md#connector-configuration).
+- **Associate SAP resources with an Azure resource ID**. This option is supported only for a data connector agent deployed via CLI. Specify the required `azure_resource_id` field in the connector configuration section on the data collector that you use to ingest data from the SAP system into Microsoft Sentinel. For more information, see [Deploy an SAP data connector agent from the command line](deploy-command-line.md) and [Connector configuration](reference-systemconfig-json.md#connector-configuration).
 
 :::image type="content" source="media/cross-workspace/sap-cross-workspace-combined.png" alt-text="Diagram that shows how to work with the Microsoft Sentinel solution for SAP applications by using the same workspace for SAP and SOC data." border="false":::
 

articles/sentinel/sap/deploy-command-line.md

@@ -147,7 +147,7 @@ This procedure describes how to create a new agent and connect it to your SAP sy
     docker update --restart unless-stopped <container-name>
     ```
 
-The deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. For more information, see [SAP data connector agent configuration file](deployment-overview.md#sap-data-connector-agent-configuration-file).
+The deployment procedure generates a [**systemconfig.json**](reference-systemconfig-json.md) file that contains the configuration details for the SAP data connector agent. The file is located in the `/sapcon-app/sapcon/config/system` directory on your VM.
 
 ## Deploy the data connector using a configuration file
 
@@ -230,7 +230,7 @@ Azure Key Vault is the recommended method to store your authentication credentia
     docker update --restart unless-stopped <container-name>
     ```
 
-The deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. For more information, see [SAP data connector agent configuration file](deployment-overview.md#sap-data-connector-agent-configuration-file).
+The deployment procedure generates a [**systemconfig.json**](reference-systemconfig-json.md) file that contains the configuration details for the SAP data connector agent. The file is located in the `/sapcon-app/sapcon/config/system` directory on your VM.
 
 ## Prepare the kickstart script for secure communication with SNC
 

articles/sentinel/sap/deploy-data-connector-agent-container.md

@@ -5,7 +5,7 @@ author: batamig
 ms.author: bagol
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 09/15/2024
+ms.date: 10/28/2024
 appliesto:
     - Microsoft Sentinel in the Azure portal
     - Microsoft Sentinel in the Microsoft Defender portal
@@ -363,14 +363,14 @@ While deployment is also supported from the command line, we recommend that you
 
     :::image type="content" source="media/deploy-data-connector-agent-container/logs-page.png" alt-text="Screenshot of the Logs tab in the Add new system side pane.":::
 
+1. (Optional) For optimal results in monitoring the SAP PAHI table, select **Configuration History**. For more information, see [Verify that the PAHI table is updated at regular intervals](preparing-sap.md#verify-that-the-pahi-table-is-updated-at-regular-intervals).
+
 1. Review the settings you defined. Select **Previous** to modify any settings, or select **Deploy** to deploy the system.
 
-The system configuration you defined is deployed into Azure Key Vault. You can now see the system details in the table under **Configure an SAP system and assign it to a collector agent**. This table displays the associated agent name, SAP System ID (SID), and health status for systems that you added via the portal or otherwise.
+The system configuration you defined is deployed into the Azure key vault you defined during the deployment. You can now see the system details in the table under **Configure an SAP system and assign it to a collector agent**. This table displays the associated agent name, SAP System ID (SID), and health status for systems that you added via the portal or otherwise.
 
 At this stage, the system's **Health** status is **Pending**. If the agent is updated successfully, it pulls the configuration from Azure Key vault, and the status changes to **System healthy**. This update can take up to 10 minutes.
 
-The deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. For more information, see [SAP data connector agent configuration file](deployment-overview.md#sap-data-connector-agent-configuration-file).
-
 ## Check connectivity and health
 
 After you deploy the SAP data connector agent, check your agent's health and connectivity. For more information, see [Monitor the health and role of your SAP systems](../monitor-sap-system-health.md).

articles/sentinel/sap/deployment-overview.md

@@ -80,15 +80,6 @@ We recommend that you involve all relevant teams when planning your deployment t
 - [Collect SAP HANA audit logs](collect-sap-hana-audit-logs.md)
 - [Deploy SAP connector manually](sap-solution-deploy-alternate.md)
 
-## SAP data connector agent configuration file
-
-The deployment procedure generates a **systemconfig.json** file that contains the configuration details for the SAP data connector agent. The file is located in the `/sapcon-app/sapcon/config/system` directory on your VM. You can use this file to update the configuration of your SAP data connector agent.
-
-Earlier versions of the deployment script, released before June 2023, generated a **systemconfig.ini** file instead. For more information, see:
-
-- [Systemconfig.json file reference](reference-systemconfig-json.md)
-- [Systemconfig.ini file reference](reference-systemconfig.md) (legacy)
-
 ## Stop SAP data collection
 
 If you need to stop Microsoft Sentinel from collecting your SAP data, stop log ingestion and disable the connector. Then remove the extra user role and any optional CRs installed on your SAP system.

articles/sentinel/sap/preparing-sap.md

@@ -93,10 +93,7 @@ The SAP PAHI table includes data on the history of the SAP system, the database,
 
 If the PAHI table is updated regularly, the `SAP_COLLECTOR_FOR_PERFMONITOR` job is scheduled and runs hourly. If the `SAP_COLLECTOR_FOR_PERFMONITOR` job doesn't exist, make sure to configure it as needed. 
 
-For more information, see:
-
-- SAP documentation: [Database Collector in Background Processing](https://help.sap.com/doc/saphelp_nw75/7.5.5/c4/3a735b505211d189550000e829fbbd/frameset.htm) and [Configuring the Data Collector](https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_752/3364beced9d145a5ad185c89a1e04658/c43a818c505211d189550000e829fbbd.html)
-- [Optimize SAP PAHI table monitoring (recommended)](deploy-command-line.md#optimize-sap-pahi-table-monitoring-recommended)
+For more information, see [Database Collector in Background Processing](https://help.sap.com/doc/saphelp_nw75/7.5.5/c4/3a735b505211d189550000e829fbbd/frameset.htm) and [Configuring the Data Collector](https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_752/3364beced9d145a5ad185c89a1e04658/c43a818c505211d189550000e829fbbd.html).
 
 ## Configure your system to use SNC for secure connections
 

articles/sentinel/sap/reference-kickstart.md

@@ -354,4 +354,3 @@ For more information, see:
 
 - [Deploy and configure the container hosting the SAP data connector agent](deploy-data-connector-agent-container.md)
 - [Troubleshoot your Microsoft Sentinel solution for SAP applications solution deployment](sap-deploy-troubleshoot.md)
-- [Systemconfig.json file reference](reference-systemconfig-json.md)

articles/sentinel/sap/reference-systemconfig-json.md

@@ -15,9 +15,9 @@ ms.collection: usx-security
 ---
 # Microsoft Sentinel solution for SAP applications `systemconfig.json` file reference
 
-The *systemconfig.json* file is used to configure the behavior of the Microsoft Sentinel for SAP applications data connector agent. This article describes the options available in each section of the configuration file.
+The *systemconfig.json* file is used to configure the behavior of the Microsoft Sentinel for SAP applications data connector agent when [deployed from the command line](deploy-command-line.md). This article describes the options available in each section of the configuration file.
 
-Content in this article is intended for your **SAP BASIS** teams.
+Content in this article is intended for your **SAP BASIS** teams, and is only relevant when your data connector agent is deployed from the command line. We recommend [deploying your data connector agent from the portal](deploy-data-connector-agent-container.md) instead.
 
 > [!IMPORTANT]
 > Microsoft Sentinel solution for SAP applications uses the *systemconfig.json* file for agent versions released on or after June 22, 2023. For previous agent versions, you must still use the *[systemconfig.ini file](reference-systemconfig.md)*.

articles/sentinel/sap/reference-systemconfig.md

@@ -16,14 +16,10 @@ ms.collection: usx-security
 
 # Microsoft Sentinel solution for SAP applications `systemconfig.ini` file reference
 
-The *systemconfig.ini* file is used to configure the behavior of the Microsoft Sentinel for SAP applications data connector agent. This article describes the options available in each section of the configuration file.
+The *systemconfig.ini* file is the legacy file used to configure the behavior of the Microsoft Sentinel for SAP applications data connector agent in versions earlier than June 22, 2023. This article describes the options available in each section of the configuration file.
 
-Content in this article is intended for your **SAP BASIS** teams.
+Content in this article is intended for your **SAP BASIS** teams. This article is not relevant if you've used the [recommended deployment procedure](deploy-data-connector-agent-container.md) from the portal. If you've installed a newer version of the agent from the command line, use the [Microsoft Sentinel solution for SAP applications `systemconfig.json` file reference](reference-systemconfig-json.md) instead.
 
-> [!IMPORTANT]
-> Microsoft Sentinel solution for SAP applications uses the *[systemconfig.json file](reference-systemconfig-json.md)* for agent versions released on or after June 22, 2023. For previous agent versions, you must still use the *systemconfig.ini* file.
->
-> If you update the agent version, the configuration file is automatically migrated.
 
 ## Systemconfig configuration file sections
 
@@ -249,4 +245,3 @@ For more information, see:
 
 - [Deploy and configure the container hosting the SAP data connector agent](deploy-data-connector-agent-container.md)
 - [Troubleshoot your Microsoft Sentinel solution for SAP applications solution deployment](sap-deploy-troubleshoot.md)
-- [Systemconfig.json file reference](reference-systemconfig-json.md)

articles/sentinel/sap/reference-update.md

@@ -107,4 +107,3 @@ For more information, see:
 
 - [Deploy and configure the container hosting the SAP data connector agent](deploy-data-connector-agent-container.md)
 - [Troubleshoot your Microsoft Sentinel solution for SAP applications solution deployment](sap-deploy-troubleshoot.md)
-- [Systemconfig.json file reference](reference-systemconfig-json.md)

articles/sentinel/sap/sap-deploy-troubleshoot.md

@@ -18,7 +18,7 @@ ms.collection: usx-security
 
 This article includes troubleshooting steps to help you ensure accurate and timely data ingestion and monitoring for your SAP environment with Microsoft Sentinel.
 
-In this article, we refer to the [**systemconfig.json**](reference-systemconfig-json.md) file, which is used for agent versions released on or after June 22, 2023. If you're using an earlier version of the agent, refer to the [**systemconfig.ini**](reference-systemconfig.md) file instead.
+Selected troubleshooting procedures are only relevant when your data connector agent is [deployed via the command line](deploy-command-line.md). If you used the recommended procedure to [deploy the agent from the portal](deploy-data-connector-agent-container.md), use the portal to make any configuration changes.
 
 ## Useful Docker commands
 
@@ -46,6 +46,8 @@ docker logs -f sapcon-[SID]
 
 ## Enable/disable debug mode printing
 
+This procedure is only supported if you've deployed the [data connector agent from the command line](deploy-command-line.md). 
+
 1. On your data collector agent container virtual machine, edit the [**/opt/sapcon/[SID]/systemconfig.json**](reference-systemconfig-json.md) file.
 
 1. Define the **General** section if it wasn't previously defined. In this section, define `logging_debug = True` to enable debug mode printing, or `logging_debug = False` to disable it.
@@ -67,9 +69,9 @@ Connector execution logs for your Microsoft Sentinel solution for SAP applicatio
 
 ## Review and update the Microsoft Sentinel for SAP agent connector configuration file
 
-If you [deployed your agent via the portal](deploy-data-connector-agent-container.md#deploy-the-data-connector-agent-from-the-portal-preview), you can continue to maintain and change configuration settings via the portal.
+This procedure is only supported if you've deployed the [data connector agent from the command line](deploy-command-line.md).  If you [deployed your agent via the portal](deploy-data-connector-agent-container.md#deploy-the-data-connector-agent-from-the-portal-preview), continue to maintain and change configuration settings via the portal.
 
-If you deployed via the command line, or want to make manual updates directly to the configuration file, perform the following steps:
+If you deployed via the command line, perform the following steps:
 
 1. On your VM, open the configuration file: **sapcon/[SID]/systemconfig.json**
 
@@ -126,6 +128,8 @@ docker cp nwrfc750P_8-70002752.zip /sapcon-app/inst/
 
 ### ABAP runtime errors appear on a large system
 
+This procedure is only supported if you've deployed the [data connector agent from the command line](deploy-command-line.md).  
+
 If ABAP runtime errors appear on large systems, try setting a smaller chunk size:
 
 1. Edit the [**/opt/sapcon/[SID]/systemconfig.json**](reference-systemconfig-json.md) file and in the **Connector Configuration** section define `timechunk = 5`.
@@ -174,6 +178,8 @@ docker restart sapcon-[SID]
 
 ### Incorrect SAP ABAP user credentials in a fixed configuration
 
+This section is only supported if you've deployed the [data connector agent from the command line](deploy-command-line.md). 
+
 A fixed configuration is when the password is stored directly in the [**systemconfig.json**](reference-systemconfig-json.md) configuration file.
 
 If your credentials there are incorrect, verify your credentials.
@@ -232,6 +238,8 @@ Common issues include:
 
 ### Retrieving an audit log fails with warnings
 
+This section is only supported if you've deployed the [data connector agent from the command line](deploy-command-line.md). 
+
 If you attempt to retrieve an audit log without the [required configurations](preparing-sap.md#configure-sap-auditing) and the process fails with warnings, verify that the SAP Auditlog can be retrieved using one of the following methods:
 
 - Using a compatibility mode called *XAL* on older versions