- Grabbed the standalone version and unpacked into the /opt directory.
- Made a soft link to the install so upgrades will be a bit easier: ln -s atlassian-jira-enterprise-4.1.2-standalone jra
- edit /opt/jira/atlassian-jira/WEB-INF/classes/jira-application.properties so that jira.home points /opt/jira
- used Webmin to create a user just for the Jira process. I called mine, wait for it...jira.
- changed ownership of the jira installation directory to be owned by the jira user
- start up jira as the jira user: sudo -u jira /opt/jira/bin/startup.sh
- I got a PermGen switch warning which pointed me to the troubleshooting guide. Decided not to worry about it until I actually do run out of PermGen space
- I realized that the instructions did not walk me through how to connect Jira to my database so I shutdown the instance and followed those directions.
- using Webmin, I created a new db user named: jirauser and gave it all permissions
- using Webmin, created a new database name jira making sure to set it to use UTF-8 encodings
- copy the MySQL JDBC driver to the /opt/jira/lib directory. Once I did that, I saw that a JDBC driver already existed in that directory, although a slightly older one, so I removed mine and left things as is.
- run the Jira configuration tool: sudo -u jira /opt/jira/bin/config.sh . I had a problem doing this because the jira account isn't meant for logging in and doesn't have an environment. To work around this, I reset the permissions on the installation directory to my account and re-ran the tool. Once I made the proper configuration choices, I reset the files back to being owned by the jira account.
- started jira again using the command in step 6
- connected to Jira via the web browser: http://localhost:8080/
- ran through the configuration wizard. Decided to not accept the default directories and use /opt/jira-home instead. Figured I wouldn't lose data to upgrades if I did a stand alone directory.
Quick blurbs about my daily struggle with technology. You'll likely to find ramblings about Linux, Java, home networks and Cloud computing.
Monday, July 19, 2010
Atlassian Stack: Jira
Next up is Jira, the task/bug tracking portion of the stack.
Subscribe to:
Post Comments (Atom)
Thanks for sharing your documentation of setting up. Even after installing and maintaining several Jira instances, it still helps to see it spelled out in a simple punch list when starting a new one!
ReplyDelete