Atlassian JIRA on Ubuntu

Some notes for installing and upgrading Atlassian JIRA on Ubuntu LTS (12.04 tested for these notes).

  • For production use, install the MySQL Server package with “apt-get install mysql-server” (can be verified with “dpkg --list mysql-server“).
    • I recommend creating a database name like “jiradb” and granting access to an isolated MySQL user named “jirasql” or similar. For upgrades, the database configuration will be re-used.
  • Download the latest JIRA Linux Installer (self-extracting shell archive). Verify the hash if possible (md5sum or similar).
  • As a precaution, I strongly recommend you use mysqldump, tar, and gzip to create a backup of your JIRA database and attachments. The installer will automatically backup some of your JIRA files, but you should be backing up the DB and attachments separately.
  • Follow the official JIRA install or upgrade document. The install bundle will handle most of the tricky dependencies and advanced configuration options for you.
  • A dedicated Linux user/group is created or re-used for JIRA to isolate it from the rest of the system. The user/group are both usually named “jira.”
  • Default “JIRA Home” directory is “/var/atlassian/application-data/jira”
  • Default “JIRA Installation” directory is “/opt/atlassian/jira”
  • Obtain a paid SSL/TLS certificate from your CA. For upgrades, you will re-use the existing certificate. Follow the instructions provided by your CA for “Apache Tomcat” which will help you create a custom Java Key Store (JKS) file for JIRA. Keep a backup of the JKS file in a secure location. Atlassian also provides useful instructions for the SSL Certificate process.
  • After every install or upgrade, you will need to re-apply the SSL settings using the JIRA configuration tool. Default tool location is “/opt/atlassian/jira/bin/config.sh”
    • This tool greatly simplifies the process of using your JKS certificate with JIRA. Unfortunately the JIRA upgrade installer is not smart enough to copy your SSL configuration so you will need to re-run the JIRA config.sh tool every time you apply a software update.
      • You need to know your “Keystore Path”, “Keystore Password”, and “Key Alias” to configure HTTPS using the Jira config.sh tool.
    • JIRA needs to be restarted to use the SSL certificate. Try “service jira stop” followed by “service jira start” to use the new SSL/TLS configuration.
Advertisements

About notesbytom

Keeping technology notes on WordPress.com to free up my mind to solve new problems rather than figuring out the same ones repeatedly :-).
This entry was posted in Linux, System Administration and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s