cancel
Showing results for 
Search instead for 
Did you mean: 
JeffW
Employee
Employee

Introduction

When Incorta is installed on premises, Incorta effectively uses it's data connectors to load data from both data sources that are located within the your internal network, as well as, those cloud based data sources (Oracle EBS, Salesforce, etc) that are accessible in the public network from your internal network.  With the introduction of the Incorta Cloud SaaS based solution, the Incorta connectors need to maintain the same connectivity, however, now the Incorta services themselves are running in the public network.  How does the Incorta Cloud connect to data resources that reside inside a private network?  The answer is the Incorta Data Agent.

Simply stated, the Data Agent is a small Incorta program that is installed within your internal network.  The Data Agent communicates with the Incorta Cloud Cluster and is responsible for executing the queries against data sources that are located within the your internal network when requested, and then returning the results of those queries to the Cloud via a secure and encrypted data path.

Incorta Topology.png

What you need to know before reading this article

Let's Go

Where to locate and installation?

As mentioned above, the Data Agent must be installed somewhere within your private network.  It should be located in a location on the network that has access to the data sources it will be required to pull data from.  If network latency could be an issue within the private network, then more than one Data Agent may be installed within the customer's network, choosing physical locations close to the data sources. 

The Data Agent must be installed on a Linux server existing within the your network.  For information about the technical requirements & procedure for installing the Data Agent service, please refer to the following link. (Requirements for the Data Agent service host & Install Procedures )

When to Use Multiple Data Agents

As mentioned above, it is possible to install multiple Data Agents within a network. The primary reasons for doing so are:

  1. Physical Location: it is best to create a Data Agent physical server located in the network close to the data source in order to take network latency out of the query timings.  This is NOT required, but in the case where a customer may support multiple physical data centers, it may be a good idea to locate one Data Agent machine within each data center.
  2. Data Agent Service: The Data Agent may be installed more than once on a Data Agent machine to support the data traffic for more than one cluster (Dev, UAT, and Prod).  Each version of the Data Agent must be installed in a different subdirectory and be configured with a separate Authorization File (see the configuration section below for a discussion on Auth files). Once installed, the Data Agent service can be started from each of the installed directories and each data agent service will support 1 and only 1 cluster.

To download the Data Agent software, login to your Customer Cloud Portal account at https://cloud.incorta.com/signin then open your Cluster to see the main page.  Then from the "Configurations" Tab in the portal, scroll down to where you see the following:

Screen Shot 2022-06-01 at 3.43.51 PM.png

You can see that there is both a link to installation steps & a download link for the software.  Also note, that here as well you have the ability to enable or disable the use of the Data Agent functionality for your cluster.  Ensure the it is toggled to the ON position.  After the ZIP file is downloaded, it must be copied to the Data Agent server, and uncompressed into the folder where the Data Agent service will be run.  This is also where the Auth file will be placed, and where Log files for the Data agent will be written.

Other Networking & Configuration Requirements

In order for the Data Agent service to be able to communicate with the Incorta Cloud, there are a few additional steps that need to be taken.

Customer Side Network

The communication with the Data Agent and the Incorta Cluster is bidirectional.  In order for the Data Agent to communicate with the Incorta Cloud, the following steps need to be taken.

First, a number of public IP addresses need to be whitelisted within the customer's network.  Currently, the IP addresses are:

  • 35.247.100.158
  • 34.70.36.234
  • 34.135.137.144
  • 35.239.15.155
  • 35.226.25.43
  • 34.121.189.240
  • 34.72.39.30
  • 35.202.239.17
  • 35.202.81.205
  • 35.239.193.0
  • 34.122.210.64
  • 34.121.68.20
  • 34.122.220.237
  • 104.154.22.33
  • 107.178.213.4
  • 34.72.114.207
  • 104.197.16.55
  • 34.134.154.80
  • 34.134.57.103
  • 35.222.71.239
  • 35.226.200.86
  • 34.123.173.187
  • 35.222.15.231
  • 34.71.48.7
  • 35.239.123.213
  • 34.70.139.40
  • 34.70.71.47

