Working with Jacada

The Jacada Interface Server provides an interface layer for mainframe applications. This layer separates the user interface from the application logic in order to insulate the organization from changes in standards and technologies.

Note: Java 8 is not supported in Jacada.

Recording a Jacada Vuser

VuGen records Jacada's Java thin-client.

To record communication with the Jacada server through the HTML thin-client, use the Web HTTP/HTML type Vuser. For more information, see Web Protocols (Generic).

Back to top

Editing a Jacada Vuser Script

The Actions method of a Java Vuser script using Jacada, has two main parts: properties and body. Use the properties section to retrieve and set the server properties. Once your have the server properties you can connect to the Jacada server.

 // Set system properties...
        _properties = new Properties(System.getProperties());
        _properties.put("", "true");
        _jacadavirtualuser = new cst.client.manager.JacadaVirtualUser();
        _jacadavirtualuser.connectUsingPorts("localhost", 1100, "LOADTEST", "", "", "");

The body of the script contains the user actions along with the exception handling blocks for the checkFieldValue and checkTableCell methods.

Example: try {
        _jacadavirtualuser.checkFieldValue(23, "S44452BA");
        } catch(java.lang.Exception e) {

try {
    	_jacadavirtualuser.checkTableCell(41, 0, 0, "");
        } catch(java.lang.Exception e) {

The checkField method has two arguments: field ID number and expected value. The checkTableCell method has four arguments: table ID, row, column, and expected value. If there is a mismatch between the expected value and the received value, an exception is generated.

By default, the try-catch wrapper blocks are commented out. To use them in your script, remove the comment markers.

In addition to the recorded script, you can add any of the Java Vuser API functions. For a list of these functions and information on how to add them to your script, see Java Vuser (Manual) Protocol.

Back to top

Replaying Jacada Scripts

Before replay, you must download the clbase.jar file from the Jacada server.

All extra files such as jars, classes, and so on, used by the Java Vuser must be accessible by the script by doing one of the following:

  • Add the files to the script's Extra Files folder: In the Solution Explorer pane, right click the Extra Files node and select Add Files to Script. The files are copied to the script's folder.
  • In the script's runtime settings, in Java Environment > Classpath, set the classpath to the Java classes. These files are then used as a reference, but are not contained in the script's folder.

During replay, the Jacada server may return screens from the legacy system in a different order than they appear in the recorded script. This may cause an exception in the replay. For information on how to handle these exceptions, contact Customer support.

Back to top