Getting started

Prerequisite

• Java Web Application Server (e.g. Apache/Tomcat, JBoss, Jetty, ...) For the moment, this library has been fully tested only with Tomcat.
• Database
• JDBC driver corresponding to the used DBMS
• File directory in which all TAP files are going to be stored (e.g. logs, backups, uploads, results, error stacks)
• (optional) Connection pool library

Use case

Let's suppose we have a PostgreSQL database named MyStarCatalogues containing several astronomical data. Among all these data we want to publish in a TAP service only one table called SuperCat (in the database schema public).

Using this TAP library, we should first fulfil the above prerequisites:

• Web Application Server? Apache Tomcat
• Database? a PostgreSQL database called MyStarCatalogues.
• JDBC driver? org.postgresql.Driver (can be found here)
• File directory? file:///somewhere/TAPFiles.
• (optional) Connection pool library? the Apache Tomcat embedded connection pool.

Goal

In both of the above methods, the goal will be to set a TAP service having the following specification:

• 4 output formats: VOTable (binary), VOTable (TableData), FITS and CSV.
• UPLOAD ability
• Simple coordinate system verification (only ICRS coordinates must be allowed)
• All ADQL geometries (depending of your DBMS and its extension(s))
• 4 common simple user defined functions (random, rtrim, rpad, initcap)