Jetty has moved!
Jetty is a project at the Eclipse Foundation.
Homepage:http://www.eclipse.org/jetty
Downloads: http://download.eclipse.org/jetty/
Documentation:http://www.eclipse.org/jetty/documentation/current/
About:http://www.eclipse.org/jetty/about.php
Jetty Powered:http://www.eclipse.org/jetty/powered/
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

How to use Jetty with JIRA

These instructions have been tested against:

Jetty Version

Jira Version

Tx Mgr & Datasource

JVM

Servlet & JSP

6.0.1

3.6.5

JOTM 2.1.10 & HSQL 1.7

1.5

2.5 & 2.1

6.1

3.6.5

JOTM 2.1.10 & HSQL 1.7

1.5

2.5 & 2.1

6.1

3.6.5

Atomikos 3.1.0 & HSQL 1.7

1.5

2.5 & 2.1

6.1

3.6.5

Atomikos 3.1.0 & HSQL 1.7

1.4

2.5 & 2.0

Prepare the JIRA webapp

  1. if you've downloaded the standalone distribution of JIRA:
    1. copy the commons/lib/hsqldb-1.7.1-patched.jar into $jetty.home/lib/ext
    2. copy the atlassian-jira directory into your $jetty.home/webapps-plus directory.
    3. edit $jetty.home/webapps-plus/atlassian-jira/WEB-INF/classes/entityengine.xml to change from the tomcat 5-specific setup for the JNDI binding for the UserTransaction. It must be java:comp/UserTransaction and NOT java:comp/env/UserTransaction.
  2. if you've downloaded the webapp distribution of JIRA:
    1. download the hsqldb jar from the JIRA site and copy to $jetty.home/lib/ext
    2. build the webapp following the instructions.
    3. make the directory $jetty.home/webapps-plus/atlassian-jira.
    4. expand the atlassian-jira-3.6.5.war into it.
    5. edit $jetty.home/webapps-plus/atlassian-jira/WEB-INF/classes/entityengine.xml to ensure that the JNDI binding for the UserTransaction is java:comp/UserTransaction. Also check that if you are using hsqldb that the <datasource> element at the bottom of the file has attribute field-type-name="hsql".
  3. regardless of which distribtion you downloaded, now edit the $jetty.home/webapps-plus/atlassian-jira/WEB-INF/web.xml file:
    1. add a <resource-ref> for the DataSource used by JIRA:
    2. if you want to use a mail Session JNDI lookup, then also add a <resource-ref> for it too:
Icon

It is important that you copy the jira webapp into the directory that is setup to deploy webapps using JNDI. If you are using the default jetty setup from the distribution, then this directory will be $jetty.home/webapps-plus not $jetty.home/webapps.

Prepare Jetty

  1. set up the jetty installation for the transaction manager of your choice, following the instructions for JOTM here or Atomikos here.
  2. configure your commons-logging implementation so that JIRA (and JOTM if you are using it) send their log messages to the same log as the jetty server. You do this by using the jcl104-over-slf4j.jar (Commons Logging over SLF4J) and an slf4j log implementation jar. You can find both of these in $jetty.home/lib/jsp-2.0, and simply copy them up into into the $jetty.home/lib/ directory. Alternatively, if you want to use commons-logging, you will need to copy the commons-logging jar and a commons logging impl into the $jetty.home/lib/ directory instead.
  3. setup the JNDI resources. To save you some time, you can use the jetty-jira.xml file attached to this page, copy it into $jetty.home/etc, and uncomment either the Atomikos or the JOTM setup as you prefer. The file also contains a mail Session JNDI binding which you can uncomment and configure if you elected to setup a <resource-ref> for it in the JIRA web.xml in previous steps.
  4. run JIRA in jetty with:

Shortening the runline

Icon

You can move all of the jetty xml configuration into a single file if you want to shorten the runline. Better yet, put it all in etc/jetty.xml and you won't even have to specify any config file on the runline, as it is the default:

Addendum

For the curious, here's what the jetty-jira.xml file looks like:

  • No labels
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery