Another use case is synchronization between Jira Cloud and Jira on-premise instances, where the Jira on-premise instance is behind the firewall and is not accessible from the outside network.
The Exalate App is able to handle this type of communication between instances and synchronize issues either in a uni- or bi-directional manner.
In such cases, only the private instance can initiate the network traffic to the public one. With the help of the Exalate app, you can sync issues between instances even if one of them is not accessible from the public network.
How is the traffic different between public and private instances?
Example
You have two Jira instances. One is a private instance (is not accessible from the outside network) and the other is a public instance.
Let's call the private instance Internal and the public instance External. Only the Internal instance can initiate network traffic to the External instance.
You want to exchange data between the InternalProject and ExternalProject that are present on the internal and external Jira instances respectively.
Below you can see the configuration steps to set up the synchronization.
Configuration Steps
- Set up a Connection from the External Instance.
- Click 'I don't have a URL'.
Exalate suggests available connection types based on the destination instance's version of Exalate. - Select the proper connection type as shown below
You can choose between Basic or Script configuration modes, since Visual configuration is only allowed in Public connections. - Complete other steps from the connection wizard.
- Click 'I don't have a URL'.
- Send an Invitation to the Destination Instance.
- Make sure the Destination side has accepted the invitation.
- Synchronize issues.
For more information, please read the getting started guide.