Configuring the project results database

Historical test data and performance results from agents and probes are stored in the IBM® DevOps Test Integrations and APIs (Test Integrations and APIs) project results database. It is difficult to estimate the space that is required as the number and type of tests to be run varies. For example, lengthy performance tests can generate large amounts of data. When you create the project results database, 50GB is probably a good starting point.

The supported databases that can be configured and used as the project results database are:
  • IBM Db2®
  • Oracle
  • Microsoft™ SQL Server
  • MySQL

For information about the supported versions of the database, see the Supported Software > Database section in Supported software

Note:
Multiple projects can reside in the same database schema without impacting one another since the projects (and their artifacts) have unique keys.

After you install Test Integrations and APIs, you can create the project results database in an existing, empty, and supported database. The required IBM Db2 and the Oracle JDBC drivers are installed with Test Integrations and APIs, and connectivity is established later from all clients, including agents and probes.

Note:
Some databases require that you configure JAR files in the database (JDBC) section of Library Manager. In addition, if you plan to view the project results database in IBM DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), copy the JAR files to the lib folder of the Test Virtualization Control Panel installation directory (for example, C:\Program Files\IBM\DevOpsTestControlPanel\usr\servers\defaultServer\apps\RTCP.war\WEB-INF\lib).

The database creation scripts can be found in the scripts folder of the Test Integrations and APIs installation directory (for example, C:\Program Files\IBM\DevOpsTestAPI\scripts).

A script is provided for some of the supported database providers:

  • IBM Db2: ghtester_db2.sql
  • Oracle: ghtester_oracle.sql
  • Microsoft SQL Server: ghtester_mssql.sql
  • MySQL: ghtester_mysql.sql

The appropriate script can be run against an empty database by a database administrator.

If you are a user of a project results database that is created by someone else, you must have the following permissions to work with the database:
  • INSERT, UPDATE, DELETE, SELECT on all the Test Integrations and APIs tables
  • EXECUTE PROCEDURE
  • SELECT SEQUENCE on the Test Integrations and APIs sequences for the Oracle databases
Note:
To ensure that the Test Integrations and APIs results database handles Unicode characters correctly, it must be configured to use UTF-8. Details on how to do this are included in the instructions on creating the results database for each database provider.

For managing test cycles, you must configure a project results database. For details on test cycles, see Test cycles overview and management.