JIRA application installation directory
.nuThe JIRA installation directory is the directory into which the JIRA application files and libraries have been extracted, either:
JIRA does not modify or store any data in this directory.
Important files and directories
The directories/files described below are found under different sub-directories of the 'JIRA Installation Directory', depending on whether you have installed a recommended Windows, Linux or Archive JIRA. Please substitute the following directories for the
<jira-application-dir> placeholder (used throughout the rest of this section), as follows:
- 'Recommended' distributions — the
atlassian-jirasubdirectory of the 'JIRA Installation Directory' installed using the 'Windows Installer' and 'Linux Installer', and there associated installations from archive files (.zip and tar.gz respectively).
The default installation directory on Linux is:
This file tells JIRA where to find the JIRA application home directory.
Be aware that your JIRA home directory defined in this file can be overridden. See Setting your JIRA application home directory for more information.
This file stores the default values for JIRA's advanced configuration settings and should not be modified. The default values of properties in this file are customized (i.e. overridden) by redefining them in either the
jira-config.properties file (in your JIRA application home directory) or the JIRA database (via the JIRA administration area). See Advanced JIRA configuration for more information.
This is the directory where plugins built on Atlassian's Plugin Framework 1 (i.e. 'Plugins 1' plugins) are stored. If you are installing a new 'Plugins 1' plugin, you will need to deploy it into this directory.
'Plugins 2' plugins should be stored in the JIRA application home directory.
JIRA's logging configuration file. See Logging and profiling.
The actual log files generated by JIRA can be found in the following locations:
- JIRA application log —
- Application server log — generally the application server log file can be found under the
logsdirectory. However, this can vary depending on the application server you are running.
This file configures the OFBiz Entity Engine, which JIRA uses to store persist data in a data source.
This file includes garbage collection (GC) logs that are used to improve the performance of JIRA applications. The log statements indicate when Java is collecting garbage, how long this process takes, and how much memory has been freed. The file is generated automatically, and is also included in the Support Zip package. For more info, see Using garbage collection logs.
The sub-directories/files described below are found under the root of the JIRA application installation directory.
This file is used for JIRA SSL configuration. See Running JIRA applications over SSL or HTTPS.
These files include garbage collection (GC) logs that can be used to monitor the performance of JIRA applications. The log statements indicate when Java is collecting garbage, how long this process takes, and which resources can be freed. The files are created automatically, and then overwritten if the maximum number of files (5) is reached. The timestamp indicates when the JIRA session related to the logs was started. For more info, see Using garbage collection logs.
The file used to edit JAVA_OPTS memory settings will depend on the method used to install JIRA, as well as the operating system used for your installation.
For example, if you are running JIRA on Tomcat in Windows (manual startup), you would update the following file:
whereas for JIRA on Tomcat in Linux/Unix, you would update this file:
See Increasing JIRA memory for further details.