JIRA Standalone vs EAR/WAR installation

Darly Senecal-B

Hi Community, specially Atlassian:

I have three questions that maybe confuse you, but I need clarification

1) I undesrstood that JIRA EAR/WAR installation is more for application servers. However, in previous questions in this forum, I got confused that for one question in which WAR installation version is for users who doesn't want to administer another server. I need clarification for better understanding for WAR/EAR.

2) Another point to mention is about JIRA Standalone, which ships with the latest version of Tomcat and Java (as I know). Besides of those two feature, which other components has the standalone version of JIRA. Also, can you mention the requiremnts of for WAR/EAR version and which components ships the WAR as well.

3) In case that I had installed a previous version of Tomcat & Java before installing JIRA, does JIRA's Tomcat/Java affects the ones that I previously installed (in terms of installation Tomcat/Java upgrade and configuration)? If so, how?

Thanks in advance for your answers

Nic Brough -Adaptavist-

1) WAR/EAR is just the application. It needs to be installed in an application server (Tomcat for example) and is structured to allow moderately easy modifications, in that you have to build it yourself after configuring it and adding any changes you need to make. You have to provide your own application server, database and Java to use it.

2) Standalone has everything you need for a quick start. You download it and run the install, and that's it, you've got a working Jira. (Not a production class one - you need to move to a proper database, but it's pretty close and the move is easy). Note that standalone is basically a big bundle of stuff that includes a pre-confgured/pre-built WAR version

3) No, they install separately (unless you tell them to install over the existing one of course)

Requirements for all the various possible combinations of java, application server, war/ear download, etc all depend on what you want to run it on and what your intended usage of Jira is going to be.