Playing Back Service Operation Transactions

To perform inbound playback:

1. In the EIPTestTool properties section of the integration gateway properties file, set the gateway manager class to EIP Gateway Manager. To do so, remove the comment from the following line:

   ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.
   EIPTestToolGatewayManager
   

2. Purge all service operation transaction data in the system or the data that is specific to the integration point test.

3. Create and run a Send Master project of type EIP Testing (EIP Batch) for each service operation transaction type that you want to test.

4. Run the message export process on the response directory populated during testing.

5. Compare the transaction data returned by the export process to the data that is stored in the integration point test data repository.

To perform outbound playback:

1. Set the following properties in the EIPTestTool Properties section in the integration gateway properties file:

   1. Set the gateway manager class to EIP Gateway Manager: to do so, remove the comment from the following line:

      ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.
      EIPTestToolGatewayManager
      

   2. Set loop back to True; to do so, remove the comment from the following line:

      ig.EIPLoopBack=True

      Change the parameter value to True, if necessary.

   3. Set the location of the input file directory; to do so, remove the comment from the following line and set the value equal to the location of the directory.

      ig.EIPInputDirectory=

   4. (Optional.) Set the log output directory; to do so, remove the comment from the following line:

      ig.EIPOutputDirectory=c:/temp/output

      You can change the directory location as appropriate.

   5. For synchronous service operation transactions, define the number of integration point test service operation transaction properties in use for the test, and specify the necessary number of entries for the integration point test service operation transaction properties file; to do so, remove the comment from the following line:

      ig.EIPMsgProp.count

      Set this property equal to the number of integration point test service operation transaction properties files in use for the test. For example:

      ig.EIPMsgProp.count=1

      You must also specify the location of the integration point test service operation transaction properties files for each file directory in use for testing. The number of files that you specify should equal the value that you specified for the ig.EIPMsgProp.count property.

      To specify the integration point test service operation transaction files for the test, remove the comment from the following line:

      ig.EIPMsgPropN.propFile

      Enter the name and location of each integration point test service operation transaction properties file in use for the test.

      For example:

      ig.EIPMsgProp1.propFile=c:\temp\File_1.xml
      

2. Launch the necessary processes on the source system to invoke integration points with the target system.

3. Run the message export process on the log output directory used during testing to pull back the transaction data for use in data comparison.

4. View the integration gateway logs or Service Operations Monitor to verify that the inbound requests are valid and that PeopleSoft Integration Broker sends the proper responses from the repository.

5. Compare the transaction data returned by the export process to the data that is stored in the integration point test data repository to view expected versus actual results.

   You can accomplish this by manually reviewing the database tables or by using an automated database table compare tool.