Installing JIRA on IBM Websphere 5.

1
These instructions will help you install JIRA on IBM Websphere 5.1, noting some deviations
from the generic install instructions.

Warning:
Please install WebSphere Application Server 5.1 Cumulative Fix 5. Actually, JIRA should only need PQ80592 (and its prerequisites)
and PQ87029 applied. PQ80592 resolves a bug that makes all JIRA pages appear blank (JRA-2510). PQ87029 ensures that
importing data works correctly (JRA-8442). Please note that only Websphere 5.1.0.5 has been tested.

1. 1. Configure JIRA

1.1. Unpack JIRA

Unpack JIRA EAR/WAR distribution into a temporary directory.

1.2. Configure entityengine.xml

The edit-webapp/WEB-INF/classes/entityengine.xml file needs to be modified
to specify the correct database field type. The example below is configured for MS SQL Server.
Please ensure that the value of the jndi-jdbc/jndi-name attribute has the "java:comp/env/" prefix.
The prefix should be in the file by default.

<datasource name="defaultDS" field-type-name="mssql"

helper-class="org.ofbiz.core.entity.GenericHelperDAO"
check-on-start="true" use-foreign-keys="false"
use-foreign-key-indices="false"
check-fks-on-start="false"
check-fk-indices-on-start="false"
add-missing-on-start="true">
<jndi-jdbc jndi-server-name="default" jndi-name="java:comp/env/jdbc/JiraDS"/>
</datasource>

Warning:
Make sure that your entityengine.xml is well-formed XML. Websphere "swallows" the error messages you should get in your log
file if entityengine.xml is not well-formed, and instead reports a spurious error message.
You can test that your entityengine.xml is well-formed by opening it in Internet Explorer or Firefox. These browsers will display an
error if the file is not well-formed XML, and will indicate the location of the error in the file.

1.3. Modify web.xml

Edit webapp/WEB-INF/web.xml file and remove lines:

<!-- Uncomment for WebSphere

Uncomment for WebSphere -->

which appear towards the bottom of the file. After removing the lines the <resource-ref>
entry should look like:

<!-- resource references -->

<resource-ref>
<description>Database for JIRA</description>
<res-ref-name>jdbc/JiraDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>SERVLET</res-auth>
<res-sharing-scope>Unshareable</res-sharing-scope>

Page 1
Copyright © 2002-2005 Atlassian All rights reserved.
 Installing JIRA on IBM Websphere 5.1

</resource-ref>

Please ensure that the res-sharing-scope is set to Unshareable.

2. 2. Build JIRA
Now build JIRA by running the build script for your platform (e.g. build.bat on Windows or
build.sh on a Unix or Linux system). This will produce the deployable WAR file in the
dist-generic directory.

3. 3. Configure the Websphere datasource

The datasource for the database should now be configured in Websphere using the Websphere
Administration Console. See this guide for setting up a DataSource in the admin web interface.
When defining the datasource map it to the jdbc/JiraServerDS JNDI key. Please ensure
that the JNDI key is set to jdbc/JiraServerDS and not jdbc/JiraDS.

4. 4. Deploy JIRA in Websphere

The JIRA WAR file can now be deployed to Websphere (by e.g. using the Websphere's
Administration Console).
When deploying the JIRA WAR file please bind JIRA's jdbc/JiraDS datasource to
Websphere's jdbc/JiraServerDS entry.

Note:
Please use the WAR file in dist-generic directory and NOT the dist-tomcat directory.

Warning:
Please ensure that WebSphere's "Servlet Caching" is turned off. Otherwise JIRA will die with ClassCastExceptions.

5. User-contributed notes
Have experiences to share with Websphere 5.1.x and JIRA? We welcome your thoughts. Please
see the user-contributed Websphere notes.

Page 2
Copyright © 2002-2005 Atlassian All rights reserved.