Skip to content

Commit addbaf2

Browse files
authored
Merge pull request #225717 from linda33wj/purview-doc-update
Add new article about SHIR versioning
2 parents 04c02d9 + 40c1f80 commit addbaf2

File tree

5 files changed

+59
-4
lines changed

5 files changed

+59
-4
lines changed

articles/purview/manage-integration-runtimes.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: how-to
9-
ms.date: 01/10/2023
9+
ms.date: 01/31/2023
1010
---
1111

1212
# Create and manage a self-hosted integration runtime
@@ -117,7 +117,9 @@ You can register multiple nodes for a self-hosted integration runtime using the
117117

118118
You can edit a self-hosted integration runtime by navigating to **Integration runtimes** in the Microsoft Purview governance portal, hover on the IR then select the **Edit** button.
119119

120-
In the **Settings** tab, you can update the description, copy the key, or regenerate new keys. In the **Nodes** tab, you can manage the registered nodes. And in the **Version** tab, you can see the IR version status.
120+
- In the **Settings** tab, you can update the description, copy the key, or regenerate new keys.
121+
- In the **Nodes** tab, you can see a list of the registered nodes, along with the status, IP address, and the option of node deletion. Learn more from [High availability and scalability](#high-availability-and-scalability).
122+
- In the **Version** tab, you can see the IR version status. Learn more from [Self-hosted integration runtime auto-update and expire notification](self-hosted-integration-runtime-version.md).
121123

122124
:::image type="content" source="media/manage-integration-runtimes/edit-integration-runtime-settings.png" alt-text="edit IR details.":::
123125

@@ -127,7 +129,7 @@ You can delete a self-hosted integration runtime by navigating to **Integration
127129

128130
If you move your cursor over the icon or message in the notification area, you can see details about the state of the self-hosted integration runtime.
129131

130-
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/system-tray-notifications.png" alt-text="Notifications in the notification area":::||
132+
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/system-tray-notifications.png" alt-text="Notifications in the notification area":::
131133

132134
### Service account for Self-hosted integration runtime
133135

76.7 KB
Loading
38.6 KB
Loading
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: Self-hosted integration runtime auto-update and expiration
3+
description: Learn about self-hosted integration runtime auto-update and expiration in Microsoft Purview.
4+
author: linda33wj
5+
ms.author: jingwang
6+
ms.service: purview
7+
ms.subservice: purview-data-map
8+
ms.topic: how-to
9+
ms.date: 01/31/2023
10+
---
11+
12+
# Self-hosted integration runtime auto-update and expiration
13+
14+
This article will describe how to let self-hosted integration runtime auto-update to the latest version and how Microsoft Purview manages the versions of self-hosted integration runtime.
15+
16+
## How to check your self-hosted integration runtime version
17+
18+
You can check the version of your self-hosted integration runtime in Microsoft Purview governance portal -> Data map -> Integration runtimes:
19+
20+
:::image type="content" source="./media/self-hosted-integration-runtime-version/self-hosted-integration-runtime-version-portal.png" alt-text="Screenshot that shows the version in Microsoft Purview governance portal.":::
21+
22+
You can also check the version in your self-hosted integration runtime client -> Help tab.
23+
24+
## Self-hosted Integration Runtime auto-update
25+
26+
Auto update is enabled by default when you install a self-hosted integration runtime. You have two options to manage the version of self-hosted integration runtime: auto-update or maintain manually. Typically, Microsoft Purview releases two new versions of self-hosted integration runtime every month, which includes new feature release, bug fix or enhancement. So we recommend users to update to newer version in order to get the latest feature and enhancement.
27+
28+
The self-hosted integration runtime will be automatically updated to newer version. When new version is available while not yet scheduled for your instance, you can also trigger the update from the portal.
29+
30+
:::image type="content" source="media/self-hosted-integration-runtime-version/shir-auto-update-with-new-version.png" alt-text="Screenshot of checking the self-hosted integration runtime version and trigger update.":::
31+
32+
> [!NOTE]
33+
> If you have multiple self-hosted integration runtime nodes, there is no downtime during auto-update. The auto-update happens in one node first while others are working on tasks. When the first node finishes the update, it will take over the remain tasks when other nodes are updating. If you only have one self-hosted integration runtime node, then it has some downtime during the auto-update.
34+
35+
## Auto-update version vs latest version
36+
37+
To ensure the stability of self-hosted integration runtime, although we release two versions, we'll only push one version every month. So sometimes you'll find that the auto-update version is the previous version of the actual latest version. If you want to get the latest version, you can go to [download center](https://www.microsoft.com/download/details.aspx?id=39717) and do so manually. Additionally, **auto-update** to a new version is managed by the service, and you can't change it.
38+
39+
The self-hosted integration runtime **Version** tab in Microsoft Purview governance portal shows the newer version if current version is old. When your self-hosted integration runtime is online, this version is the auto-update version and will automatically update your self-hosted integration runtime in the scheduled time. But if your self-hosted integration runtime is offline, the page only shows the newer version.
40+
41+
If you have multiple nodes, and for some reasons that some of them aren't auto-updated successfully. Then these nodes roll back to the version, which was the same across all nodes before auto-update.
42+
43+
## Self-hosted Integration Runtime expiration
44+
45+
Each version of self-hosted integration runtime will be expired in one year. The expiring message is shown in Microsoft Purview governance portal and the self-hosted integration runtime client **90 days** before expiration.
46+
47+
## Next steps
48+
49+
- [Create and manage a self-hosted integration runtime](manage-integration-runtimes.md)

articles/purview/toc.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,11 @@ items:
154154
href: manage-credentials.md
155155
displayName: Create and manage credentials
156156
- name: Manage integration runtimes
157-
href: manage-integration-runtimes.md
157+
items:
158+
- name: Create and manage a self-hosted integration runtime
159+
href: manage-integration-runtimes.md
160+
- name: Self-hosted integration runtime auto-update and expiration
161+
href: self-hosted-integration-runtime-version.md
158162
- name: Manage assets with Metamodel
159163
href: how-to-metamodel.md
160164
- name: Create Service Principal

0 commit comments

Comments
 (0)