JIRA 4.0 : Installing JIRA on Orion Server - Oracle OC4J
This page last changed on Jun 15, 2009 by rosie@atlassian.com.
These instructions will help you install JIRA on OrionServer and Oracle's App Server (OC4J). This document is relevant to Orion 1.5.4, 1.6.0 and 2.0.x, and OC4J 9.0.4 up to 10.1.2.x. On this page:
1. Unpack JIRADownload and unzip JIRA (but not with XP's unzipper nor the default tar utility on Solaris). Ensure that you download the WAR/EAR version, not the Standalone version that is recommended on the Downloads page.
A new directory containing JIRA will be created, hereafter referred to as $JIRA_INSTALL.
2. Database configuration2.1. Copy JDBC driver jar to Orion/OC4JDownload the JDBC driver .jar file for your database (see the list here), and copy it to Orion's the lib/ directory (or OC4J's j2ee/home/applib/). For instance with PostgreSQL, one might have $ORION/lib/pg73jdbc3.jar. 2.2 Orion/OC4J Database configurationEdit $ORION/config/data-sources.xml (or $OC4J/j2ee/home/config/data-sources.xml) and define a 'datasource' for the database you wish JIRA to use. For example, using PostgreSQL: <data-source class="com.evermind.sql.DriverManagerDataSource" name="JIRA database" location="jdbc/JiraCoreDS" xa-location="jdbc/xa/JiraXADS" pooled-location="jdbc/JiraDS" connection-driver="org.postgresql.Driver" username="postgres" password="postgresPassword123" url="jdbc:postgresql:jiradb" inactivity-timeout="30" /> or for HSQLDB (which, although you shouldn't use it in the long term, has the virtue of requiring zero setup): <data-source class="com.evermind.sql.DriverManagerDataSource" name="JIRA database" location="jdbc/JiraCoreDS" xa-location="jdbc/xa/JiraXADS" pooled-location="jdbc/JiraDS" connection-driver="org.hsqldb.jdbcDriver" username="sa" password="" url="jdbc:hsqldb:/tmp/jiradb" inactivity-timeout="30" /> Database details (in bold) will vary depending on database — see this page for other database details.
2.3. JIRA entityengine.xml configurationHaving installed a JDBC driver and configured a datasource, you now need to tell JIRA where to find the datasource and transaction manager, as well as what type of database you're using. Open the edit-webapp/WEB-INF/classes/entityengine.xml file. There are two sections that must be changed. First, near the top, locate: <transaction-factory class="org.ofbiz.core.entity.transaction.JNDIFactory"> <user-transaction-jndi jndi-server-name="default" jndi-name="java:comp/env/UserTransaction"/> <transaction-manager-jndi jndi-server-name="default" jndi-name="java:comp/env/UserTransaction"/> </transaction-factory> and remove the /env, so it reads: <transaction-factory class="org.ofbiz.core.entity.transaction.JNDIFactory"> <user-transaction-jndi jndi-server-name="default" jndi-name="java:comp/UserTransaction"/> <transaction-manager-jndi jndi-server-name="default" jndi-name="java:comp/UserTransaction"/> </transaction-factory> Second, at the bottom, customize the datasource section, specifying the right database type and jndi-name (highlighted in bold here): <datasource name="defaultDS" field-type-name="postgres72" 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" check-indices-on-start="true"> <jndi-jdbc jndi-server-name="default" jndi-name="jdbc/JiraDS"/> </datasource> (In this example we're using PostgreSQL, and have added a schema-name="public" attribute as PostgreSQL requires.) The jndi-name attribute in entityengine.xml must match the ejb-location attribute in your Orion config/data-sources.xml file. Note the lack of java:comp/env in the jndi-name attribute.
To specify the location of your JIRA Home Directory (note that you need to do this before you build JIRA):
You can specify any location on a disk for your JIRA home directory. Please be sure to specify an absolute path. Please note that you cannot use the same JIRA home directory for multiple instances of JIRA. We recommend that you do not specify your JIRA home directory inside your installation directory, to prevent information from being accidentally lost during major operations (e.g. backing up and restoring instances). 4. App server modificationsOC4J 9.0.4 users: please also edit j2ee/home/config/application.xml, and comment out the '../jsp/lib/taglib' library: <!-- <library path="../jsp/lib/taglib"/> --> Otherwise you will get errors like this when importing data or upgrading: 2005-11-21 15:07:17,089 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org/dom4j/Element java.lang.NoClassDefFoundError: org/dom4j/Element at org.jaxen.dom4j.Dom4jXPath.<init>(Dom4jXPath.java:103) at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:313) at org.dom4j.xpath.DefaultXPath.<init>(DefaultXPath.java:63) at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:188) at org.dom4j.DocumentHelper.createXPath(DocumentHelper.java:109) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build92.doUpgrade(UpgradeTask_Build92.java:63) .... This does not apply to OC4J 10.0.2.x and above. Finally, Orion does not come bundled with a compiler for JSP files. Hence Orion users (not OC4J) will need to copy tools.jar from the JDK lib directory to the Orion directory. This doesn't apply to OC4J. 5. Build JIRANow build JIRA by typing build (Windows) or ./build.sh (Unix) on the command line, in $JIRA_HOME. This will produce the deployableWARfile in the $JIRA_HOME/dist-generic directory. You can copy this elsewhere if you prefer. 6. Deploy JIRAEdit config/application.xml to add the JIRA webapp to the default application like so: <web-module id="jira" path= _"$JIRA_HOME_ /dist-generic/atlassian-jira-3.3.war"/> (where $JIRA_HOME is the path to your JIRA distribution) Now bind this "jira" webapp to a website. For example, to add JIRA to the default Orion website edit config/default-web-site.xml (in OC4J, config/http-web-site.xml) and add the following line: <web-app application="default" name="jira" root="/jira"/> Where:
7. Set mail.mime.decodeparametersThe following system property must be set in order for the JIRA mail handler to work correctly with emails from RFC 2231-compliant mail clients: mail.mime.decodeparameters=true System properties are set in different ways depending on your application server. 8. Start Orion with -userThreads propertyStart Orion by using java -Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl -jar orion.jar -userThreads (oc4j.jar in j2ee/home for OC4J) in the directory where you installed Orion. Watch the log/* files for any errors. In Oracle App Server (OAS) -userThreads is set in the GUI screen. Go to <ContainerName> -> Administration -> Server Properties. On that screen, the field Command Line Options, OC4J Options has a default value of "-properties". It should be changed to -properties -userThreads
JIRA should become accessible at http://localhost/jira/ (using Orion, and assuming the default port 80 in default-web-site.xml) or http://localhost:8888/jira (OC4J). Run the Setup Wizard .
Problems?Here's a list of things to check:
If the problems persist, please file a support request, attaching your logs and config files, and we'll take a look. User-contributed notesHave experiences to share with Orion and JIRA? We welcome your thoughts. Please see the user-contributed Orion notes. |
![]() |
Document generated by Confluence on Oct 06, 2009 00:31 |