As of version 2.15, ApTest Manager supports the use of an optional SQL-based relational database management system (RDBMS) to capture information related to your Requirements, Test Cases, and Test execution. This optional functionality can be added to any Test Suite at any time. This section describes the supported RDBMS and methods for installing the necessary "drivers" to give your ApTest Manager server to access them.

This section assumes that your ApTest Manager environment AND your RDBMS environment are already configured and working. See the RDBMS documentation for details on installing and operating it. ApTest does not provide support in any way, shape or form for installation or operation of relational database management systems.

Once you have successfully executed the necessary steps in this section, you should see Chapter 4 of the Admin Guide for information on using the driver to connect ApTest Manager to your RDBMS.

Note that installation of RDBMS drivers is an advanced topic, and requires substantial knowledge of both the server on which ApTest Manager is installed and of the RDBMS to which you are connecting. The information in this section is as complete as we can make it, given that every environment is different.

Finally, note that if your favorite SQL RDBMS is not mentioned here, it may be possible for us to support it. Please contact atm-sales@aptest.com for more information and a price quote.

Table of Contents

1 Microsoft SQL Server

ApTest Manager has been tested and verified to work with Microsoft SQL Server 2005 R1. This version (or a later one) must be installed. We strongly suggest that a separate database be created just for ApTest Manager, and that a separate user be defined to access and maintain this database. Your Microsoft SQL Server Database Administrator will know how to do this.

In order to configure ApTest Manager to talk to Microsoft SQL Server, you will need to install the Perl module DBD-ODBC (version 1.13 or later). If you are using Strawberry Perl, this driver is already included. If you are using ActivePerl, from a Windows command shell, perform the following:

C:\Documents and Settings\Administrator>  ppm install DBD-ODBC

This will retrieve the latest version of the ODBC module and install it on your system.

You will also need to set up a DSN on your system. This is a Windows Administrative task, and is outside the scope of these instructions. It is highly dependent on where and how your SQL Server is configured. In general, the DSN should be defined as a "System DSN". Define it according to the instructions from your Microsoft SQL Server Database Administrator, and remember the name - you will need it when you configure the connection in ApTest Manager.

Finally, follow the instructions in Chapter 4 of the Admin Guide to configure access to your newly defined "System DSN" using the "MS SQL Server (ODBC)" Database type. You will need to provide the DSN, the username, and the password.

2 MySQL

ApTest Manager has been tested and verified to work with MySQL version 3.23. This version (or a later one) must be installed. We strongly suggest that a separate database be created just for ApTest Manager, and that a separate user be defined to access and maintain this database. Your MySQL Database Administrator will know how to do this.

In order to configure ApTest Manager to talk to MySQL you will need to install the Perl module DBD-mysql (version 4.001 or later). If you are using Strawberry Perl, the MySQL driver is already installed. If you are using ActivePerl, from a Windows command shell, perform the following:

C:\Documents and Settings\Administrator>  ppm install http://theoryx5.uwinnipeg.ca/ppms/DBD-mysql.ppd

This will retrieve the latest version of the MySQL driver module and install it on your system.

Finally, follow the instructions in Chapter 4 of the Admin Guide to configure access to your MySQL RDBMS database using the "MySQL" Database type. You will need to provide the hostname, port number, the username, and the password.

3 Oracle

ApTest Manager has been tested and verified to work with Oracle version 10g. This version (or a later one) must be installed. We strongly suggest that a separate database be created just for ApTest Manager, and that a separate user be defined to access and maintain this database. Your Oracle Database Administrator will know how to do this.

In order to configure ApTest Manager to talk to Oracle you will need to install the Perl module DBD-Oracle (version 1.17 or later). If you are using ActivePerl 5.8, from a Windows command shell, perform the following:

C:\Documents and Settings\Administrator>  ppm install DBD-Oracle

This will retrieve the latest version of the Oracle driver and install it on your system.

If you are using Strawberry Perl, follow the instructions here.

Finally, follow the instructions in Chapter 4 of the Admin Guide to configure access to your Oracle RDBMS using the "Oracle" Database type. You will need to provide the hostname, the port, the system identifier, the username, and the password.

4 PostgreSQL

ApTest Manager has been tested and verified to work with PostgreSQL version 7.4.13. This version (or a later one) must be installed. We strongly suggest that a separate database be created just for ApTest Manager, and that a separate user be defined to access and maintain this database. Your PostgreSQL Database Administrator will know how to do this.

In order to configure ApTest Manager to talk to PostgreSQL you will need to install the Perl module DBD-Pg (version 1.49 or later). If you are using Strawberry Perl, this driver is already included. If you are using ActivePerl 5.8, from a Windows command shell, perform the following:

C:\Documents and Settings\Administrator>  ppm install src\DBD-Pg-5.8.ppd

This will retrieve the latest version of the Pg driver and install it on your system.

Finally, follow the instructions in Chapter 4 of the Admin Guide to configure access to your PostgreSQL RDBMS using the "PostgreSQL" Database type. You will need to provide the database name, the hostname, the port, the username, and the password.

Copyright © 2000-2015 Applied Testing and Technology, Inc. All rights reserved.