Differences
This shows you the differences between two versions of the page.
| jdbc_addon [2017/12/18 03:46] – created admin | jdbc_addon [2017/12/18 03:48] (current) – removed admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | If your requirements system allows access through JDBC or ODBC, you can set up **TestOptimal** to retrieve the requirements for the tags using JDBC. | ||
| - | The configuration is just one setting entry to " | ||
| - | |||
| - | tagUri=sql: | ||
| - | |||
| - | Replace sqlStatement with the sql statement used to retrieve all requirement tags from your requirement system database. Use " | ||
| - | |||
| - | SELECT requirement_id, | ||
| - | |||
| - | The select must return at least two columns with first column for requirement id (tag) and the second column for the requirement description. Both columns are text columns. | ||
| - | |||
| - | For ODBC data source, you will require additional step to [[Access CSV File|set up ODBC data source]] using Windows ODBC Data Source control panel. | ||
| - | |||
| - | If you are using jdbc driver to access to your sql database, you will need to determine the jdbc driver classs name and appropriate connection string which usually contains your sql database name. For more information on deterining the appropriate jdbc driver class name and connection string for your sql database, check out [[http:// | ||
| - | |||
| - | The final step is to ensure the jdbc driver (jar file) is copied to /lib/ folder under TestOptimal home directory. You will need to restart the server to make the changes effective. | ||