Previous Topic: Internal Database ConfigurationNext Topic: Configure DevTest to Use DB2


External Database Configuration

You can configure DevTest to use an external database by editing the site.properties file in the LISA_HOME directory.

Note:

The _site.properties file includes properties for each of the supported databases:

If you are running DevTest Server, you do not need to reconfigure each DevTest Workstation installation. The configuration in site.properties is propagated to each workstation, VSE, coordinator, simulator server, and any other DevTest component that connects to the registry.

The general steps are as follows:

  1. Locate the _site.properties file in the LISA_HOME directory and change the name to site.properties.
  2. Modify the new site.properties file, uncommenting the properties to match the target database.
  3. When configuring to a DevTest supported external database, such as Oracle, DB2, MySQL, or SQL Server:
    1. Uncomment the following properties for that external database in the appropriate section.

      For example:

      lisadb.pool.common.driverClass=oracle.jdbc.driver.OracleDriver lisadb.pool.common.url
      
      lisadb.pool.common.url=jdbc:oracle:thin:@HOST:1521:SID
      
    2. Update the lisadb.pool.common.url property with the appropriate hostname, port, and SID values.
    3. Update the following user and password properties with the correct values for accessing the database:

      lisadb.pool.common.user

      lisadb.pool.common.password

    4. Comment out the following two properties for the Derby database:

      #lisadb.pool.common.driverClass=org.apache.derby.jdbc.ClientDriver

      #lisadb.pool.common.url=jdbc:derby://localhost:1528/database/lisa.db;create=true

    5. Set the following property to false:

      lisadb.internal.enabled=false

  4. Start the registry or DevTest Workstation.