Testing Connectivity - trillium_quality - 17.2

Trillium TS Web Services Developer Guide

Product type
Software
Product family
Trillium
Product
Trillium > Trillium Quality
Version
17.2
Language
English
Product name
Trillium Quality
Title
Trillium TS Web Services Developer Guide
Topic type
Overview
Installation
How Do I
Configuration
Administration
Reference
First publish date
2008

There are several methods for testing connectivity.

The easiest method is to issue a Ping request, for example, http://localhost:8484/TrilliumSOAP/services/TrilliumSOAP/Ping, which returns the current date and time from the server. Ping verifies connectivity but does not perform any work using the underlying Trillium software.

A second method is to create a simple HTML file in tomcat’s ROOT folder (by default, C:\Program Files\Trillium Software\MBSW\17\tsq\Software\apache-tomcat\webapps\ROOT). Browse to that file (for example, http://localhost:8484/hello.html) and check the response. Again, this does not test underlying Trillium software.

A third method is to test both Tomcat and Trillium components by issuing a test cleanse request, for example:

http://localhost:8484/TrilliumSOAP/services/TrilliumSOAP/RESTCleanseANSI?
webKey=TRILLIUM&projectName=CRM&inputFields=TRILLIUM_ADDR_LINE1&
inputFields=TRILLIUM_CITY&inputFields=TRILLIUM_STATEORPROVINCE&
inputFields=TRILLIUM_COUNTRY&inputValues=300%20Concord&
inputValues=billerica&inputValues=ma&inputValues=usa&
outputFields=DR_POSTAL_CODE&outputFields =POSTAL_MATCH_LEVEL_TEXT&
outputFields=TS_MATCH_LEVEL</filepath>