Directory Structure

This topic describes the directory structures created by the setup program.

Related Topics
J2EE Implementation
File Naming Conventions
Installation Log Files

Build scripts

The ENOVIA Business Process Services setup program adds the following subdirectories to the location specified as the directory for the build scripts, usually the installation directory for ENOVIA Live Collaboration Server software.

Subdirectories created under: 
SERVER_INSTALL\Apps\Framework\<version>\
 
         | Common\
 All trigger programs common to all applications; includes their utility programs. 
         | Common UI\
 Program and image files needed for the user interface. Applet jar files are also located here. 
         | Doc\
 User’s guides and online help for the Application Exchange Framework and the applications. Online help for each application is located in a subdirectory with the name of the application.

The user’s guides for the apps and the framework are located in the pdf\ directory.

The common\ directory contains VCP help.

The javadoc\ directory contains javadoc from the framework classes.

 
         | Pixmaps\
 Graphics (.gif) files for icons and other images 
         | Schema\
 Tcl file that add administrative objects owned by each application; also includes programs used by the framework, such as the trigger manager, atuomatic object creation program, and the scheman variable mapping program. 
         | Store\
 Test store directory used for checking in files; empty upon installation. 
         | UserInterface\
   
         | Uninstall\
   
            | UI\
   
              | Backup\
   
                | ematrix\
 Any modified files are copied here using the same directory structure as exists under the STAGING\ directory.

The setup program for each ENOVIA product add a subdirectory under the Framework\ directory. Each application subdirectory contains the program files needed to build that application. For example, the directory structure would look as follows if the Engineering Central application were installed.

Subdirectories created under: 
SERVER_INSTALL\Apps\EngineeringCentral\<version>\
 
         | AppsCommon\
 Program files for the Common Components application 
         | Common\
   
         | Doc\
   
         | EngineeringCentral\
 Program files for the Engineering Central application 
         | Uninstall\
   
            | UI\
   
              | Backup\
   
                | ematrix\
 Any modified files are copied here using the same directory structure as exists under the STAGING\ directory.

Application Server directories

When Web Interface is chosen during framework installation, the setup program creates a subdirectory called ematrix\ under the STAGING\ directory. Setup installs some files to this directory, and creates subdirectories for other files. When you install an ENOVIA product, setup creates a subdirectory under the ematrix\ directory using the name of the application, and copies all application-specific files to this subdirectory. Directories for the online help and the user's guide are also created. When setup is complete, the following directory structure is created under the ematrix\ directory:

Subdirectories created under: 
SERVER_INSTALL\STAGING\
 
        | ematrix\
 JSP, JavaScript, and style sheet files related to the Login, Logout, and Home pages. All other component files are in the common\ subdirectory. 
           | classes\
 .jar files needed for the applications 
           | common\
 All JSP files that belong to the Application Exchange Framework and the dynamic user interface components used for applications. Only ENOVIA Business Process Services installs to the common\ directory and its subdirectories. Individual applications use files from the directory but don’t install to it. 
           | scripts\
 All JavaScript (.js) files that belong to ENOVIA Business Process Services; used for the applications. 
           | styles\
 All style sheet (.css) files that belong to ENOVIA Business Process Services; used for the applications. 
           | images\
 All image (.gif) files that belong to ENOVIA Business Process Services; used for the applications. All the icon files for the object types are in this directory. For example, it contains images for object type Part and administration types like Role and Person. 
           | components\
 Program and image files for common components; installed as part of ENOVIA Business Process Services. 
           | doc\
 Contains a subdirectory for each installed application’s help systems, and a pdf\ directory for user’s guides. Within each application’s help\ subdirectory, there is a subdirectory for each language, named using the standard abbreviation for the language (e.g., en\ for English, fr\ for French, etc.). The javadoc\ directory contains javadoc from the framework classes. 
           | properties\
 All property files, including the String Resource files and system property files that let you configure features. 
           | APPS_DIR\
 Each application, such as Engineering Central and Supplier Central, has its own directory. The application subdirectories have the same name as the application with no spaces, such as EngineeringCentral\ and SupplierCentral\. The following types, which belong to the applications, are in this directory:
  • JSP (.jsp) files
  • JavaScript (.js) files
  • Style sheet (.css) files
  • All component files
 
              | images\
 All image (.gif) files that belong to the corresponding applications 
           | Web-Inf\
 Contains the emxUtil.tld and framework.tld files, which are custom tag libraries.