JIRA

Admin

Use

	JIRA Installation & Upgrade Guide Requirements Installing JIRA Installing Java Installing JIRA Standalone Installing JIRA WAR/EAR Installing JIRA WAR/EAR Increasing application se.. Next step Running the Setup Wizard Connecting JIRA to a Database Database Overview SQL Server MySQL PostgreSQL Oracle DB2 Firebird MaxDB Sybase HSQL Switching databases Configuring JIRA Standalone Running JIRA as a Service Configuring SSL (HTTPS) Installing with Confluence Configuring JIRA WAR/EAR Configuration overview Configuring database storage Server-specific Guides Server Comparison JBoss 4.x JBoss 3.x Jetty OC4J 10.1.3.x+ Orion and OC4J 9.x-10.1.2.x Pramati 3.5 Resin 3 Resin 2.1 Tomcat 6.0 Tomcat 5.5 Tomcat 5.0 Tomcat 4.1 Tomcat 4.0 Weblogic 8.1 and 9.1 Websphere 6.x Websphere 5.1 Websphere 5 Other servers Integrating JIRA with a Web Server Integrating with IIS Integrating with Apache Upgrading JIRA Upgrading JIRA Safely Disabling Auto-Export

Installing JIRA WAR/EAR

PDF

Note

Not sure whether to install JIRA Standalone or JIRA WAR/EAR? Read the requirements and recommendations.

Installing JIRA WAR/EAR

The distribution ZIP file contains an Ant build script to create a deployable EAR or WAR for your particular application server (and any necessary library directories).

The basic set of steps to install JIRA WAR/EAR is as follows:

Download and unzip JIRA (but not with XP's unzipper nor the default tar utility on Solaris). Ensure that you download the WAR/EAR version, not the Standalone version that is recommended on the downloads page.
Follow the instructions in the readme.txt file, located in the root directory of the unpacked JIRA distribution. This refers to the server-specific installation guides.
Note, regardless of your choice of server, if your operating system is UNIX/Linux you are strongly recommended to create a dedicated user to run JIRA. For further details, please refer to the JIRA Server Requirements section on the Requirements page.
Access JIRA using your web browser and run through the brief setup wizard.

Note

Avoid the Windows XP built-in unzip tool! The built-in unzip tool in Windows XP is broken — it silently fails to extract files with long names (see JRA-2153). Other users have also reported problems using WinRAR. Please use another tool like WinZIP to unpack JIRA.
Avoid the Solaris default tar utility! On Solaris, please use GNU tar to unpack JIRA in order to handle long filenames.

Increasing application server memory

For production use, please check that your application server is allocated sufficient memory. Java apps claim up to only 64Mb by default, and this usually isn't enough for JIRA. See the Increasing JIRA memory page for more information.

Next step

Please see Configuring JIRA WAR/EAR.