The properties in site.properties are sent from the registry to any DevTest application or service that connects to it. These properties take precedence over any properties that are defined locally in lisa.properties. However, these properties do not take precedence over the properties that are defined in local.properties or defined on the command line using -D command-line option.
DevTest Enterprise Dashboard Properties
Designates the Service URL to use for sending component and metric information to the DevTest Enterprise Dashboard.
Important! The Enterprise Dashboard database is not able to reside in the same database schema as a registry database. Because the site.properties is handled solely by a registry process, a custom Enterprise Dashboard database will need to be configured in the local.properties file. For more details on configuration of the Enterprise Dashboard database, look at the _local.properties template in the home directory of your DevTest installation.
Database Properties
These are the default properties used by DevTest to connect to the registry database.
Derby is not supported in a distributed environment. You must use an enterprise database in a distributed environment.
The following components interact with a database: reporting, VSE, ACL, and the broker. By default, these components use the common connection pool. However, you can define a separate pool for each or mix and match. To define a new connection pool, add properties such as lisadb.pool.newpool.url. The underlying pool implementation is the open source c3p0 pool. DevTest passes the various properties down. For information about the c3p0 settings that you can select from, see http://www.mchange.com/projects/c3p0/index.html#configuration_properties.
Default: common
Default: common
Default: common
Default: common
The following pool properties keep the number of connections to a minimum when DevTest is idle.
Default: 0
Default: 0
Default: 10
Default: 1
Default: 45
Default: 5
Should the internal Derby database instance in the registry be started?
Controls whether the registry starts an internal Derby database. If you configured all the previous components to use an external database, you can save resources by setting this property to false.
Default: true
Oracle Properties
Default: oracle.jdbc.driver.OracleDriver
Default: jdbc:oracle:thin:@[HOST]:1521:[SID]
Default: none
Default: none
MS SQL Server Properties
Default: com.microsoft.sqlserver.jdbc.SQLServerDriver
Default: jdbc:sqlserver://[SERVER]:[PORT];databaseName=[DATABASENAME]
Default: none
Default: none
DB2 Properties
Default: com.ibm.db2.jcc.DB2Driver
Default: jdbc:db2://[HOSTNAME]:[PORT]/[DATABASENAME]
Default: none
Default: none
MySql Properties
Default: com.mysql.jdbc.Driver
Default: jdbc:mysql://[DBHOST]:[DBPORT]/[DBNAME]
Default: none
Default: none
Derby Properties
Default: org.apache.derby.jdbc.ClientDriver
Default: jdbc:derby://[SERVER]:[PORT]/[DATABASE];create=true
Default: none
Default: none
Miscellaneous Properties
Default: true
lisa.dcm.labstartup.min=6
lisa.dcm.lisastartup.min=4
lisa.dcm.lisashutdown.min=2
lisa.dcm.lab.cache.sec=<180 default>
lisa.dcm.lab.factories=com.itko.lisa.cloud.serviceMesh.ServiceMeshCloudSupport;com.itko.lisa.cloud.vCloud.vCloudDirectorCloudSupport;;
lisa.dcm.SERVICEMESH.baseUri=<url>
lisa.dcm.SERVICEMESH.userId=<userId>
lisa.dcm.SERVICEMESH.password=<password>
lisa.dcm.vCLOUD.baseUri=<https://<fqdn>/api/versions>
lisa.dcm.vCLOUD.userId=<userId>
lisa.dcm.vCLOUD.password=<password>
lisa.net.timeout.ms=60000
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|