Generic Server Installation Guide
| 
PDF |
If you have configured JIRA on an app server not documented by Atlassian, please share your experiences with others.
JIRA should be able to work on any J2EE 1.3 compliant application server or
Servlet 2.3 compliant web container.
The main installation issues are always to do with getting the right files
in the right place for the server so the classpaths are all working correctly,
and finding the JNDI locations of various objects.
We're actively seeking JIRA users on other application servers so that we can
work through any installation issues with them and provide detailed instructions
for their server in the distribution.
If you have problems following this guide on your server, please let us know
on the mailing list and we'll try to help
you work them out. Also debugging JIRA might give
you some extra helpful information.
We'll now go through the general steps required to install JIRA from the WAR (Webapp ARchive) distribution.
1. Unpack JIRA
Unzip the JIRA WAR (Webapp ARchive) distribution. A new directory containing JIRA will be created, hereafter
referred to as $JIRA_HOME
2. Configure JIRA
As described above, we need to edit entityengine.xml to tell JIRA about its database and
transaction manager. Edits should be made to edit-webapp/WEB-INF/classes/entityengine.xml, which
will be baked into the .war file when build.(sh|bat) is run. You will need to know the JNDI
locations of:
- the javax.transaction.UserTransaction and javax.transaction.TransactionManager
objects, for the transaction manager
- the location of your datasource (if configured via the server).
3. Build JIRA
JIRA can now be built by typing build (Windows) or ./build.sh (Unix) on the
command line in the $JIRA_HOME directory. This will produce the deployable WAR file in the
$JIRA_HOME/dist-* directories.
4. Deploy JIRA
Deploy the JIRA EAR or WAR in your application server - consult your server specific documentation for how to
do this.
5. Bind the JIRA website
JIRA has a single web module called atlassian-jira-web (for later versions, the module name is the same as the name of the WAR or EAR file that is generated from the ant process). You may need to configure this as a web module within your server.
If you have done these steps properly, the Setup Wizard should show up when
you access the path at which you have deployed JIRA via your web browser.
Again, if you have problems following this guide on your server, please let us know on the mailing list and we'll try to help you out.
