Service Virtualization

  • 1.  Some components are configured with non-production database (Derby).

    Posted Sep 28, 2017 01:31 AM

    Why poratl will suggest that some components use derbys database, I have to configure two oracle examples used to save the data:

    ps: Attachments are screenshots

    dradis.properties:

    ################################################################################
    ### dradis.properties                                                        ###
    ###                                                                          ###
    ### This file contains default values for properties used by DevTest         ###
    ### Enterprise Dashboard                                                     ###
    ################################################################################

    ## Our embedded web server
    dradis.webserver.port=1506

    ## Our embedded web server's host. '0.0.0.0' will bind to all local addresses.
    dradis.webserver.host=0.0.0.0


    ## enable https and setup the webserver ssl keystore
    #dradis.webserver.https.enabled=true
    #dradis.webserver.ssl.keystore.location={{DRADIS_HOME}}webserver.ks
    #dradis.webserver.ssl.keystore.password=yourpassword
    #dradis.webserver.ssl.keymanager.password=yourpassword

    #####################################################################################
    ##   
    ## NOTES ABOUT ENTERPRISE DASHBOARD Database
    ##
    ##  The Enterprise Dashboard database is used for the DevTest Solutions
    ##  Usage Audit Report data, registry status and component information,
    ##  historical event logs, and historical component metrics.
    ##
    ##  Note: Enterprise Dashboard requires its own large database. The database
    ##        can reside on a different system and must have at least 50 GB of
    ##        storage.
    ##
    ##  Derby is NOT supported in a Distributed Environment. Users must use an
    ##  enterprise database in a Distributed Environment.
    ##
    ##  To set up a custom Enterprise Dashboard database, you will need to
    ##  configure it here, since the Enterprise Dashboard database cannot use the
    ##  same database as the Registry.
    ##
    #####################################################################################

    ## Should we start the internal Derby DB instance in the Enterprise Dashboard?
    dradis.db.internal.enabled=true

    ## Internal Derby DB network interface to use (0.0.0.0 == all network interfaces)
    #dradis.db.internal.host=0.0.0.0

    ## Internal Derby DB port number to use
    #dradis.db.internal.port=1530
    #dradis.db.internal.start.retries=3
    #dradis.db.internal.start.delay=5000

    ## alternative database connection string templates
    ##
    ## ==================================================================================
    ## Oracle
    ## ==================================================================================
    ## dradis.db.driverClass=oracle.jdbc.driver.OracleDriver
    ## dradis.db.url=jdbc:oracle:thin:@[HOST]:1521:[SID]
    ## dradis.db.user=[USER]
    ## dradis.db.password=[PASSWORD]
     dradis.db.driverClass=oracle.jdbc.driver.OracleDriver
     dradis.db.url=jdbc:oracle:thin:@localhost:9000:dradis
     dradis.db.user=dradis
     dradis.db.password={cry}4bda715adaa24468265c9e885e645855
    ##
    ## ==================================================================================
    ## MS SQL Server
    ## ==================================================================================
    ## dradis.db.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
    ## dradis.db.url=jdbc:sqlserver://[SERVER]:[PORT];databaseName=[DATABASENAME]
    ## dradis.db.user=[USER]
    ## dradis.db.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## DB2
    ## ==================================================================================
    ## dradis.db.driverClass=com.ibm.db2.jcc.DB2Driver
    ## dradis.db.url=jdbc:db2://[HOSTNAME]:[PORT]/[DATABASENAME]
    ## dradis.db.user=[USER]
    ## dradis.db.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## MySql
    ## ==================================================================================
    ## dradis.db.driverClass=com.mysql.jdbc.Driver
    ## dradis.db.url=jdbc:mysql://[DBHOST]:[DBPORT]/[DBNAME]
    ## dradis.db.user=[USER]
    ## dradis.db.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## Derby
    ## ==================================================================================
    ## dradis.db.driverClass=org.apache.derby.jdbc.ClientDriver
    ## dradis.db.url=jdbc:derby://[SERVER]:[PORT]/[DATABASE];create=true
    ## dradis.db.user=[USER]
    ## dradis.db.password=[PASSWORD]
    ##
    #####################################################################################

    site.properties:

    #####################################################################################
    ### TEMPLATE SITE PROPERTIES (site.properties)                                    ###
    ###                                                                               ###
    ### This template may be used to create a site.properties file.                   ###
    ###                                                                               ###
    ### The properties in this file will override any properties that are defined in  ###
    ### lisa.properties.                                                              ###
    ###                                                                               ###
    ### WARNING: lisa.properties should not be modified as it may be overwritten at   ###
    ###          any time                                                             ###
    ###                                                                               ###
    #####################################################################################
    ###                                                                               ###
    ### The properties in site.properties will be sent from the Registry to any       ###
    ### DevTest Application or service that connects to it.  These properties take    ###
    ### precedence over any properties defined locally in lisa.properties. However,   ###
    ### these properties do not take precedence over properties defined locally in    ###
    ### local.properties or defined on the command line using the '-D' command line   ###
    ### option.                                                                       ###
    ###                                                                               ###
    #####################################################################################

     

    #####################################################################################
    ###
    ### SECTION 1 -  ENTERPRISE DASHBOARD
    ###
    #####################################################################################
    ## ==============================================
    ## DevTest Enterprise Dashboard
    ##  This is the Service URL to use for sending component and metric information
    ##  to the DevTest Enterprise Dashboard
    ## ==============================================
    devtest.enterprisedashboard.host=localhost
    devtest.enterprisedashboard.port=1506
    #devtest.enterprisedashboard.https.enabled=true
    ##
    ##
    ## IMPORTANT - The Enterprise Dashboard database is not able to reside in the same
    ## database schema as a Registry database. Since the site.properties is handled solely
    ## by a registry process, a custom Enterprise Dashboard database will need to be
    ## configured in the dradis.properties file. For more details on configuration of the
    ## Enterprise Dashboard database, please look at the _dradis.properties template in
    ## the home directory of your DevTest install
    ##
    #####################################################################################

    #####################################################################################
    ###
    ### SECTION 2  - Database
    ###
    #####################################################################################
    ##
    ## These are the default properties used by DevTest to connect to the default
    ## internal Derby database.
    ##
    ## Derby is NOT supported in a Distributed Environment. Users must use an
    ## enterprise database in a Distributed Environment
    ##
    #####################################################################################
    ##
    ## The following components interact with a database:
    ##
    ##   ACL, Reporting, VSE, and 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
    ## will pass the various properties down.  For information about the c3p0
    ## settings that you can choose from, see:
    ##   http://www.mchange.com/projects/c3p0/index.html#configuration_properties.
    ##
    #####################################################################################
    ##
    ## alternative database connection string templates

    ## ==================================================================================
    ## Pools
    ## ==================================================================================
    lisadb.acl.poolName=common
    lisadb.broker.poolName=common
    lisadb.reporting.poolName=common
    lisadb.dradiscache.poolName=common
    lisadb.vse.poolName=common


    ## ==================================================================================
    ## Set the password by removing the trailing _enc from the property name
    ## and adding =MyPlaintextPassword.  DevTest automatically encodes the password
    ## for you at startup.
    ## =================================================================

    ##
    ## ==================================================================================
    ## Oracle
    ## ==================================================================================
    ## lisadb.pool.common.driverClass=oracle.jdbc.driver.OracleDriver
    ## Select one of the two connection URLs depending on usage of SID or SERVICE
    ## lisadb.pool.common.url=jdbc:oracle:thin:@[HOST]:1521:[SID]
    ## lisadb.pool.common.url=jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE
    ## lisadb.pool.common.user=[USER]
    ## lisadb.pool.common.password=[PASSWORD]
    lisadb.pool.common.driverClass=oracle.jdbc.driver.OracleDriver
    ## Select one of the two connection URLs depending on usage of SID or SERVICE
     lisadb.pool.common.url=jdbc:oracle:thin:@localhost:9000:dbcomponent
    ## lisadb.pool.common.url=jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE
     lisadb.pool.common.user=component
    lisadb.pool.common.password_enc=lfb7f6e01aada1613b1ec39166621439547bb6f0af9889cb03d0af0a6a072acbdc247a968caae
    ##
    ##
    ## ==================================================================================
    ## MS SQL Server
    ## ==================================================================================
    ## lisadb.pool.common.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
    ## lisadb.pool.common.url=jdbc:sqlserver://[SERVER]:[PORT];databaseName=[DATABASENAME]
    ## lisadb.pool.common.user=[USER]
    ## lisadb.pool.common.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## DB2
    ## ==================================================================================
    ## lisadb.pool.common.driverClass=com.ibm.db2.jcc.DB2Driver
    ## lisadb.pool.common.url=jdbc:db2://[HOSTNAME]:[PORT]/[DATABASENAME]:progressiveStreaming=2;
    ## lisadb.pool.common.user=[USER] 
    ## lisadb.pool.common.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## MySql
    ## ==================================================================================
    ## lisadb.pool.common.driverClass=com.mysql.jdbc.Driver
    ## lisadb.pool.common.url=jdbc:mysql://[DBHOST]:[DBPORT]/[DBNAME]
    ## lisadb.pool.common.user=[USER]
    ## lisadb.pool.common.password=[PASSWORD]
    ##
    ## ==================================================================================
    ## Derby
    ## ==================================================================================
    ## lisadb.pool.common.driverClass=org.apache.derby.jdbc.ClientDriver
    ## lisadb.pool.common.url=jdbc:derby://[SERVER]:[PORT]/[DATABASE];create=true
    ## lisadb.pool.common.user=[USER]
    ## lisadb.pool.common.password=[PASSWORD]
    ##
    #####################################################################################

    ## ==================================================================================
    ## Default pool properties to keep the number of connections to a minimum if we are idle.
    ## ==================================================================================
    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

    ## ==================================================================================
    ## Should the internal Derby DB instance in the Registry be started?
    ## ==================================================================================
    #lisadb.internal.enabled=true
    lisadb.internal.enabled=false

    #####################################################################################
    ###
    ### SECTION 3 - MISC SETTINGS
    ###
    #####################################################################################

    ## ==================================================================================
    ## If you're not using Pathfinder, you can disable it by setting this property to false.
    ## ==================================================================================
    #lisa.pathfinder.on=true


    ## ==================================================================================
    ## DCM Settings
    ## ==================================================================================

    ## ==================================================================================
    ## The timeout value (in milliseconds) used by the underlying messaging system. You should modify the value for
    ## cloud integration because certain operations can take longer than the default 30 seconds.
    ## ==================================================================================
    #lisa.net.timeout.ms=60000

    ##==================================================
    ## Rally report parameters.
    ##==================================================
    ##rally.api.url=https://rally1.rallydev.com/slm/webservice/v2.0/
    ##rally.api.key=

    ##==================================================
    ## URL used in Rally Report for test case PDF
    ## and test result location in Devtest
    ##==================================================
    ## devtest.report.test.pdf.path=/devtest/reports/api/generatePDF/functional/

    ##==================================================
    ## APIM integration parameters
    ##==================================================
    ## apim.sskar.filename=[sskarFileName]
    ## apim.solution.kit.guid=[SolutionKitGUID]

     

     

     



  • 2.  Re: Some components are configured with non-production database (Derby).
    Best Answer

    Broadcom Employee
    Posted Sep 28, 2017 02:03 AM

    In the dradis.properties comment the following line

    dradis.db.internal.enabled=true

     

    & add

    dradis.db.internal.enabled=false

     

    Refer Configure Enterprise Dashboard to Use Oracle - DevTest Solutions - 10.1 - CA Technologies Documentation 

     

    Restart all DevTest components & check if your issue is resolved



  • 3.  Re: Some components are configured with non-production database (Derby).

    Posted Sep 29, 2017 12:09 PM

    issue not resolved



  • 4.  Re: Some components are configured with non-production database (Derby).

    Broadcom Employee