Using EIP Testing Projects

This section describes how to:

  • Create EIP Testing projects.

  • Specify file input and output directories.

  • Override requesting and destination nodes.

  • Start batch processing.

  • Use the Batch Project Executor Command Line Tool

The first step to using an EIP Testing project is creating the EIP Testing (Batch EIP) project type. To create a project, select File > New Project. Information about creating projects is provided earlier in the Send Master product documentation.

See Creating Send Master Projects.

To add input files to this project type, you specify the directory location where the files reside.

To specify input files for EIP Testing projects:

  1. In the Input Information section, in the Input Directory field, select the location of the input files.

  2. In the Output Directory field, select the location where the output files should be written.

  3. (Optional.) Select Create If Not Found to create the input and output directories, if they do not exist.

  4. (Optional.) Select Overwrite File to direct Send Master to overwrite any output files that exist with the same names.

  5. Select File > Save Project.

Send Master reads the request and destination node information from the input files. However, you can override the node information:

To override the requesting and destination node information specified in the input files:

  1. Open an EIP Testing project.

  2. In the Input Information section, in the Optional Overrides section, enter a new requesting node name in the Requesting Node field.

  3. To override the destination node , in the Optional Overrides section, enter a new destination node name in the Destination Node field.

  4. Select File > Save Project.

To post the files in an EIP Testing project, open the project and click the Post button.

To view the output from EIP Testing projects, navigate to the output directory that you specified on the Headers tab in the Input Information section. You can also view output in Send Master in the Output Information section of the Project work space.

The Batch Project Executor enables you to use the functionality of the EIP Testing project type from a command line tool. This section discusses the Batch Project Executor tool, including its:

  • Usage.

  • Syntax.

  • Parameters.

Usage

The standard usage of the Batch Project Executor command line tool is:

BatchProjectExecutor [-options]

Syntax

The syntax for executing a batch project is:

BatchProjectExecutor -in "C:\temp\input" -out
"C:\temp\output" -url "http://localhost/PSIGW
/PeopleSoftListeningConnector" -result "C:\temp
\output\result.txt"

Parameters

The following table describes the parameters you can pass to the Batch Project Executor.

Parameter

Description

-in

Certification directory that contains the raw request files.

-out

Output directory to store all of the response files.

-url

Server URL to send all of the requests to during processing.

-result

Name of the file that will contain the results during batch execution. The contents of this file will be represented as XML.

-ow

(Optional.) Overwrite files if they already exist.

-cd

(Optional.) Create the output directory if not found.

-rn

(Optional.) Override the requesting node found in the IBInfo section.

-dn

(Optional.) Override the destination node found in the IBInfo section.

-? -help

(Optional.) Show the Help menu.

Sample Output

The following example shows successful output:

<?xml version="1.0"?>
<success>
    <request elapse="1.953 (s)" end="02:33:55.177" filename=
       "20030519T130405.request" id="" start="02:33:53.224" 
       success="true"/><request elapse="0.201 (s)" end="02:33:55.408" 
       filename="20030519T150417.request" id="" start="02:33:55.207" 
       success="true"/>
    <request elapse="0.220 (s)" end="02:33:55.638" filename="20030520T150406.
       request" id="" start="02:33:55.418" success="true"/>
    <request elapse="0.190 (s)" end="02:33:55.828" filename=
       "20030519T150406.request" id="" start="02:33:55.638" success="false">
       <![CDATA[Error communicating with server: Connection refused: connect]]>
    </request>
</success>

The following example shows a failure:

<?xml version="1.0"?>
<failure>
    <![CDATA[Error while initializing: Invalid output directory: 
    C:\temp\output]]>