> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/getting-started-with-the-platform/deployment-options/getting-started-with-the-platform-deployment-options-getint-for-jira-data-center-jira-server/getint-jira-server-jira-data-center-app-native.md).
# Getint Jira Server / Jira Data Center App (Native)
### Overview
Getint for Jira Server and Jira Data Center is installed directly in Jira as a native Atlassian application.
The application runs within your Jira environment and stores its configuration in the Jira database. Synchronization jobs are executed by Jira and do not require a separate Getint-managed service.
This deployment model is commonly used by organizations that require:
* Local infrastructure control
* Internal network connectivity
* Data residency requirements
* Restricted outbound access
* Jira Data Center deployments
* Self-managed environments
### Installation from Atlassian Marketplace
1. Open **Administration** → **Manage Apps**.
2. Select **Find new apps**.
3. Search for the required Getint application.
4. Install the application.
5. Apply the license if required.
After installation, the Getint administration section becomes available in Jira.
### Licensing
Getint licenses are managed through Atlassian Marketplace licensing.
To verify the current license:
1. Navigate to **Administration** → **Manage Apps**.
2. Locate the installed Getint application.
3. Review the license status.
If the license expires, synchronization jobs may stop running depending on the licensing model.
### Configuration Storage
Getint stores integration configuration and synchronization metadata in the Jira database.
No separate database is required.
The application creates dedicated tables for:
* Connections
* Integrations
* Synchronization records
* Processing status
* Execution history
* Error tracking
* System configuration
The exact table names may vary between application versions.
### Scheduled Jobs
Getint uses Jira scheduled services to execute synchronization tasks.
These jobs are responsible for:
* Running integrations
* Processing synchronization queues
* Cleaning up historical data
* Updating synchronization status
### Logs
Getint creates dedicated log files for troubleshooting and operational monitoring.
#### Log Location
The application stores logs in:
```
JIRA_HOME/log/getint
```
If the Jira environment does not contain a log directory, Getint creates:
```
JIRA_HOME/getint
```
#### Log Contents
Logs may contain:
* Synchronization activity
* API requests and responses
* Processing statistics
* Error details
* Diagnostic information
Support may request log files during troubleshooting.
### Data Retention
Synchronization activity generates database records and log entries over time.
Administrators can configure retention periods to control storage growth.
{% hint style="warning" %}
Logs are retained for 14 days by default. You can adjust the retention period to a shorter or longer duration based on your organization's requirements.
{% endhint %}
#### Cleanup Process
A background cleanup job periodically removes:
* Historical synchronization records
* Old execution logs
* Expired processing data
Retention settings can be configured from the Getint administration section.
### Performance Considerations
Synchronization performance depends on several factors:
* Jira server resources
* Database performance
* Integration complexity
* Number of synchronized records
* API limitations of connected systems
For larger deployments, monitor:
* CPU utilization
* Memory consumption
* Database growth
* Synchronization duration
### Testing
Before deploying integrations in production, validate the configuration in a testing environment.
Recommended validation activities include:
* Connection testing
* Authentication verification
* Field mapping validation
* Synchronization rule testing
* Permission verification
Testing helps identify configuration issues before production use.
### Upgrade Process
Application upgrades follow the standard Atlassian Marketplace process.
Before upgrading:
1. Review release notes.
2. Create a Jira backup.
3. Verify compatibility with your Jira version.
4. Test the upgrade in a non-production environment when possible.
### Uninstallation
Removing the application stops all Getint synchronization jobs.
Administrators should review:
* Existing integrations
* Historical synchronization data
* Log files
* Database records
Depending on organizational requirements, additional cleanup may be performed after uninstallation.
For deployment planning, security reviews, or support questions, contact the [Getint team](https://getint.io/help-center).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.getint.io/getting-started-with-the-platform/deployment-options/getting-started-with-the-platform-deployment-options-getint-for-jira-data-center-jira-server/getint-jira-server-jira-data-center-app-native.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.