After an Automation script is published to Toad Intelligence Central as a script, you can view, run, and manage the script from the Object Explorer or the Script Manager in Toad Data Studio. A script published as a generic file can be viewed and managed, but not run.
Note: This feature is available in the Toad Data Studio Professional edition only and requires access to a Toad Intelligence Central server.
To run an Automation script in Toad Intelligence Central
To cancel (stop) a running script
To schedule or reschedule a script
You can use the Script Manager to view and manage all your Automation scripts. In addition, you can view and access all scripts that have been shared with you or manage all scripts for which you have Manage privileges.
To open the Script Manager
Use the upper pane to view script status, execution result, and execution date for all scripts to which you have access.
Tip: Right-click grid to export script list and execution information to Excel.
To change account used for script execution
Select the Run Details tab in the Alter Schedule dialog. Then specify a user account under which to run the script. For more information about specifying an account for script execution, see Publish Automation Scripts to Intelligence Central .
Note: Only the owner and those with Manage privileges can change the user account for script execution.
To change password on account used for script execution
You can test the database and FTP connections for a script after it is published to Intelligence Central.
To test script connections in Intelligence Central
Use one of the following methods:
To view script execution logs
Use one of the following methods to view script logs.
Note: To manually delete logs, right-click a script in the Script Manager and select Operations | Delete History. You can delete logs for scripts that you own or scripts for which you have Manage privileges.
To view script connections and detailed information
The user account under which the script runs
Tip: If the Username field is empty, the script runs under the default user account. See Publish Automation Scripts to Intelligence Central for more information.
In the Object Explorer, use the following toolbar buttons to perform operations on Automation scripts in TIC.
Button | Description |
---|---|
Modify sharing (visibility) options for the selected script. Specify Sharing and Manage Privileges for Objects | |
Schedule or reschedule the selected script. Note: If the script is disabled, enable it by deselecting the Disable this scheduled Automation option in the Alter Schedule dialog. Change the user account under which the script runs. | |
Update the password or credentials used to execute the selected script. If you update only the password, this action updates the password for each script that runs under this user account. | |
Add or delete tags for the selected script. Alter Tags | |
Disable the selected script's schedule. A disabled script does not run at its scheduled time. However, it does retain its scheduling specifications. Click to enable the selected script's schedule. | |
Run the selected script. Click to stop or cancel the selected script while it is executing. Note: The Cancel Script button displays only while the selected script is executing. | |
Change default value for variable/variables in the selected script. Disabled if variables are not detected. Variables in Views/Scripts and Publishing to Intelligence Central | |
Open the Script Manager to view and manage all scripts to which you have access. | |
Test the selected script's database connections. | |
Delete the saved script execution logs for an Automation script running on Intelligence Central. Note: Only the root user account can delete Automation script logs on Intelligence Central. | |
Edit the selected script. | |
Save a copy of the published script locally. | |
Drop the selected script. | |
Lock the selected script. Lock and Unlock Objects | |
Unlock the selected script. Lock and Unlock Objects |
Users with Manage privileges can do the following (unless the object is locked):
In most cases, you can use the error message or the execution log to troubleshoot Automation script execution issues. For additional help, see the following:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center