WebSphere MQ Workflow 3.4 Generic C API Test / Prototyping Tool

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

Tool Components

The tool contains the following logical components:

* Parser

* Navigator

* Object Manager

* Executor

* Verifier



Parser

The main function of the "Parser" is to interpret the contents of the input file. The input file for the tool contains information about a sequence of APIs or macros and their parameters, which have to be executed. It uses a special "Syntax" and is stored in an ASCII file as a test case.

Information about MQ Workflow objects (object handles) is passed to "Object Manager" to resolve indexes to real object references.
API, macro statements, and parameters other than object indexes are transferred directly to the "Executor" .


Navigator

The "Navigator" manages the tool components from one API or Macro statement to the next one . If a loop statement is found , the "Navigator" performs the loop until the loop expression is met . If comments are found , they are ignored .


Object Manager

With an API, you can create, delete, or change MQ Workflow objects. To execute such an API, you must specify objects as parameters.
Objects( instances ) exist longer than a single API call . The "ObjectManager" must resolve an externally defined object handle to the real object reference. It then stores that information while the tool is active. This means that the stored information is available for a sequence of API calls.

Executor

The main task is to execute a single API or macro with the parameters
that are passed from the "Parser" and "ObjectManager" . The "Executor" receives return codes, MQ Workflow objects, or other objects ( for example, character string object ). This result together with
the expected result will be passed to the "Verifier" .
Note: A macro is a test tool method (e.g. TestTool_ Sleep) or
contains combined APIs (e.g. Container_COPY_IN_TO_OUT).


Verifier

The "Verifier" compares the actual result with the expected result . A result report is created as an ASCII file .