search cancel

DevTest Upgrade to having Different Database Pool

book

Article ID: 203054

calendar_today

Updated On:

Products

CA Application Test Service Virtualization

Issue/Introduction

 
 
 

Upgraded DevTest.

Below is the database configuration as of previous release. 

Have different database pool configured for each components in site.properties file. As part of the upgrade, would like to consolidate/normalize with standard database configuration comes with DevTest, but still keep the old previous release.

Can this be done?

The site.properties file

lisadb.acl.poolName=aclreg
lisadb.broker.poolName=brokerpathfinder
lisadb.reporting.poolName=reporting
lisadb.dradiscache.poolName=enterprisedashboard

## ==================================================================================
## Enterprise Dashboard database properties 
## ==================================================================================

lisadb.pool.enterprisedashboard.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
lisadb.pool.enterprisedashboard.url=jdbc:sqlserver://<hostname:port>;databaseName=LISA_EDashboard
lisadb.pool.enterprisedashboard.user=<username>
lisadb.pool.enterprisedashboard.password_enc=<pwd>

## ==================================================================================
## ACL/Registry database properties 
## ==================================================================================
lisadb.pool.aclreg.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
lisadb.pool.aclreg.url=jdbc:sqlserver://<hostname:port>;databaseName=LISA_1_REG
lisadb.pool.aclreg.user=<username>
lisadb.pool.aclreg.password_enc=<pwd>

## ==================================================================================
## Broker/Pathfinder database properties 
## ==================================================================================
lisadb.pool.brokerpathfinder.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
lisadb.pool.brokerpathfinder.url=jdbc:sqlserver://<hostname:port>;databaseName=LISA_1_PF
lisadb.pool.brokerpathfinder.user=<username>
lisadb.pool.brokerpathfinder.password_enc=<pwd>

## ==================================================================================
## Reporting database properties 
## ==================================================================================
lisadb.pool.reporting.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
lisadb.pool.reporting.url=jdbc:sqlserver://<hostname:port>;databaseName=LISA_1_Reporting
lisadb.pool.reporting.user=<username>
lisadb.pool.reporting.password_enc=<pwd>


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

 

Environment

All supported DevTest releases.

Cause

N/A

Resolution

Confirmed with development this plan for the upgrade will work:

1. The Audit information is in the Enterprise Dashboard database, so will not need to start with a fresh database and just upgrade that schema. Backup the Enterprise Database before the upgrade.

2. In the site.properties file, have all the pools be with a name of common, so all the tables, including DRADISCACHE, all are in one Registry database.

lisadb.acl.poolName=common
lisadb.broker.poolName=common
lisadb.reporting.poolName=common
lisadb.dradiscache.poolName=common

3. You can then drop the DRADISCACHE table from the upgraded Enterprise Database.

Additional Information

The DRADISCACHE is a table that is associated with the Registry.  Not the Enterprise Dashboard.  If the Enterprise Dashboard was to go down for any reason, the Registry and other components would not go down.  All the metrics being gathered get stored in the DRADISCACHE table and then when the Enterprise Dashboard comes up, the Registry sends all the metrics stored in the DRADISCACHE table and then the table is emptied.  But if the Enterprise Dashboard database were to go down, this would be an issue.