Directory Structure

This page describes the directory structure of lwork and lsvr.
dts1024
This page describes the directory structure of
DevTest Workstation
and
DevTest Server
.
This page assumes that you did not specify a separate data directory for the installation of
DevTest Solutions
. If you have a separate data directory, the following directories can be in a location other than
LISA_HOME
:
  • cvsMonitors
  • database
  • hotdeploy
  • locks
  • tmp
  • vseDeploy
  • local.properties
  • logging.properties
  • de-identify.xml
  • _local.properties
  • _logging.properties
  • _de-identify.xml
  • library for customizations
  • projects with assets
  • examples folders
DevTest Workstation
Directories
The
LISA_HOME
directory for
DevTest Workstation
contains the following directories:
The
locks
directory must have read/write permissions.
  • .install4j
    Contains the installer.
  • addons
    Contains the
    DevTest
    add-ons.
  • agent
    Contains the files for the
    DevTest
     Java Agent.
  • bin
    Contains the executable files for
    DevTest Workstation
    and other components.
  • defaults
    Contains the audit document and staging documents that are common across all projects. Project-specific staging documents are located in the
    Projects
    directory.
  • doc
    Contains the license agreement, JavaDocs for the 
    DevTest
     Java Agent, and JavaDocs for the Software Development Kit (SDK).
  • examples
    A default project containing examples that use the demo server.
  • examples_src
    Examples source files and the Kiosk-related files.
  • hotDeploy
    A directory that
    DevTest
    monitors. This file contains Java classes and JAR files. Java classes and JAR files in this directory are on the
    DevTest
    classpath. Any new files or directories added to this directory are dynamically added to the
    DevTest
    classpath.
    Putting a custom extension into hotDeploy still requires rebooting the
    DevTest
    component (for example,
    VSE
    or 
    DevTest Workstation
    ) before the extension is available for use. The HotDeployClassLoader loads the extension’s class files, but the "lisaextension" file is not discovered automatically, so the extension is still unknown to
    DevTest
    . The "lisaextension" files are only discovered during start-up.
  • incontainer
    Contains the incontainer testing instructions.
  • jre
    Contains the required JRE.
  • lib
    Contains the required JAR files.
  • licenses
    Contains the license files that are required for running
    DevTest Solutions
    .
  • locks
    Contains the lock files that are used for interprocess concurrency.
  • Projects
    Contains example projects, and any projects that you create.
  • reports
    Contains the XML-based test reports that
    DevTest
    creates.
  • snmp
    Contains the SNMP-related files.
  • tmp
    Contains the logging files that
    DevTest
    creates. If you communicate with Support on an issue, you could be asked to send one or more files from this directory. The tmp directory must be 1.5 times the size of the installer.
  • umetrics
    Contains the files that are related to collecting metrics.
  • webserver
    Contains the web server files.
DevTest Server
Directories
The
LISA_HOME
directory for
DevTest Server
contains the following directories:
The
locks
directory must have read/write permissions.
  • .install4j
    Contains the installer.
  • addons
    Contains the
    DevTest
    add-ons.
  • agent
    Contains the files for the
    DevTest
    Java Agent.
  • bin
    Contains the executable files for the registry, coordinator, simulator, 
    VSE
    DevTest Workstation
    , and other components. This directory also contains the following batch files:
    • startdefservers.bat - starts the default servers.
    • stopdefservers.bat - stops the default servers.
  • cvsMonitors
    Contains the deployed CVS monitors.
  • database
    Contains the DDL files and
    Application Insight
     upgrade scripts for various databases.
  • defaults
    Contains the audit document and staging documents that are common across all projects. Project-specific staging documents are located in the
    Projects
    directory.
  • doc
    Contains the license agreement, JavaDocs for the
    DevTest
     Java Agent, and JavaDocs for the Software Development Kit (SDK).
  • examples
    A default project containing examples that use the demo server.
  • examples_src
    Examples source files and the Kiosk-related files.
  • hotDeploy
    A directory that
    DevTest
    monitors. This file contains Java classes and JAR files. Java classes and JAR files in this directory are on the
    DevTest
    classpath. Any new files or directories added to this directory are dynamically added to the
    DevTest
    classpath.
  • incontainer
    Contains the incontainer testing instructions.
  • jre
    Contains the required JRE.
  • lib
    Contains the required JAR files.
  • licenses
    Contains the license files that are required for running
    DevTest Solutions
    .
  • locks
    Contains the lock files that are used for interprocess concurrency.
  • Projects
    Contains example projects, and any projects that you create.
  • reports
    Contains the XML-based test reports that
    DevTest
    creates.
  • snmp
    Contains the SNMP-related files.
  • tmp
    Contains the logging files that
    DevTest
    creates. If you communicate with Support on an issue, you could be asked to send one or more files from this directory.
  • umetrics
    Contains the files that are related to collecting metrics.
  • webserver
    Contains the web server files.