This topic describes how to configure DevTest to use an IBM DB2 database.
In the following procedure, you configure the DB2 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.ibm.db2.jcc.DB2Driver lisadb.pool.common.url=jdbc:db2://HOSTNAME:PORT/DATABASENAME 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.
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:
You typically update the following properties:
Important! The JDBC driver must be added to both directories.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|