You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article will explain how to run Self-Hosted Integration Runtime in Windows container.
19
-
Azure Data Factory are delivering the official windows container support of Self-Hosted Integration Runtime. You can download the docker build source code and combine the building and running process in your own continuous delivery pipeline.
18
+
Azure Data Factory provides Windows container support for the Self-Hosted Integration Runtime. You can [download the Docker Build source code](https://github.com/Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container) and combine the building and running process in your own continuous delivery pipeline.
19
+
20
+
> [!TIP]
21
+
> This article explains how to run the Self-Hosted Integration Runtime in a Windows container on a compatible physical or virtual machine. If you don't want to manage infrastructure, you can run the Self-Hosted Integration Runtime on Azure App Service. For more information, see the [Azure Data Factory self-hosted integration runtime on App Service](https://github.com/Azure-Samples/azure-data-factory-runtime-app-service) sample.
> AUTH_KEY is mandatory for this command. NODE_NAME, ENABLE_HA and HA_PORT are optional. If you don't set the value, the command will use default values. The default value of ENABLE_HA is false and HA_PORT is 8060.
44
-
45
-
## Container health check
46
-
After 120 seconds startup period, the health checker will run periodically every 30 seconds. It will provide the IR health status to container engine.
30
+
31
+
1.[Install Docker and enable Windows containers.](/virtualization/windowscontainers/quick-start/set-up-environment)
32
+
33
+
1.[Download the container image source code from GitHub.](https://github.com/Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container)
34
+
35
+
1. If you need to use a specific version of the SHIR, you can download it and move it to the *SHIR* folder.
36
+
37
+
Otherwise, skip this step. The container image build process will download the latest version of the SHIR automatically.
> The `AUTH_KEY` environment variable is mandatory and must be set to the auth key value for your data factory.
59
+
>
60
+
> The `NODE_NAME`, `ENABLE_HA` and `HA_PORT` environment variables are optional. If you don't set their values, the command will use default values. The default value of `ENABLE_HA` is `false`, and the default value of `HA_PORT` is `8060`.
61
+
62
+
## Container health check
63
+
64
+
After the 120 second startup period, the health check runs periodically every 30 seconds. It provides the SHIR's health status to the container engine.
47
65
48
66
## Limitations
49
-
Currently we don't support below features when running Self-Hosted Integration Runtime in Windows container:
67
+
68
+
Currently we don't support the below features when running the Self-Hosted Integration Runtime in Windows containers:
69
+
50
70
- HTTP proxy
51
-
- Encrypted Node-node communication with TLS/SSL certificate
71
+
- Encrypted node-node communication with TLS/SSL certificate
52
72
- Generate and import backup
53
73
- Daemon service
54
-
- Autoupdate
74
+
- Auto-update
55
75
56
76
### Next steps
77
+
57
78
- Review [integration runtime concepts in Azure Data Factory](./concepts-integration-runtime.md).
58
79
- Learn how to [create a self-hosted integration runtime in the Azure portal](./create-self-hosted-integration-runtime.md).
0 commit comments