You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I'm trying to setup our JIRA with our SSL cert. I'm a noob when it comes to Java and SSL though. I've tried to follow the instructions here -> Running Jira applications over SSL or HTTPS | Administering Jira applications Data Center and Server 9.11 | Atlassian Documentation but I'm having trouble with the Java portion.
I see the JIRA\jre\bin folder but no java, if that makes sense. If someone could provide more simple instructions I would greatly appreciate it.
Hi @John Aboud
Which step(s) are you getting stuck on?
It sounds like you might be missing the java executable in order to run the java commands.
IMO it maybe better to run your own Java than the bundled versions Atlassian may provide - In my case we use OpenJDK for our Atlassian data center apps running on Linux. <JAVA_HOME> in these instructions would be where ever your JDK was installed. If you do this you will need to update you environment variables so Jira knows where to find Java in order to run,
Thank for the reply. I'm running Jira on a Windows Server. When I started following the instructions, I ran into the Java problem. There is a JRE installed within the Jira installation folder, so I set the environment variable to point to that. Still didn't work.
Will installing a separate instance of JDK (possibly a different version) jeopardize my Jira installation?
I have not had much experience with Windows server but I don't think it would cause any issues. You will need to update your environment variables to point to the new JDK installation path. I imagine worse case would be that other apps depending on your Java installation may break if they don't support the JDK version.
Within my org and environment constraints - we manually upgrade our JDK each time there's a new version, and then simply point our JAVA_HOME variable to the new JDKs path. If we have any issues with this we just point back to the previous version.