Deploying and Managing Atlassian Jira and Confluence Instances
Prerequisites and Environment Setup
Ensure the target server meets the system requirements for the specific versions of Jira or Confluence being deployed. A supported Java Development Kit (JDK) and a compatible database such as PostgreSQL, MySQL, or Oracle must be installed and configured prior to installation.
1. Acquisition of Installation Binaries
Download the official installation archives from the Atlassian website. Store the archives in a persistent directory, such as /opt/atlassian/installers.
# Example using wget for official distribution
wget https://www.atlassian.com/software/jira/downloads/bin/atlassian-jira-software-<version>.tar.gz
2. Configuration of Environment Variables
Performance tuning often requires modifying the startup scripts. Locate the setenv.sh file within the bin directory of the installation path.
# Edit the environment script
vi /opt/atlassian/jira/bin/setenv.sh
Adjust the JAVA_OPTS variable to allocate appropriate heap memory based on server capacity. Avoid injecting unauthorized agents.
# Example memory configuration
export JAVA_OPTS="-Xms1024m -Xmx2048m ${JAVA_OPTS}"
3. Database Identification and Backup
Before making significant changes, identify the instance configuration. For PostgreSQL databases, the instance identifier can be verified within the property tables.
-- Verify property entries
SELECT * FROM propertyentry WHERE PROPERTY_KEY='jira.sid.key';
Always create a full backup of the database and the confluence.cfg.xml or jira-config.properties files before proceeding with upgrades or migration.
4. License Management
Valid licenses must be obtained through the official Atlassian portal. Navigate to the administration panel within the application UI to apply the license key.
- Access Administration > License Details.
- Paste the valid license key obtained from the official dashboard.
- For Data Center editions, ensure the cluster configuration matches the license terms.
5. Service Control
Manage the application lifecycle using the provided service scripts. Ensure all nodes are stopped during maintenance windows.
# Stop the service
service jira stop
# Or for Confluence
service confluence stop
Apply configuration changes and restart the services to ensure settings take effect.
# Start the service
service jira start
# Restart if necessary
service confluence restart
6. Verification
After startup, verify the application logs for errors. Confirm that the license status is active and that the database connection is stable. Regular backups should be scheduled to maintain data integrity.