Previous Topic: Configure DevTest to Use DB2Next Topic: Configure DevTest to Use Oracle


Configure DevTest to Use MySQL

This topic describes how to configure DevTest to use a MySQL database.

In the following procedure, you configure the MySQL version of the site.properties file. The following properties in this file are relevant to the database configuration:

lisadb.reporting.poolName=common
lisadb.vse.poolName=common
lisadb.acl.poolName=common
lisadb.broker.poolName=common
 
lisadb.pool.common.driverClass=com.mysql.jdbc.Driver
lisadb.pool.common.url=jdbc:mysql://DBHOST:DBPORT/DBNAME
lisadb.pool.common.user=database_username
lisadb.pool.common.password=database_password
 
lisadb.pool.common.minPoolSize=0
lisadb.pool.common.initialPoolSize=0
lisadb.pool.common.maxPoolSize=10
lisadb.pool.common.acquireIncrement=1
lisadb.pool.common.maxIdleTime=45
lisadb.pool.common.idleConnectionTestPeriod=5

To minimize the number of connections to the database, connection pooling is used. The underlying implementation of the pooling functionality is c3p0. For detailed information about the settings, see http://www.mchange.com/projects/c3p0/index.html#configuration_properties. By default, all the components use the common connection pool. However, you can define a separate pool for each component or mix and match.

The MySQL database must provide collation and characters set supporting UTF-8; double-byte characters are stored in the ACL and reporting tables. The default code page for the database has to be UTF-8; it is not enough only to define your database as UTF-8. If the MySQL database is not UTF-8, then runtime errors occur.

For the reporting database, we recommend at least 10 GB for optimal performance. A database for VSE is required only if you are working with legacy images created in a release earlier than 6.0.

The value of any property that ends with password is automatically encrypted at startup.

Note: The remote installations of DevTest Workstation, coordinator, simulator server, VSE, or any other remote DevTest component do not require more configuration. They all receive site.properties from the registry when they connect and configure their database access accordingly.

Follow these steps:

  1. In the LISA_HOME directory, locate the _site.properties file.
  2. Change the file name to site.properties.
  3. Open the site.properties file.
  4. Configure the database configuration properties.

    You typically update the following properties:

  5. The schema is automatically created in the database when the registry starts for the first time. However, if you do not want the DevTest user to have DBA privileges, you can manually create the schema beforehand. The mysql.ddl file in the LISA_HOME\database directory contains SQL statements that can serve as the basis for creating the reporting tables and indexes.
  6. Set the lisadb.internal.enabled property to false.
  7. Add the MySQL JDBC driver to both the LISA_HOME\lib\shared directory and the LISA_HOME\webserver\phoenix\phoenix-1.0.0\WEB-INF\lib directory. The minimum version of the MySQL JDBC driver is 5.1.25.

    Important! The JDBC driver must be added to both directories.

  8. Start the registry.