Getint for Jira Data Center
Getint for Jira Data Center & Server: Architecture & Deployment Guide
Overview
Getint for Jira Data Center and Server is a native application built using the Atlassian Plugins SDK (P2 framework). Unlike the Cloud version, which is a SaaS service, the Data Center version resides entirely within your infrastructure. This deployment type is designed for high-availability environments and organizations with strict data residency requirements.
1. Technical Architecture
The application runs as a native plugin within the Jira Java Virtual Machine (JVM).
Clustered Environments: For Jira Data Center instances with multiple nodes, Getint uses a cluster lock mechanism. This ensures that synchronization tasks are executed on only one node at a time, preventing data conflicts or duplicate syncs.
Scheduling: The app initiates a background scheduled job to handle data integration. While users define the sync interval in the settings, the actual execution is managed by the Jira internal scheduler.
Internal Communication: The app communicates with Jira via the Jira Java API and the Internal REST API.
2. Data Storage & Security
This deployment model is "Firewall-Friendly" and does not require outbound access to external Getint servers.
Local Storage: All configuration details, mapping logic, and synchronization metadata are stored within your own Jira Database (in dedicated Getint tables).
File Storage: Synchronization logs and temporary files are stored in the
JIRA_HOME/log/getintdirectory (or the rootJIRA_HOMEIf no log folder exists.)Zero External Connectivity: When deployed in a standalone on-premise capacity, the platform operates independently of
getint.ioservers. No ticket data ever leaves your internal network.
We know Data Center admins have to be careful about storage bloat. If you ever decide to uninstall the app, feel free to clear out any leftover Getint database tables and log files. It’s completely safe to delete them, and it’s actually a great way to keep your instance optimized and clutter-free.
3. Installation & Licensing
Following the 2025 standard, installation is managed directly via the Atlassian Marketplace.
Navigate to the Atlassian Marketplace.
Search for Getint and select the version compatible with Data Center.
Click Get it now or Try it free.
Log in to your Jira instance as a System Administrator.
Navigate to Administration (Gear Icon) > Manage Apps.
Upload the
.jaror.obrfile if you downloaded it manually, or confirm the installation from the Marketplace prompt.License Verification: Access the license settings within the Getint menu to apply your Marketplace license key.
4. User Access & Permissions
To manage integrations, users must be granted specific access through Jira Groups.
Admin Access: System Administrators see the "Getint" menu by default.
Delegated Access: To allow non-admin users to manage specific integrations, create a group following the naming convention:
getint-jira-[target-tool](e.g.,getint-jira-azure-devops).Service Account: We recommend using a dedicated "Service User" to establish the connection. This provides a clear audit trail in issue histories (e.g., "Updated by Getint Integration").
5. Key Comparison: Data Center vs. Cloud
Feature
Data Center (Native)
Jira Cloud (SaaS)
Hosting
Customer Infrastructure
Getint (AWS)
Data Storage
Local Database & JIRA_HOME
Getint Infrastructure
Cluster Support
Native Cluster Lock
Multi-tenant SaaS
Maintenance
Managed by Customer
Managed by Getint
External Access
Not Required (Firewall safe)
Required (SaaS model)
For organizations ready to begin their integration, you can initiate a 30-day free trial directly through the Atlassian Marketplace to evaluate the platform in your sandbox or production environment. If your deployment involves complex high-availability configurations or specific security requirements, you can schedule a technical consultation with a Getint specialist. For more information, feel free to contact us at our Help Center.
Last updated
Was this helpful?