With the introduction of the Incorta Cloud, the customer administrator no longer has access to the backend Incorta servers. This means that certain scripting features that are delivered with the product and are accessible in on-premises installations are not accessible in cloud installations. However, this does NOT mean that scripting for Cloud installations is not possible. This document will explain how to implement running Incorta Scripting from a remote machine.
As mentioned in the Introduction, Incorta installations contain prewritten scripts for performing many tasks such as:
In the cloud, the Incorta Customer Administrator no longer has access to the backend server directory that contains these scripts.
First it is important, as referenced above, that these programs (as Python scripts) are not part of the Incorta "services" running your Analytics or Loader. Instead the Python code (incorta.py) makes certain functions available for scripting using Incorta's internal API for these functions. Therefore, a Linux server with access to the internet, with the required directories copied to that machine can become a machine capable of running these scripts against the Incorta Cluster in the Cloud.
The ZIP files for the code that needs to be installed on the remote machine is attached and can be downloaded from this article.
|This contains objects that are necessary for the /bin scripts to run. No scripts reside in this zip file.
|This contains all of the delivered python and scripts delivered with a typical incorta install in the <Incorta Install Path>/IncortaNode/bin directory.
That's it! You are now capable of accessing all of the <file-name>.sh scripts delivered by Incorta in a typical install. Good Luck and happy scripting.
0**** <username> cd /home/<username>/incorta_bin/bin && ./<script-name>.sh >> <log-name>.log 2>&1