Test Integration Modules (Optional) - IAConnect - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

IAConnect
Platform
OnBase
Product
IAConnect
Release
Foundation 23.1
License

This is not required step in the process. It is typically run to diagnose issues that occur during a new installation. To run this test, at least one posting of a voucher must have been attempted from IAConnect. This posting attempt could be either successful or failed; the test works either way. When IAConnect makes a voucher posting attempt, it creates a posting sample record inside the log file that can then be used in this test interface.

  1. Edit the Web.config log file verbosity setting to level 4 and save the file.
  2. Start the Costpoint Integration Console at Start | Costpoint 7.0.x | Start Costpoint 7.0.x Integration Console.
  3. Select Test Integration Modules (Web Services/EJB) from the available options and click Next.
  4. Select the process file you want to test (the AP Preprocessor file or the PO Preprocessor file) and click Test.
  5. The parameters dialog box is displayed. Leave all default field entries on this form except for the User and Password fields. Enter a valid Costpoint user ID and password as described in Costpoint Connection Settings.
  6. Click the View/Edit button next to the Document field. The Method Editor is displayed. Leave that dialog box open and proceed to the next step.
  7. Once a posting has been attempted from IAConnect with either the PO or AP Voucher process and the log file has been set to a loglevel=4, there is a log file that contains data you'll need to copy and paste into the Method Editor dialog. Navigate to this file, CostpointWCFService.xml.log, which is located in the directory C:\Reports on the web server on which IAConnect has been installed.
  8. Open the CostpointWCFService.xml.log log file. Select and copy the section that begins with <?xml version='1.0' encoding='UTF-8'?> and ends with </appreproc>.
  9. Paste the text into the Method Editor. Click Validate Schema to ensure the file format is correct.
  10. Click OK. This returns you to the parameters dialog box.
  11. Click Test to submit the XML file to the CIS web service. The test produces any Costpoint errors if they are encountered.
    Note:

    This process is not just a false test; it posts the actual transaction to Costpoint if successful.

  12. The Testing process dialog box is displayed and shows the progress of the test. Once the process is complete, the results of the test allow you to diagnose the issue more clearly. If you get a severity 3 error or above, the record did not post to Costpoint successfully. If you get a severity 1 or 2 error, the record did get posted but something happened that you need to look into further.
  13. Be sure to change the loglevel in the Web.config file back to 1 when testing is complete.