Skip to content

Commit 535bc4f

Browse files
authored
Merge pull request #222697 from limwainstein/sap-auto-update
Sap auto update
2 parents 386b9bb + 2335758 commit 535bc4f

File tree

2 files changed

+50
-8
lines changed

2 files changed

+50
-8
lines changed

articles/sentinel/sap/update-sap-data-connector.md

Lines changed: 44 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,62 @@
11
---
2-
title: Update Microsoft Sentinel's SAP data connector agent | Microsoft Docs
2+
title: Update Microsoft Sentinel's SAP data connector agent
33
description: This article shows you how to update an already existing SAP data connector to its latest version.
44
author: MSFTandrelom
55
ms.author: andrelom
6-
ms.topic: reference
7-
ms.date: 11/07/2022
6+
ms.topic: how-to
7+
ms.date: 12/31/2022
88
---
99

1010
# Update Microsoft Sentinel's SAP data connector agent
1111

1212
This article shows you how to update an already existing Microsoft Sentinel for SAP data connector to its latest version.
1313

14-
If you have a Docker container already running with an earlier version of the SAP data connector, run the SAP data connector update script to get the latest features available.
14+
To get the latest features, you can [enable automatic updates](#automatically-update-the-sap-data-connector-agent-preview) for the SAP data connector agent, or [manually update the agent](#manually-update-sap-data-connector-agent).
1515

16-
## Update SAP data connector agent
16+
Note that the automatic or manual updates described in this article are relevant to the SAP connector agent only, and not to the Microsoft Sentinel Solution for SAP. To successfully update the solution, your agent needs to be up to date. The solution is updated separately.
1717

18-
Make sure that you have the most recent versions of the relevant deployment scripts from the Microsoft Sentinel GitHub repository.
18+
## Automatically update the SAP data connector agent (Preview)
19+
20+
You can choose to enable automatic updates for the connector agent on [all existing containers](#enable-automatic-updates-on-all-existing-containers) or a [specific container](#enable-automatic-updates-on-a-specific-container).
21+
22+
> [!IMPORTANT]
23+
> Automatically updating the SAP data connector agent is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
24+
25+
### Enable automatic updates on all existing containers
26+
27+
To enable automatic updates on all existing containers (all containers with a connected SAP agent), run the following command on the collector VM:
28+
29+
```
30+
wget -O sapcon-sentinel-auto-update.sh https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/SAP/sapcon-sentinel-auto-update.sh && bash ./sapcon-sentinel-auto-update.sh
31+
```
32+
33+
The command creates a cron job that runs daily and checks for updates. If the job detects a new version of the agent, it updates the agent on all containers that exist when you run the command above. If a container is running a Preview version that is newer than the latest version (the version that the job installs), the job doesn't update that container.
34+
35+
If you add containers after you run the cron job, the new containers are not automatically updated. To update these containers, in the */opt/sapcon/[SID or Agent GUID]/settings.json* file, define the `auto_update` parameter for each of the containers as `true`.
36+
37+
The logs for this update are under *var/log/sapcon-sentinel-register-autoupdate.log/*.
38+
39+
### Enable automatic updates on a specific container
40+
41+
To enable automatic updates on a specific container or containers, run the following command:
42+
43+
```
44+
wget -O sapcon-sentinel-auto-update.sh https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/SAP/sapcon-sentinel-auto-update.sh && bash ./sapcon-sentinel-auto-update.sh --containername <containername> [--containername <containername>]...
45+
```
46+
47+
The logs for this update are under */var/log/sapcon-sentinel-register-autoupdate.log*.
48+
49+
### Disable automatic updates
50+
51+
To disable automatic updates for a container or containers, define the `auto_update` parameter for each of the containers as `false`.
52+
53+
## Manually update SAP data connector agent
54+
55+
To manually update the connector agent, make sure that you have the most recent versions of the relevant deployment scripts from the Microsoft Sentinel GitHub repository.
1956

2057
Run:
2158

22-
```azurecli
59+
```
2360
wget -O sapcon-instance-update.sh https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/SAP/sapcon-instance-update.sh && bash ./sapcon-instance-update.sh
2461
```
2562

articles/sentinel/whats-new.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,12 @@ See these [important announcements](#announcements) about recent changes to feat
1717

1818
[!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
1919

20+
## March 2023
21+
22+
### Automatically update the SAP data connector agent (Preview)
23+
24+
You can now [enable automatic updates for the SAP data connector agent](sap/update-sap-data-connector.md#automatically-update-the-sap-data-connector-agent-preview). You can choose to apply automatic updates to all existing containers or to a specific container.
25+
2026
## February 2023
2127

2228
- [Out-of-the-box content centralization changes](#out-of-the-box-content-centralization-changes) (in [Announcements](#announcements) section below)
@@ -54,7 +60,6 @@ To give you more flexibility in scheduling your analytics rule execution times a
5460

5561
[Learn more about advanced scheduling](detect-threats-custom.md#query-scheduling-and-alert-threshold).
5662

57-
5863
## January 2023
5964

6065
- [New incident investigation experience (Preview)](#new-incident-investigation-experience-preview)

0 commit comments

Comments
 (0)