We are trying to deploy JIRA in house and would like to know if there is a recommended system's architecture diagram
Thank you for your reply, we are trying to make sure there is a fallback server in case of failure of the primary as well as authenticating through LDAP (the only means as I understand), what would the need be there, an attachment string to the RO group or a separate group created in LDAP specific to JIRA
Thanks in advance
A system architecture diagram is a little vague as a requirement - what do you expect it to tell you?
When deploying JIRA, you need a server to run it, network access to the server, some storage for the installation and data directories and a database to connect to. That's a diagram with one or two simple circles if you drew it up as an architecture diagram really. If you want to show details like connectivity, or data flow, or physical disks etc, then that's mostly up to you and your hardware, network and software standards, not something we can draw for you.
Ok, considering part of a failover system without looking at the whole isn't really going to help. For the LDAP, you'll want something that can mirror the same LDAP accounts you're using and provide that to JIRA if it fails.
Then for JIRA, have a look through https://confluence.atlassian.com/enterprise/high-availability-guide-for-jira-288657149.html
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs