Toad DevOps Toolkit exposes key Toad for Oracle functionality (such as Code Analysis and Unit Testing) as programmable objects that can be called from DevOps scripts such as PowerShell or Visual Basic. This enables you to include database-development steps into your Continuous Integration model through tools such as Jenkins or Bamboo.
What this all really means is that the deployment of Oracle application and database upgrades is now made much easier, keeping your team more productive and your end users satisfied with their business tools. Developers can now handle shorter release cycles without compromising quality for speed. Database administrators can now be more proactive with database improvements, even in the face of ever-increasing responsibilities and the growing complexity and variety of modern database systems.
Requirement |
Details |
---|---|
Memory |
Note: The memory required may vary based on the following:
|
Hard disk space |
|
Operating system |
|
Requirement |
Details |
---|---|
Database client |
An Oracle client must be installed and configured on the system where you are running Toad DevOps Toolkit. The following are supported:
Note: You must use the 32-bit version of Toad DevOps Toolkit with the 32-bit Oracle client, and the 64-bit version of Toad DevOps Toolkit with the 64-bit Oracle client. |
Database server |
Oracle versions:
Important: It is recommended that your client version be of the same release (or later) as your database server. This is an Oracle recommendation to prevent performance issues. |
Cloud database service |
Oracle Database as a Service on Amazon EC2 and Oracle Cloud |
In order to run Toad DevOps Toolkit against the database, the following privileges are required:
Operating System |
Requirements |
---|---|
Windows 7 |
|
Windows 8 and later Windows Server 2012 and 2016 |
|
Note: You can install multiple versions of Toad DevOps Toolkit side-by-side, but only one Com object is registered at a time.
Before you can use Toad DevOps Toolkit, you must apply your license key. A .dlv license file containing a valid license key is used to license Toad DevOps Toolkit.
Quest provides you with a license file (.dlv) containing a valid license.
When Toad DevOps Toolkit is installed, a license configuration file (License.cfg) is installed in C:\ProgramData\Quest Software\Toad Devops Toolkit. This configuration file specifies a default path to the .dlv file.
You can place the .dlv file in the default location specified in the configuration file, or you can place the .dlv file in a new location and then change the specified path in the License.cfg file.
Upon initial launch, Toad DevOps Toolkit reads the .dlv file and caches the license locally (in the ProductLicenses.xml file). When the locally-cached license expires, Toad DevOps Toolkit again searches the .dlv file (location specified by the License.cfg file) for a valid license.
To manually apply a license for Toad DevOps Toolkit
To add a license using a script
You can add a license from a .dlv file by running the following command using PowerShell:
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing.AddLicense('full_path')
$TDT.Quit()
where full_path is the full path and file name of the .dlv file containing the license to add
Example: $TDT.Licensing.AddLicense('C:\mynewlicense.dlv')
To refresh cached license
If you need to load a new license from the .dlv file before your current license expires, run the following command using PowerShell:
Caution: This command clears the locally-cached license before reading the .dlv file specified by License.cfg.
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing.Refresh()
$TDT.Quit()
To show license information
To show the locally-cached license information, run the following command using PowerShell:
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing
$TDT.Quit()
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center