¿Is there any way to replicate the new workitems created into different repositories?
For example.
I have 3 different RTC servers. A and B
When i create a new workitem in repo A, i want this to be replicated into repo B automatically.
And it should be bidirectional, so if I modify it in repo B it have to be updated in repo A automatically too.
Is it possible ? ( i think it isnt)
¿Are any partner that provides a plugin with this functionality?
or maybe i have to write my own method to do this?
Thank you very much.
Accepted answer
It would be possible to create a custom synchronizer (similar to the ClearQuest Synchronizer) that does this. The API for synchronizers is available in the server as well as in the plain Java Client Libraries.
I am not aware that there is a RTC-RTC synchronizer. One of the partners that does synchronizer is TaskTop. they could be approachable if there is a business case to develop one.
Please note that this however exactly not what the Jazz Architecture approach is designed for. Duplication and synchronization is - as we know from all the history of tools and integrations - a bad idea. All kinds of problems can come up, especially mapping problems between the definitions of the processes on both ends, synchronization conflicts, blocks due to operational behavior. This is even problematic if the processes on both ends are stable it gets worse if they develop over time.
The Idea of CLM is to store the data only once and integrate on server/url level to avoid these problems.
I am not aware that there is a RTC-RTC synchronizer. One of the partners that does synchronizer is TaskTop. they could be approachable if there is a business case to develop one.
Please note that this however exactly not what the Jazz Architecture approach is designed for. Duplication and synchronization is - as we know from all the history of tools and integrations - a bad idea. All kinds of problems can come up, especially mapping problems between the definitions of the processes on both ends, synchronization conflicts, blocks due to operational behavior. This is even problematic if the processes on both ends are stable it gets worse if they develop over time.
The Idea of CLM is to store the data only once and integrate on server/url level to avoid these problems.
One other answer
It would be possible to create a custom synchronizer (similar to the ClearQuest Synchronizer) that does this. The API for synchronizers is available in the server as well as in the plain Java Client Libraries.
I am not aware that there is a RTC-RTC synchronizer. One of the partners that does synchronizer is TaskTop. they could be approachable if there is a business case to develop one.
Please note that this however exactly not what the Jazz Architecture approach is designed for. Duplication and synchronization is - as we know from all the history of tools and integrations - a bad idea. All kinds of problems can come up, especially mapping problems between the definitions of the processes on both ends, synchronization conflicts, blocks due to operational behavior. This is even problematic if the processes on both ends are stable it gets worse if they develop over time.
The Idea of CLM is to store the data only once and integrate on server/url level to avoid these problems.
I am not aware that there is a RTC-RTC synchronizer. One of the partners that does synchronizer is TaskTop. they could be approachable if there is a business case to develop one.
Please note that this however exactly not what the Jazz Architecture approach is designed for. Duplication and synchronization is - as we know from all the history of tools and integrations - a bad idea. All kinds of problems can come up, especially mapping problems between the definitions of the processes on both ends, synchronization conflicts, blocks due to operational behavior. This is even problematic if the processes on both ends are stable it gets worse if they develop over time.
The Idea of CLM is to store the data only once and integrate on server/url level to avoid these problems.