Secondly, the Loader and Analytics services communicate with the Data Agent over 2 Ports. In many installations, these ports may be set to the Default of 6767 and 6768.  However, in some Clusters, you will find alternate port numbers created dynamically by the system.  You can find these port numbers by logging into the Incorta CMC as Administrator and navigating to the "Cluster Configurations --> Server Configurations" panel.  There you will see which ports are being used for the Data Agent, and you can ensure that the "Enable Data Agent" switch is set to the ON position.

Screen Shot 2022-06-01 at 3.28.17 PM.png

These ports need to be open for external bidirectional network traffic at the customer's firewall.

Incorta Application

Setting up the Data Agent from the Incorta UI is quite simple.  You must log in to Incorta with a user that has either the Admin or Schema Manager role, which will allow access to the Data Tab in Incorta.

Screen Shot 2022-06-01 at 3.51.55 PM.png

By clicking on the New button at the top right of the screen and selecting "Add Data Agent" you will be presented with the following screen:

Screen Shot 2022-06-01 at 3.54.28 PM.png

Fill in the name and the optional description and then click on Create. You will then be presented with the option to create the Authentication File.

Screen Shot 2022-06-01 at 3.57.19 PM.png

Click on Generate Now, and you will see that a file is downloaded to your machine in the Downloads folder.  The filename will end in a .auth file extension.  This file will need to be copied to the Data Agent server on the customer's network into the <data agent install folder>/conf directory.  Before the data agent service is started, the Data Agent in the Incorta UI will reflect that it is NOT communicating with the Data Agent by a red circled X as shown below:

Screen Shot 2022-06-01 at 4.00.01 PM.png

Note on the Authorization File: The reason for the Authorization file is to give the Data Agent service the information it needs to communicate securely with the Cloud Cluster for which it is being configured.  As mentioned previously, each Data Agent service can communicate with 1 and only 1 Incorta Cluster.  The Authorization File (which is encrypted itself) contains the certificate and all the other information that the Data Agent service needs to connect to an Incorta Cloud Cluster.

Follow the procedure to start the Data Agent Service on the Data Agent server after having applied the Port, IP Whitelisting, and installation of the Auth file. The status should change to a green X indicating that the Data Agent service is communicating with the Incorta Cloud servers. 

Screen Shot 2022-06-01 at 4.09.53 PM.png

Special Considerations

Data Agent Upgrades

The Data Agent is software.  Just like the Incorta version of the software that you are using in the Cloud, it has a version number associated with its release.  There are periodic updates to the Data Agent software, and it will be necessary for you to update your Data Agent from time to time.  Typically, if you are performing an upgrade to Incorta, the release notes will indicate which version of the Data Agent is current for that version of Incorta.  Follow the download procedure discussed above to download the latest version of the Data Agent from your cloud portal after an upgrade to Incorta is applied.  Then follow the steps to

  1. Stop the data agent service using the "./agent.sh stop" command
  2. Take a backup copy of your Auth file
  3. Apply the new Zip file to the <data agent install directory> 
  4. Place the Auth file in the <data agent install directory>/conf directory if it is not already there
  5. Start the data agent service using the "./agent.sh start" command

Your Data Agent service in the UI should report green X status.  If it does not, contact Support for assistance.

Data Sources that are NOT Data Agent Compatible

It should be noted that some of the Incorta Data Connectors are NOT compatible with the Data Agent.  Most of the connectors that are NOT supported by the Data Agent are data sources hosted by other SaaS providers, where our Incorta connector is utilizing a published API to get the data from that data source. Examples of data sources not supported by the Data Agent include:

  • Oracle Cloud Applications
  • Salesforce
  • SAP
  • etc.

As SaaS providers themselves, customers are typically accessing these systems using pubic IP addresses or public URLs.  In this case there is no need to access the data "through" the customer's private network because the data is available in the public network with the correct connect string and access credentials.  If you have any questions about specific data sources NOT supported by Incorta's Data Agent, you can contact your Customer Support Manager, or you Sales Account Manager, and they will be able to direct you to the correct resource to answer your question. 

Related Material

Here are some links to assist you in getting started with Incorta:

Best Practices Index
Best Practices

Just here to browse knowledge? This might help!

Contributors
Version history
Last update:
‎06-06-2022 07:59 AM
Updated by: