Validating CONNECT Installation

Owned by Tran Tang (Unlicensed)
Last updated: Jul 23, 2019

CONNECT ValidationSuite Tests

After the CONNECT Gateway has been installed, the Validation Suite can be used to verify that the installation is working correctly. The Validation Suite will detect if the gateway is in standard or passthrough processing mode and adjust tests accordingly. Currently, Patient Discovery and Document Query function slightly differently between standard and passthrough.

Running the Validation Suite from the source code requires that the source code has been built, as this process copies WSDL and Schema files to the correct location.

Locating Validation Suite Tests

The Validation Suite is included in the CONNECT Source as well as the CONNECT binary. In the source they can be found at <CONNECT_SOURCE_DIR>/Product/SoapUI_Test/ValidationSuite/ConnectValidation-soapui-project.xml

Executing Validation Suite Tests

The Validation Suite can be run via Maven or SoapUI. To run them via Maven, please refer to the README in the top level of the CONNECT source and to the Maven notes. To run the Validation Suite via the SoapUI, simply load the Validation Suite into SoapUI, set the project variable GatewayPropDir to the location of the gateway configuration (this directory contains gateway.properties, exchangeInfo.xml, internalExchangeInfo.xml, etc.), and run the test suite.

Important note regarding UDDIConnectionInfo.xml and internalConnectionInfo.xml

As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For users of CONNECT 5.0 and earlier versions, substitute references to these new files with the original exchangeInfo.xml and internalExchangeInfo.xml files

Installing SoapUI (optional)

A separate installation of SoapUI is required only if the Validation Suite will be run in the SoapUI. Running the Validation Suite via Maven does NOT require a SoapUI installation.

Config SoapUI for Development

to disable the soapui-project:definitionCache from being add to the project every time it ran

  • File > Preferences > WSDL-settings
  • disable: "Cache-WSDLs"

when installing the new-soapui-app, the following jar are required for the soapui validation suite.

  • fileutil.jar
  • mysql-connector-java-jar

Troubleshooting


SoapUI Does Not Start

If SoapUI will not start, which has been observed on some Linux and Solaris systems, uncomment the following line in the SoapUI startup script:

-Dsoapui.jxbrowser.disable=true


Error: "No Suitable Driver Found"

If SoapUI throws an error similar to "An error occurred [No suitable driver found for jdbc:mysql://localhost:3306/patientcorrelationdb], see error log for details.", add the following line to the top of the setup scripts for g0 and g1:

com.eviware.soapui.support.GroovyUtils.registerJdbcDriver( "com.mysql.jdbc.Driver" )

Failing tests with error: "groovy.lang.MissingPropertyException: No such property: nhinc for class"

Copy FileUtils.jar from CONNECT binary to SoapUI lib folder.