Building the DI Directory Structure

Prior to downloading and installing DI Platform server and developer software for 7.0, DI recommends that you create the following directory structure on your machine:

\DI

\Projects

\Solution

\downloads

\licenses

If yours is a large site where content is developed, tested, released, and extracted in four separate phases, but the content is stored on a single server, consider using a four-stage release process with a slightly different DI directory structure.

NOTE: This reflects the environments used on a single server so the DI directory has subdirectories for each environment.

You can install server and developer software on a single machine or different machines using the same directory structure. You can install Java and Apache Tomcat third-party software using DivePort-Setup.exe.

The following table provides a brief description of the default directories and subdirectories that the installer uses in a typical DI directory structure.

Directory	Subdirectory	Description
DI	\Projects	Default location for Workbench projects. This folder is created manually.
DI	\Solution	Default location for folders and files created by DI product installations. This folder is created manually.
DI\Solution	\downloads	Default location for DI software downloads. This folder is created manually.
DI\Solution	\licenses	Folder for licenses and key files. This folder is created manually.
DI\Solution	\diveline	Subdirectory with program files required by the DiveLine service. Each installed DiveLine instance can have its own \diveline folder.
DI\Solution	\dl-dataroot	Top level directory for the DiveLine server for configuration information, cache, and log files. Each installed DiveLine instance can have its own \dl-dataroot folder.
DI\Solution	\executables	Default location for many DI executable files.
DI\Solution	\webapps	Program, configuration, and setup files for DivePort and NetDiver.
DI\Solution	\webdata	Data and customization files for DivePort and NetDiver.