Exalate uses a groovy-based scripting engine to implement filtering, transformation and mapping. Even though scripting like that is more complex than a drag and drop interface, it is the only way that makes even the most complex mapping possible to implement. See how the most complex use cases can be implemented using the synchronization processors.
Yes. Right now, Exalate is compatible with JIRA Server, JIRA Cloud and HP QC ALM. We are working on the integration with other issue trackers.
Exalate is available for JIRA Server, JIRA Cloud and HP/QC ALM.
Synchronizing is unlimited between any of these platforms as long as Exalate is installed on each instance. We provide 2 licensing models:
- Instance licensing - the model, where each instance requires a valid license to synchronize.
- Network licensing - the model where only one side pays for the synchronization between instances.
When connecting to the Exalate network, you are able to synchronize as long as your remote partner is fully paying for the synchronization using the Exalate network license.
You can install the app unlicensed and keep the License Key field empty in this case.
Exalate is already in use since 2014 at different enterprises. One of our customers processes on average 12000 issues / month without significant impact on the overall instance
There are no limits to sending information using the customKeys property of a replica. It allows to send any arbitrary object which will get serialized at one end and deserialized at the other.
Yes, it is possible to synchronize an issue from A to B and then from B to C, thus creating a chain of synchronized issues.
Yes. A hubissue is representing standard fields but also a whole set of objects of comments, attachments ...
For instance. it is possible to list all the added and removed comments using the correct properties. Check what is contained in a replica.
When an instance requests another instance to send over the content of an attachment, the other instance will respond with an hash key calculated from the content of the attachment. The same hash key is calculated on the receiving end to ensure that the received content matches the original attachment. The download will be retried once to avoid transmission errors. Failing this second attempt an error is raised and the administrator is notified.
There are 2 different situations to be considered
Any new issue brought under sync will be synchronized normally
All issues under sync will require a 'calibration phase' which allows to bring the synchronization back into shape.
Every replica of an issue is stored on 2 systems. A replica is the result of the transformation of an issue into a hub issue (through the datafilter) This replica is stored:
on the source tracker to detect if relevant changes have been made since the last synchronization
in the destination tracker to provide the content of the previous version.
The distributed architecture of the synchronization engine allows to upgrade either end as appropriate. The common hub issue model ensures that the synchronization information can be translated to the local context.
Yes - the synchronization panel will detail out all information relevant to the synchronization.
Optionally. The application administrator can configure how links to the remote issue are represented. Either as JIRA issue link, as a weblink in the synchronization panel or not at all.
Not yet - we are working on it. When staging exalate 1.3 or earlier, make sure that synchronization engine is not triggered by deactivating all instances.
When you delete an issue Exalate consider it as a synchronization event. It triggers a number of events which ensure that future synchronization events are not processed anymore. The synchronization panel will indicate that the remote issue has been removed.
Not at all - every application administrator can define how 'hubissues' are translated to the local context.
No - the intermediate layer is taking care to transport whatever information the originating tracker wants to share. It is up to the other side to take it into account.
In 3.2.1 release subscriptions page was hidden. But the page is still there. You can access it using this kind of link :
Yes, it is possible. Both on Jira Server and on Jira Cloud, you can use either an issue operation (menu item in the More drop-down)or even configure workflow for the issue to put it under synchronization when certain transition is performed( Exalate Post-function).
Exalate has a built in scripting engine to implement almost any use case in a flexible way. Check our use case examples for more details.
From JIRA to HP: Changes are processed almost immediately, depending on the number of outstanding synchronization requests.
From HP to JIRA: The exalate application is querying the HP application every 5 seconds for any new change, and processes these (using a single thread). If the number of changes requires more processing time than 5 seconds, the next cycle is run immediately.
From JIRA to JIRA: Changes are processed almost immediately, depending on the number of outstanding synchronization requests.
When the issues get synced, you can select whether users see a link to those remote issues or not. The admin has the option to decide if the users can have direct access to the issue they are connecting.
This is a set of scripts, where we define the data we want to synchronize and the reaction when we receive the synchronization data. Every script has its purpose.
Data filter defines what your instance sends during synchronization(how a message is created). Create Processor tells how would an issue get created due to the first message from the remote Instance.
Change processor tells how would an issue change due to a subsequent message from the remote Instance.
Atlassian requires that any 'add-on' technology runs on a separate server. This is called Atlassian Connect.
Relevant data for the functioning of the add-on will be exchanged with the vendors' servers. The same applies to Exalate.
Whenever an issue is updated, a webhook will be called. It triggers the Exalate logic to collect all relevant data such as specified in the outgoing processor (Data Filter).
This communication is secured via https and JWT.
In case the Destination side is on the private network the issue data resides on the Exalate Cloud servers until the destination Jira instance requests for any changes. These changes will then be sent to the Jira Server - and that communication is normally also secured via https. The information on the Exalate cloud server is removed.
In case the Destination side is publicly accessible the issue data resides on the Exalate Cloud server until the app filters and processes changes. These changes will then be sent to the Destination Jira Instance - and that communication is normally also secured via https. The information on the Exalate cloud server is removed.
Contrary to the common implementation model as prescribed by Atlassian, Exalate cloud apps are single tiered.
Meaning - that the operation and handling of the data is fenced from any other interference.
The consequence is that the data center compatibility label for our add-ons (Exalate for Jira server, Table Grid Editor for Server, Pivot Gadget) have been revoked.
What does it mean for your environment in case you use the add-on on a Jira Data Center?
There is no impact on your environment. These add-ons have successfully been used for a couple of years in data center environments.
When do you expect to be compliant to the new requirements
We expect to have Data Center compliant add-ons in the course of Q4 2018.
Find more information on the Atlassian blog.
Thanks to the distributed model, it is possible to adapt the common hub issue to the local context. For instance, if your local workflow evolves, you will be able to change the create and change processors to take into account the new configuration.
Exalate is based on a distributed model where each application administrator configures what information can be send and how incoming messages must be handled. All messages exchanged between the nodes are based on a common defined 'hubissue' which carries all information one application administrator wants to communicate to the other side. The processors will use this information to apply the changes to the local issues.
Absolutely. The synchronization panel shows all relevant details - even if the remote issue has been removed.
Yes. Thanks to the groovy goodness, one can parse the newly added comments and trigger a resolve transition
A scenario we encounter regularly is the service desk use case where tickets raised by a customer need to be raised internally in different projects - depending on the set of properties. One use case was particularly interesting. The target project depended on 3 different properties resulting in 200+ potential permutations. This mapping is stored in a single database table.
The way we solved it involved finding the right projectkey in the database table and use it to raise the issue in the right project. Check following example showing how such configuration can be set up using Exalate.
The synchronization engine is processing sync events sequentially (for the moment - November 26. 2016). Processing 10000 issues in 100 different projects might take a couple of hours. We have been synchronizing 10k+ issues as part of our performance tests and we are looking at increasing the processing speed to meet the challenge that one of our prospects is facing.
Yes. Each integration point can evolve as long as the hub issue model and exalate api is respected.
This happens immediately. Exalate is based on a fully event-driven engine Whenever a user changes some information (and that information needs to be sent), a sync event is generated containing a snapshot of the modified issue - ready to be sent to the remote instance. When 10 issues are changed, or 1 issue 10 times at the same moment (it does happen) - 10 events are generated.
The replication layer in the exalate architecture will transmit each sync event to the remote instance, triggering a sync request, which is processed at its own pace.
Handling a full synchronization event takes a couple of seconds (give / take the size of the information to be transmitted)
Whenever an error occurs, a detailed overview (= stack trace) leading to the problem is raised. In case this is not sufficient, one might create a support.zip and send it to firstname.lastname@example.org for further processing.
Since Exalate is an app for different deployments of Jira (Server, Cloud, Data Center) and other platforms, we do not attempt to ensure that our application is compatible with all third-party reverse-proxy solutions that might be set up on the Jira host.
However, we've tested it with nginx, and we can state that Exalate is compatible with nginx as a reverse-proxy server.
The group of exalate administrators will be notified in 2 different ways
by email with the details of the error notification
In JIRA - by using 'In-JIRA' notifications - popping up a warning about the blocking error
Also, errors are generated at 4 different levels.
As an example - when the proxy user is not allowed to modify the local issue due to issue security
Typical example - when there is an error in the processor scripts, or when there is a permission problem to apply changes to an issue
A connection problem
Bugs in the synchronization layer.
Yes, it's possible to sync multiple projects with one connection.
Basically, it's all about the configuration of the Sync Rules. Once that you establish a connection between instances you can specify which data would you like to send to the other side and how to interpret incoming sync data.
The Data Filter of the sending side interacts with Create and Change Processor of the receiving side.
For more details, please check the synchronization processors.
Versions and pre-requisites
Currently, Exalate supports JIRA Core, JIRA Service Desk, JIRA Data Center, JIRA Software, JIRA Cloud, HP ALM. We are working on some other issue trackers to be compiled with Exalate
All editions of JIRA (Core, Software, Service Desk) and platforms (Server, Datacenter and Cloud). Server and datacenter supported from JIRA 6.3 and up.
We are validating against HP ALM 12.02, and 12.50.
For now only HP ALM defects could be synchronized.
For JIRA Server: Exalate is an Atlassian add-on, which can be installed as any other add-on. Synchronization information is stored in the JIRA database. The memory footprint is limited and should not require any modification from the existing setting. In case of doubt, adding 128MB to your jvm settings should be sufficient.
You will be required to configure a single JIRA user, which will be used to access the issues to be synchronised
Exalate also requires a SMTP server to raise notifications in the case of errors. For this SMTP a hostname, userid and password are to be provided in case outgoing mail requires authentication
For JIRA Cloud: Exalate is an Atlassian add-on, which can be installed as any other add-on. Synchronization information is stored in the JIRA database.
For HP ALM: Exalate is delivered as an external application which interfaces with HP through the REST API. You will need following:
A host which can run the application
The application is delivered either as a RPM (centos) or as a docker image (many platforms)
In the case of an RPM, a postgresql 9.4 database needs to be deployed on the host
The exalate application needs to have access on the HP ALM application (for reading and writing)
In 4.0 version we've introduced Connection and Invitation concept that includes changes to the User Interface.
The configuration is simplified now. What we used to call Instances and Relations is now merged into Connections.
The Connection includes information from the Instance and a Relation, based on that Instance.
In Exalate 4.x, there is no need to share access credentials anymore, even if your instance requires authentication.
Starting from 4.0.0 version in the Exalate app for JIRA Server, 4.1.0 in the Exalate app for JIRA Cloud and 2.0.0 in the Exalate app for HP QC/ALM, Exalate is using a new security approach.
Below you can find answers to the most common security questions.
No, the invitation could be applied only to the invited side. It includes an Invitation code that helps to secure Connection data.
Once the Connection set-up is finished, Exalate generates the shared secret. The secret is used to define a secure connection between both Instances.
It is shared only once to generate a JWT token. The token is temporary and is generated for every communication request between Exalate on both Instances.
The following information is exchanged between Instances:
- shared secret;
- information about the type of the connection with the Destination instance;
- Connection name;
- information about the Connection initiator
- Exalate app version, including supported features
- Instance type and version ( JIRA Server, JIRA Cloud or HP QC/ALM)
- Instance URL and Exalate URL
- Instance UID, which is a unique instance identifier
The JWT token generates on every communication request between Instances. It authenticated the request so the destination side can be sure they are getting data from the expected Instance.
Instance URL, Instance version, Exalate URL, a unique instance identifier.
For more details check Atlassian security overview.
On the configuration stage of the Exalate app for HP QC/ALM you need to specify HP QC /ALM Instance(issue tracker) user and password. The credentials are used to communicate with the HP QC/ALM Instance.
Debugging Sync scripts on Exalate for Jira Server — Sometimes you need to have a closer look at synchronization scripts to find out whats wrong. This article shows how to investigate the Exalate errors.