You can customize Test Integrations and APIs to use
other scripting languages. The language must have a .jar file that
supports the Java™ Scripting API and can embed in the
product.
You must download the required JAR files and then add the
JAR files to Library Manager. You must follow this
procedure wherever the scripting engine is utilized in the Agent installation.
-
Start Library Manager in any of the following methods:
-
In Microsoft™
Windows™, you can start Library Manager by using
the Library Manager
(set-up) option in
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\DevOps Test
API.
-
Click the LibConfig.exe file in the installation directory of Test Integrations and APIs.
For example, the installation directory path can be C:\Program Files\IBM\DevOpsTestAPI
-
Select Scripting Engines as the application.
-
Click Add in the Provider panel
to add the provider of the application JAR files.
-
Enter a name in the Rename Provider dialog.
-
Select the provider by clicking the checkbox.
-
Click Add in the Settings
panel.
The Select Files To Add dialog is displayed.
-
Open the folder on your computer where you downloaded the files.
-
Select the JAR files, and then click Add
Files.
The
JAR files that you added are displayed in the
Resource column in the
Settings panel.
Note: The JAR
files are installed in the directory displayed in the
Installation Directory field after you click
OK.
-
Click OK to install the application
JAR files and close Library Manager.
Example: Adding Groovy script to Test Integrations and APIs
For example, to add a Groovy script to
Test Integrations and APIs, complete the
following steps:
- From the Groovy website, download
the latest stable release.
- Perform step 1 through step 9 to add the Groovy
JAR files to the Library Manager.
- Restart Test Integrations and APIs.
- Groovy is displayed as an option in the drop-down menu for the
Function.
The script files are installed in the default installation directory of Test Integrations and APIs.