java com.ibm.workflow.api.tool.JGATT <[path]tc fn> <[path]log fn> or jre -classpath <path> com.ibm.workflow.api.tool.JGATT <[path]tc fn> <[path]log fn> or java com.ibm.workflow.api.tool.JGATT Syntax <FileSpec> or ...Abbreviations:
tc test case log result fn file name path e.g. d:\data\ FileSpec e.g. d:\data\syntax.txt [...] optional
If no test case file name extension is specified, an extension "dat" is expected. If no result file name extension is specified, the tool will create an extension "log".Invocation Example of the Test Tool as MQ Workflow Client Application :
java com.ibm.workflow.api.tool.JGATT d:\testcase\tc01 d:\result\tc01Invocation Example to retrieve the Test Tool Syntax:
java com.ibm.workflow.api.tool.JGATT syntax d:\testcase\syntax.txt
Usage: java com.ibm.workflow.api.tool.JGATT [-option [argument] ...] Some valid option and argument combinations: java <ToolName> -i <> -o <> [-u <>] [-p <>] [-g <>] [-s <>] [-y <>] [-l <>] [-n <>] [-f] [-d] java <ToolName> -x <> java <ToolName> -h The following options are valid: -i <TestCase> test case input file name -o <Result> test case output file name -u <UserID> user id -p <Password> password -g <SystemGroup> system group name -s <System> system name -y <Configuration> configuration identifier -e <SessionID> session identifier -l <AgentLocator> agent locator -n <AgentName> agent name -h help (this help) -f finish without System.exit(rc) -d dump arguments -c dump class/lib path settings -x <Syntax> syntax output file nameIf you use API parameters (for example -uADMIN) also refer to the tool syntax on how to use them within an API template (Keyword: <CL-VALUE>) and see also example API parameter via command line.
NOTE: Flags -e and -c are not features of the tool for MQ Workflow 3.2.2.