• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk and Atlassian JIRA

S

slowice

Guest
Hi!

Does anybody have instructions on how to install Atlassian JIRA (complete installation instructions?) and limited to one domain only in PLESK 8??

I prefer the TOMCAT installation, but generating the WAR file and installing does not work right, and i am not sure if the standalone version with it's own tomcat would break something in plesk / on the server...
Any help appreciated!
 
The standalone should not interfere
with Plesk. You may configure
Tomcat to bind on a different port
to Plesk and/or have tomcat Listen
on a different address to Plesk.
 
i tried the standalone too, but i always get the error message that the JAVA_HOME is not set.

what is the correct path for JAVA_HOME on Plesk 8.2???

Jira needs Java JDK to work.
 
To locate the java home, do locate from the command line like so:
locate /bin/java
The JAVA_HOME will be the value of the resulting path to the left of locate /bin/java
e.g. if the result was
/usr/java/jdk1.6.0_03/bin/java
then the JAVA_HOME value would be /usr/java/jdk1.6.0_03

Add the following to the Alassian startup script (near the top):
export JAVA_HOME=/usr/java/jdk1.6.0_03
 
Back
Top