Installing Microsoft Azure Integration Runtime

The Integration Runtime (IR) is a customer managed data integration infrastructure used by Azure Data Factory to provide data integration capabilities across different network environments. It was formerly called as Data Management Gateway.

It is used by Business Central and Dynamics GP to provide a one-way data synchronization between your on-premises SQL Server hosting your company databases, and your Business Central tenant data store in the cloud via Azure Data Factory.

The self-hosted IR is capable of:
  • Running copy activity between a cloud data stores and a data store in private network.
  • Dispatching the following transform activities against compute resources in On-Premise or Azure Virtual Network: HDInsight Hive activity (BYOC), HDInsight Pig activity (BYOC), HDInsight MapReduce activity (BYOC), HDInsight Spark activity (BYOC), HDInsight Streaming activity (BYOC), Machine Learning Batch Execution activity, Machine Learning Update Resource activities, Stored Procedure activity, Data Lake Analytics U-SQL activity, .Net custom activity, Lookup activity, and Get Metadata activity.
To install, go to the Assisted Setup page and download the installation file. Copy the authentication key as you will need it for the configuration step.

NOTE: Be sure to scroll horizontally to the end of the line while selecting the key text.


Launch the installation file to begin the setup process. You must first select the language which you will be using with the Integration Runtime.


Accept (or not) the end-user license agreement to continue with the installation process.


Select the installation folder to host the application files.


Click the install button to begin the installation process. You may be prompted to run the application with elevated permissions to bypass User Account Control settings on your machine.


Once the installation has been completed, click Finish to proceed with IR's configuration.


Paste the Authentication Key from step 1. If you require to bypass proxy settings within your organization, be sure to click on the Change link to setup your proxy info.


The following screen will allow you to enter the name of the self-hosted node and will display a list of nodes as configured by Business Central on the Azure Data Factory service. Also, you may enable remote access from your intranet to the integration node. Click finish when done.


If you choose to enable remote access for management purposes, you must enter an open TCP/IP port on your firewall. By default, this port is 8060. Should you want to enable secure access to while remoting into the node, be sure to select a certificate. You can also enable remote access without a certificate.


Finally, click on Finish to complete the configuration settings an finalize the node registration process.


For more information on Azure Data Factory, please visit:
https://docs.microsoft.com/en-us/azure/data-factory/

For more information on Azure Integration Runtime, please visit:
https://docs.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime

Until next post,

MG.-
Mariano Gomez, MVP

Comments

Julian Nachajon said…
hello,
Can i connect GP to Dynamics CRM Online with this tool?
there is any connector to use?

best
cici said…
Hi Mario

The Cloud migration works fine for master data.
But there is an action in Cloud Migration Management named "Managed Custom Tables".
I added one table GL00100 from GP but the migration reports a key violation when the IR is trying to insert a second record with the pk = 0.
Definitely, more stuff to do to make migration work for tables other then master data. I wonder if you know what is needed to bring other tables in BC.
cici said…
Nice feature.
But it doesnt work for tables other than master tables.
For example I added a GP on premise table GL00100 in Custom migration tables and migration fails for GL00100.
I was wondering if you know what might be needed to bring data in for this table.

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

eConnect Integration Service for Microsoft Dynamics GP 2010