It's all about the answers!

Ask a question

RTC synchronization rules between prod and test environments


Michael Mancini (1362410) | asked Aug 05 '11, 1:10 p.m.
Has anyone used RTC synchronization rules to work across other RTC environments? An example of what I'm looking for is to synchronize all work items from our production environment to other test environments so that all data is replicated.

3 answers



permanent link
Ralph Schoon (63.6k33647) | answered Aug 08 '11, 4:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Michael,

I am not aware that that is possible. I don't think there is a RTC to RTC synchronizer.

Can you elaborate on the requirements? I am not sure what you mean with test environment. If it would be an RTC test environment you could potentially use CSV export/import to get some useful data into the test environment. Another way would be to recreate the environment from backups. Please be aware that the test environment in this case would have to be isolated because the URL's of both systems would be the same.

permanent link
Michael Mancini (1362410) | answered Aug 08 '11, 8:23 a.m.
Hi Michael,

I am not aware that that is possible. I don't think there is a RTC to RTC synchronizer.

Can you elaborate on the requirements? I am not sure what you mean with test environment. If it would be an RTC test environment you could potentially use CSV export/import to get some useful data into the test environment. Another way would be to recreate the environment from backups. Please be aware that the test environment in this case would have to be isolated because the URL's of both systems would be the same.


Hi Ralph - The requirements are simple in the fact that all I am looking to do is easily sync two environments, one being the live production environment and the other being a test environment. I know that the synchronizer isn't meant for RTC --> RTC communication, but if it can be used to keep even a daily sync of work items over to our test environment that would be helpful. We used a repotools export/import to migrate the bulk of data over, but we still would like more relevant work item information going forward and if there is an automated way (with the synchronizer) of completing this task I would like to utilize it.

permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 08 '11, 6:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The CQ Synchronizer is based on the Item Synchronizer, which uses an
Item Manager to synchronize work items in RTC with that Item Manager. So
you'd need to write an Item Manager for RTC to get an RTC/RTC
Synchronizer. That is not something in-plan for RTC, but the source
code for the Item Manager is part of the RTC SDK, so one could try to
write it oneself.

Cheers,
Geoff

On 8/8/2011 8:53 AM, mmancini wrote:
rschoonwrote:
Hi Michael,

I am not aware that that is possible. I don't think there is a RTC
to RTC synchronizer.

Can you elaborate on the requirements? I am not sure what you mean
with test environment. If it would be an RTC test environment you
could potentially use CSV export/import to get some useful data into
the test environment. Another way would be to recreate the
environment from backups. Please be aware that the test environment
in this case would have to be isolated because the URL's of both
systems would be the same.

Hi Ralph - The requirements are simple in the fact that all I am
looking to do is easily sync two environments, one being the live
production environment and the other being a test environment. I know
that the synchronizer isn't meant for RTC --> RTC communication,
but if it can be used to keep even a daily sync of work items over to
our test environment that would be helpful. We used a repotools
export/import to migrate the bulk of data over, but we still would
like more relevant work item information going forward and if there
is an automated way (with the synchronizer) of completing this task I
would like to utilize it.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.