Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Section
Column

Start your servlet container. If you are using the tomcat bundle double click <frevvo-home>\start-frevvo. This will start the database connector web application. Access the connector by typing one of the test Urls below directly in your browser.

Column
width240px

On this page:

Table of Contents
maxLevel1

If you are using the v2.3 database connector you can quickly verify proper installation using the built-in status service by putting this URL into your browser: http://localhost:8082/database/status. Change localhost and port 8082 to the host and port where you installed the connector.If you are using the v2.3 database connector you can quickly verify proper installation by putting this URL into your browser: http://localhost:8082/database/status. Change localhost and port 8082 to the host and port where you installed the connector.

If you are using the v2.2 database connector you can verify the installation using one of the pre-configured SQL queries. 

The database connector comes with a built-in hsqldb database for testing purposes. And the database connector's configuration.xml comes pre-configured with a few sample SQL queries. If you installed database.jar under the  tomcat bundle, run the following test queries. This will retrieve data from the built-in database:

...

The solution is to stop and restart the database connector. If you are using the  tomcat bundle you can do this by: Double click <frevvo-home>\stop-frevvo. Wait until  stops. Then Double click <frevvo-home>\start-frevvo

The query returns old results after you update the SQL in configuration.xml

It is very helpful to first test your queries by entering the query URL directly into your web browser and verify that the data resultset returned to your browser as a web page is as you expect. Note however that browsers often cache web pages. If you edit your configuration.xml SQL query and reload/refresh the URL in your browser you may NOT get the updated results due to your browser's caching. Avoid this caching issue by always opening a new browser tab to retest an updated query.