Child pages
  • zAgileConnect for JIRA Data Center
Skip to end of metadata
Go to start of metadata

Background

zAgileConnect supports JIRA Data Center (JIRA DC) for customers who have deployed multiple JIRA Server instances in a cluster topology.  The key characteristics of this topology relevant for zAgileConnect, in the current JIRA DC implementation, are as follows:

  • Shared database across multiple JIRA instances
  • Replicated Lucene index between JIRA instances
  • Replicated internal cache between JIRA instances
  • Shared Attachment repository
  • Shared Plugin repository

The most critical of these is the replication of internal caches and index across multiple JIRAs.  zAgileConnect for JIRA DC is implemented to account for potential latency in these replication events.

To obtain the plugin for JIRA DC, please contact sales @ zAgile.com.  


 

Installation of zAgileConnect for JIRA DC


The installation of zAgileConnect for JIRA DC follows the same steps as that of JIRA Server.  There are a few additional configuration items (described below) to consider after the installation is completed.
To follow the steps to install zAgileConnect for JIRA Server, please follow the link: Installing zAgileConnect for JIRA Server

 

If you are upgrading zAgileConnect plugin for JIRA DC, please uninstall the existing plugin and reinstall the upgraded version. We have noticed inconsistent behavior in JIRA DC when directly upgrading the plugin.

 

Configuration of zAgileConnect for JIRA DC


To address concurrent updates to Salesforce from multiple JIRA instances, as well as to ensure that the updates are picking up the latest changes (accounting for latency in cache replication), zAgileConnect provides the following configurable options that may be tuned for your specific cluster topology:


 


Interval between successive issue events sent to Salesforce

This option determines the time interval between successive Issue updates sent to Salesforce.  In heavily active JIRA instances, the option to send updates every 'n' seconds reduces overall traffic to Salesforce.  All Issue updates are batched and applied to Salesforce in batches.  The default value is 10 seconds, implying that all Issue events within a period of 10 seconds will be sent as a single batch.


Delay interval between issue update event notification and Issue update in Salesforce

This option determines how often JIRA issue updates are sent to Salesforce.  In heavily active JIRA instances, the option to send updates every 'n' seconds reduces overall traffic to Salesforce.  All Issue updates are batched and applied to Salesforce in batches.  The default value is 10 seconds, implying that an issue update may take up to 10 seconds to be reflected in Salesforce.

Max number of issue events sent to Salesforce per request

In an active JIRA environment with multiple instances, it may be necessary to control how many updates may be sent to Salesforce in a single batch to maintain within Salesforce limits.  The default value is 75.



  • No labels