Understanding Tools Used in Automated Integration Point Testing

PeopleSoft Integration Broker builds the following integration point test data repository structure during the export process.

You specify the top-level directory for the repository in the integration gateway properties file using the ig.EIPInputDirectory property.

Image: Integration point test data repository structure

This example shows the integration point test data repository structure that the system builds during the export process.

In a Microsoft Windows environment, each of the box in the previous diagram would correspond to folders in Microsoft Windows Explorer.

Image: Sample Repository Structure in Microsoft Windows Explorer

The following graphic shows what the structure might look like in Microsoft Windows Explorer using actual data.

When a synchronous request is received during testing, the gateway manager performs a lookup in the cached data gathered from the integration point test service operation transaction property file. If the system finds a match is found, the request XPaths are traversed to build the appropriate hash that can then be used to locate the corresponding response located within the integration point certification repository. The system loads the response file and passes it back to the requestor.

For asynchronous requests, the gateway manager generates an acknowledgement as the response and passes it back to the requestor.

In addition to returning the appropriate response files during outbound playback, the gateway manager logs request and response files. When the appropriate flag is set in the integration gateway properties file, the gateway manager logs the files into the defined output directory. Response and request file have the following naming convention.

<time stamp>.<request or response>

For example:

220030519T150406.832.request

The integration gateway properties file contains an EIPTestTool Properties section, in which you set the following information for integration point test automation:

Integration point test service operation transaction property files are XML files that contain synchronous integration point definitions broken down by product or sub-product. These files are used during message export and outbound playback.

One integration point test service operation transaction properties file must exist for each product line or sub-product.

Integration point testing metadata is not contained in a single file, because it does not scale well and because this information needs to be cached and accessed quickly.

Each integration point entry is keyed by requesting node, destination node, and service operation version.

You specify the location of the file in the integration gateway properties file using the ig.EIPMsgProp.N.propFile property.

The integration point test service operation transaction properties file contains the following properties for synchronous integration points:

• Requesting node.

• Destination node.

• Service operation name.

• XPaths to fields in the request to be used as the unique key.

  Leave this blank to use the entire contents as the hash key.

• Description.

The following example shows the contents of a sample integration point test service operation transaction properties file.

<?xml version="1.0"?>
<eips>
   <eip messagename="QE_SALES_ORDER_SYNC.VERSION_1" destinationnode="QE_LOCAL">
      <descr>
         <![CDATA[Outbound Synchronous QE_SALES_ORDER_SYNC from 
         QE_LOCALto QE_IBTGT]]>
      </descr>
      <xpath>
         MsgData/Transaction/QE_SALES_ORDER/QE_ACCT_ID
      </xpath>
   </eip>
</eips>

The Send Master utility features an EIP Testing (Batch EIP) project type that enables you to test batches of MIME messages from a directory, and also allows you to test different transaction values.

In addition to using the Send Master graphical user interface, you can also initiate automated testing through a Batch Project Executor command line tool.

The Message Export command line tool is a batch file that extracts transaction data from request and response data, and creates a hierarchical structure of source, service operation, and destination directories in the integration point test data repository.

The Message Export command line tool is located in the PeopleSoft web server domain: MessageExport.bat.

MessageExport [-options]

MessageExport -in "C:/temp/input" -out "C:/temp/output" -eip 
"c:\temp\eip\eip_prop\eip_crossnode_sync.xml" -result 
"C:/temp/output/result.txt"

<?xml version="1.0"?>
<success>
    <file path="C:\TEMP\eip\export_in\20051128T041615.545.request" 
      rawfilepath="C:\TEMP\eip\export_out\QE_LOCAL\QE_SALES_ORDER_SYNC.
      VERSION_1\V999\QE_IBTGT\20051128T041615.545_48.request" 
      success="true" transdatafilepath="C:\TEMP\eip\export_out\QE_LOCAL\
      QE_SALES_ORDER_SYNC.VERSION_1\V999\QE_IBTGT\request\1.xml"/>
    <file path="C:\TEMP\eip\export_in\20051128T041615.545.response" 
      rawfilepath="C:\TEMP\eip\export_out\QE_LOCAL\QE_SALES_ORDER_SYNC.
      VERSION_1\V999\QE_IBTGT\20051128T041615.545_48.response" 
      success="true" transdatafilepath="C:\TEMP\eip\export_out\QE_LOCAL\
      QE_SALES_ORDER_SYNC.VERSION_1\V999\QE_IBTGT\response\1.xml"/>
</success>

<?xml version="1.0"?>
<failure>
    <![CDATA[Invalid output directory: C:\Documents and Settings\Jfranco\
     Desktop\export]]>
</failure>

When you use the Message Export tool, PeopleSoft Integration Broker generates unique request and response pairs, and creates a unique hash key ID for the generated pair. The hash key is used by the integration gateway during playback to ensure that proper correlation occurs between the request and response files.

If you bypass the export process and manually add files for testing, or if you carry out testing when the target or source systems are not available to properly record information, you must generate a hash key. The Hash Key Generator is a command line tool that enables you to generate a hash key.

The Message Export command line tool is located in the PeopleSoft web server domain: HashKeyGenerator.bat.

HashKeyGenerator [-options]

HashKeyGenerator -in "C:\temp\input.txt

HashKeyGenerator  -v 214 "John Doe" PeopleSoft

HaskKeyGenerator -v Sally 1234 -t

A Node Map properties file is an XML file that enables you to associate renamed or custom node names with actual shipped application node names. This enables you to use unique node names during testing.

The system uses this file during outbound playback.

You create this file and specify the shipped application node names and all custom node names in use for a specific node. You must specify the file name and location in the integration gateway properties file, using the ig.EIPNodeMap property.

The following example shows a node map properties file.

<?xml version="1.0"?>
<nodemap>
    <map name="PSFT_HR"><node name="HRTST01"/><node name="HRTST02"/><node name="HRTST03"/>
    </map>
    <map name="PSFT_CRM">
        <node name="CRMTST01"/>
        <node name="CRMTST02"/>
        <node name="CRMTST03"/>
    </map>
</nodemap>

In the highlighted portion of the example, the map name PSFT_HR corresponds to a delivered application node. The node names HRTST01, HRTST02 and HRTST03 correspond to custom nodes names that are in use.