You can use Toad Data Point to publish Automation scripts to a Toad Intelligence Central (TIC) server in order to share scripts with other users. Read this topic to better understand how Toad publishes Automation scripts.
Note: This feature is available in the Toad Data Point Professional edition only and requires access to a Toad Intelligence Central server.
Toad performs the following steps when publishing an Automation script to TIC.
Test runs the script (in the TIC environment)
Note:Toad does not test run the script if you deselect this option in the Publishing dialog.
It is important to know how Toad modifies your script prior to publishing and how Toad handles your script's input and output files.
Toad Embeds SQL Files—When publishing an Automation script, Toad embeds into the script any SQL files used by the script. See How Toad Manages Input and Output Files for more information.
Use Network File Paths—For best results, modify your script to only use input and output files stored in a network location (except those files that will be embedded). Please note that Toad does not check the script for local file paths before publishing.
Review the following table to learn how Toad manages input and output files so you can modify your script if necessary.
|Input/Output Files Used by Automation Activities||Toad Embeds
|For Best Results Use Network Paths Only*|
|Toad files: Data Compare, Data Cleansing, Visualization, Pivot Grid, and Toad Data Report|
|Toad Import and Export templates|
|Automation script used by the Run Automation Script activity|
|SQL files used by Toad Import and Export templates (provides query)|
SQL files used by Select to File, Execute Script, and Select to Editor with Results activities (provides query)
Toad embeds the file and deselects the Link SQL file option.
Note: This action applies only to published scripts. When you specify the Embed SQL into Automation script option in non-published scripts, Toad does not embed these files.
|Non-SQL files used by Import/Export templates (Excel, CSV)|
|Files used by activities such as Copy File, Delete File, and Zip Files|
All output files, including:
* The drive letter in a network path is replaced with the full UNC name during publishing.
To ensure a successfully-published script, prepare your script and the TIC environment. See Prepare to Publish Automation Scripts for more information.
When an Automation script is published to TIC, the passwords for the script's database connections are encrypted using 256-bit AES encryption. Each connection is encrypted using a new AES key and initialization vector.
The symmetric key is then encrypted by the publishing client using an asymmetric 1024-bit RSA public key that is generated separately for each installation of TIC. The private key is stored in the Windows machine key storage on the server where TIC is running.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad