Communication is via a control channel that uses a shared Azure Relay connection.
Credential synchronization is transparent to the data developer and is handled by the self-hosted IR.Īzure Data Factory and Synapse pipelines communicate with the self-hosted integration runtime to schedule and manage jobs. Each node encrypts the credentials by using DPAPI and stores them locally. If multiple nodes are set for high availability, the credentials are further synchronized across other nodes.
LIGHTZONE JAVA RUNTIME WINDOWS
The self-hosted integration runtime node encrypts the credentials by using Windows Data Protection Application Programming Interface (DPAPI) and saves the credentials locally. Then the data developer creates a linked service for an on-premises data store, specifying the self-hosted integration runtime instance that the service should use to connect to data stores. Here is a high-level summary of the data-flow steps for copying with a self-hosted IR:Ī data developer first creates a self-hosted integration runtime within an Azure data factory or Synapse workspace by using the Azure portal or the PowerShell cmdlet. When you move data between on-premises and the cloud, the activity uses a self-hosted integration runtime to transfer the data between an on-premises data source and the cloud. If you use the self-hosted integration runtime as a proxy for SSIS integration runtime, FIPS-compliant encryption can be enabled and will be used when moving data from on premises to Azure Blob Storage as a staging area.Ĭurrently self-hosted integration runtime can only be shared with multiple data factories, it can't be shared across Synapse workspaces or between data factory and Synapse workspace. To disable FIPS-compliant encryption, change the following registry subkey's value from 1 (enabled) to 0 (disabled): HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled. To work around this problem, you have two options: store credentials/secret values in an Azure Key Vault or disable FIPS-compliant encryption on the server.
For example, if you have two self-hosted integration runtimes that serve two data factories, the same on-premises data source can be registered with both data factories. You can have multiple self-hosted integration runtimes on different machines that connect to the same on-premises data source.When the self-hosted integration runtime and data source are on different machines, the self-hosted integration runtime doesn't compete with the data source for resources.
LIGHTZONE JAVA RUNTIME INSTALL
We recommend that you install the self-hosted integration runtime on a machine that differs from the one that hosts the on-premises data source. However, having the self-hosted integration runtime close to the data source reduces the time for the self-hosted integration runtime to connect to the data source. The self-hosted integration runtime doesn't need to be on the same machine as the data source.If you have two data factories or Synapse workspaces that need to access on-premises data sources, either use the self-hosted IR sharing feature to share the self-hosted IR, or install the self-hosted IR on two on-premises computers, one for each data factory or Synapse workspace. You can install only one instance of a self-hosted integration runtime on any single machine.For more information, see Sharing a self-hosted integration runtime. You can also share it with another data factory within the same Azure Active Directory (Azure AD) tenant. You can use a single self-hosted integration runtime for multiple on-premises data sources.Considerations for using a self-hosted IR
LIGHTZONE JAVA RUNTIME HOW TO
To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az. To get started with the Az PowerShell module, see Install Azure PowerShell. This article uses the Azure Az PowerShell module, which is the recommended PowerShell module for interacting with Azure.