WebSphere MQ Workflow 3.4.0 Java Generic API Test / Prototyping Tool

[prev][next][parent][TOC]

Overview

The tool components offer the necessary features to perform tests of WebSphere MQ Workflow API definitions independent of the platform on which they are to be implemented.

They also allow you to perform different tasks. The following functions are available:



The tool offers the following interfaces: For more details, see the interface diagram.


The APIs are defined using a special language called Tool Syntax.

To perform a test case, do the following:
  1. Define the test scenario by a sequence of APIs written in the following Tool Syntax. You can choose to use:

  2. Store the scenario in an ASCII file. If no file extension is specified, the tool will use dat (xxxxxxxx .dat).

  3. Prepare a property file (JGATT.properties) for Agent settings. This is optional if you use the Java API Tool Syntax, but it is required for the C API Tool Syntax.

  4. Install the MQ Series Workflow Java Generic API Test and Prototyping Tool .

  5. Execute the API scenario by invoking the Tool.

  6. Look for the execution result.

    The result of a test case is also stored in an ASCII file. If no extension is specified, the tool will use log (yyyyyyyy.log).

    The result file contains the name of the test case, a timestamp, certain system properties, the key words for class and method names of the APIs, the parameters, exception reports, and other result values. If an expected exception or an expected value is specified in the xxxxxxxx.DAT file, the result file also contains a comparison between actual and expected exception or value.

For certain APIs (...PersistentOid() and ...PersistentObject() and remote activity implementation APIs), the tool offers optional additional input / output files (see PersistentObject example and and Remote Activity Implementation Example).