Installing JIRA on JBoss 3

The application server (JBoss) is responsible for establishing a database connection, and making it available to webapps like JIRA as a "DataSource". JBoss comes with one DataSource preconfigured using a built-in hsqldb database. You can see the configuration for this in server/default/deploy/hsqldb-ds.xml. In the rest of this guide, we assume use of this DataSource (called 'DefaultDS').

If you wish to use another database (MySQL, Oracle etc), create another config file in the 'deploy' directory, eg server/default/deploy/jira-ds.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!-- DataSource for JIRA webapp,
     called 'JiraDS' (must be same in entityengine.xml) -->
<datasources>
  <local-tx-datasource>
    <jndi-name>JiraDS</jndi-name>
    <connection-url>jdbc:mysql://localhost/jiradb?autoReconnect=true</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>jira_mysql_username</user-name>
    <password>jira_mysql_password</password>
  </local-tx-datasource>
</datasources>

Here we have created a MySQL DataSource called 'JiraDS'. We would also have to copy the MySQL JDBC jar to servers/default/lib/. See the database configuration page for details.

Open the edit-webapp/WEB-INF/classes/entityengine.xml file, and make the following changes:

1.1 Modify transaction factory attribute

Make the following changes (in bold) to the <transaction-factory> tag:

<transaction-factory
  class="org.ofbiz.core.entity.transaction.JNDIFactory">
  <user-transaction-jndi jndi-server-name="default"
    jndi-name="UserTransaction" />
  <transaction-manager-jndi jndi-server-name="default"
    jndi-name="java:/TransactionManager" />
</transaction-factory>

1.2 Modify datasource attributes

Lower down in entityengine.xml, the <datasource> tag needs modifying in two locations:

<datasource name="defaultDS"
                field-type-name="hsql"
                schema-name="PUBLIC"
                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:/DefaultDS"/>
</datasource>

• The field-type-name parameter needs to be set appropriately for the type of database you use.
• The jndi-name attribute needs to point to a DataSource to use. As mentioned above, JBoss comes preconfigured with a "DefaultDS" DataSource, which we assume use of here. If instead, you added the MySQL DataSource above, the jndi-name value would be java:/JiraDS.

Now build JIRA by typing build (Windows) or ./build.sh (Unix) on the command line, in the directory where you originally extracted JIRA to. This will produce a deployable WAR file in the dist-generic directory.

On some versions of JBoss you may need to undeploy any old JIRA EARs/WARs and remove all deployed files before deploying the new WAR.

Rename the WAR to jira.war, and drop it into your deployment directory (usually jboss/server/default/deploy/). If JBoss is running, you should see messages on the JBoss console saying that it is deploying the WAR.

Start JBOSS by running bin/run.bat under the JBoss directory. Watch the startup logs for errors. Once JBoss has started, JIRA should be accessible at http://localhost:8080/jira/ (change the host and port as needed; the 'jira' part is whatever the WAR name is).

Have experiences to share with JBoss and JIRA? We welcome your thoughts. Please see the user-contributed JBoss 3 notes.