Layout of the installation directory

The installation directory has a specific layout after the installation process completes. Some directories are created when you start the server and other are configured in the installed.properties file.

The installation process for version 6.2.2 and above creates an installation directory structure that is different from earlier versions. The following table shows the differences. Note that the values in the table are the default values.

Table 1. Installation directory structure
Versions prior to Version 6.2.2 Version 6.2.2 and above Description
groovy-2.1.9 opt/groovy Contains the Groovy distributable used by plug-ins. Created during the installation process.
server/jre opt/java Contains the Java Runtime Environment (JRE) used to run the server. Created during the installation process.
server/tomcat/bin opt/tomcat/bin Contains Apache Tomcat web server software. Created during the installation process.
server/tomcat/conf opt/tomcat/conf Contains the Apache Tomcat configuration files. Created during the installation process.
server/tomcat/endorsed endorsed Contains the Apache Tomcat endorsed library files. Created during the installation process.
server/tomcat/lib opt/tomcat/lib Contains the Apache Tomcat library files. Created during the installation process.
server/tomcat/logs var/log Default directory where log files are stored. Created during the installation process.
server/tomcat/temp var/temp Contains temporary files used by the server. Created during the installation process.
server/tomcat/webapps opt/tomcat/webapps Contains the IBM® UrbanCode™ Release webapp run by Tomcat. Created during the installation process.
server/tomcat/work opt/tomcat/work Contains compiled JSPs and other assets stored by Apache Tomcat.
server/tomcat/files opt/tomcat/files Contains the Apache Tomcat legal files.
server/server.startup.bat bin/start_server.cmd Location and name of the executable file to start IBM UrbanCode Release on Windows. Created during the installation process.
server/server.shutdown.bat bin/stop_server.cmd The executable file to stop IBM UrbanCode Release. Created during the installation process.
server/server bin/server Location and name of the executable file to start and stop IBM UrbanCode Release on non-Windows systems. Created during the installation process.
ucrelease/conf conf/server The property files used by the server. Created during the installation process.
ucrelease/derby var/db/derby Files related to the Derby database. Created when the database is started.
ucrelease/emailNotificationImages var/emailNotificationImages Contains images uploaded for email notifications. Created on demand by the server.
ucrelease/licenses licenses Contains third party software licenses. Created during the installation process.
ucrelease/plugins plugins Default directory for the plug-in repository and reports. Created on demand by the server.
ucrelease/spooled-email var/mail/spooled-email Contains files needed for the SMTP server. Created on demand by the server.
ucrelease/spooled-email-failed var/email/spooled-email-failed Contains files needed for the SMTP server. Created on demand by the server.
ucrelease/sde_cache.data var/temp/sde_cache.data Contains information cached by the browser. Created on demand by the server.