WebSphere MQ Workflow 3.4 Generic C API Test / Prototyping Tool

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

Overview

The tool components offer the necessary features to perform tests of 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 interface diagram.


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

To perform a test run, do the following:
  1. Define the test scenario by a sequence of APIs that are written in Tool Syntax (see Tool Syntax Introduction and Tool Syntax Example).
  2. Store the scenario in an ASCII file. If no file extension is specified, the tool uses dat (xxxxxxxx .dat).
  3. Install the MQ Series Workflow Generic C API Test and Prototyping Tool .
  4. Execute the API scenario by invoking the Tool.
  5. Look for the execution result.

    The result of a test run is also stored in a ASCII file. If no file extension is specified, the tool uses log (yyyyyyyy.log).
    The result file contains the test case name, a time stamp, the key words for class and method names of the APIs, the parameters, return codes, and other result values . If an expected return code or an expected value is specified in the xxxxxxxx.dat file , the result file also contains a comparison between actual and expected return code or value .

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