Integration Point Test Service Operation Transaction Properties File

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.

Note:

Integration point test service operation transaction properties files are required for synchronous service operation transactions only.

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>