It's all about the answers!

Ask a question

Synchronization Rules - what do they do under the covers?


David Doughty (1812119) | asked Sep 27 '10, 10:15 a.m.
3rd party integrations to Rational Team Concert use the Synchronization Rules to allow 3rd party products to share records (this is a simple enough model to understand).

With the sync rules is someone able to tell me what the effect is of disabling the automatic outgoing synchronisation?

Is this a good idea, what if there is no out oging synchronisation needed or wanted, or do you still need to allows outgoing sync, and turn off the field mapping so that there is nothing going out?

My thoughts are that RTC will create outgoing "packets" but do nothing with them. Therefore these packets will be created within the RTC database, and will remain until they are sync'd out. Which will continue for each record created that would normally be sync'd out. Which is a bad thing, because you end up with a database full of outgoing messages, going nowhere.

Does anyone know if this is what happens? is there also an over head for RTC for holding these messages? Does it try and repeatidly process these messages? I assume not, as it appears to be a manual operation once the automation fails or is deliberately not run.

If anyone can offer any further insight to the operation of the synchronizer that would be most helpful.

thanks

dD

2 answers



permanent link
Geoffrey Clemm (29.5k23035) | answered Sep 28 '10, 12:15 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One reason you want to enable outgoing synchronization is that
otherwise, any incoming change to a modified field will be blocked as a
conflict, and require manual intervention to resolve. It is fine to
ignore some (or most) of the fields in both repositories, but for the
fields that aren't being ignored, you'll want to have synchronization
rules acting in both directions for those fields, to avoid these
blocking conflicts.

Cheers,
Geoff

On 9/27/2010 10:23 AM, ddoughty wrote:
3rd party integrations to Rational Team Concert use the
Synchronization Rules to allow 3rd party products to share records
(this is a simple enough model to understand).

With the sync rules is someone able to tell me what the effect is of
disabling the automatic outgoing synchronisation?

Is this a good idea, what if there is no out oging synchronisation
needed or wanted, or do you still need to allows outgoing sync, and
turn off the field mapping so that there is nothing going out?

My thoughts are that RTC will create outgoing "packets" but
do nothing with them. Therefore these packets will be created within
the RTC database, and will remain until they are sync'd out. Which
will continue for each record created that would normally be sync'd
out. Which is a bad thing, because you end up with a database full of
outgoing messages, going nowhere.

Does anyone know if this is what happens? is there also an over head
for RTC for holding these messages? Does it try and repeatidly
process these messages? I assume not, as it appears to be a manual
operation once the automation fails or is deliberately not run.

If anyone can offer any further insight to the operation of the
synchronizer that would be most helpful.

thanks

dD

permanent link
Lorelei Ngooi (1.5k22) | answered Sep 28 '10, 9:39 a.m.
JAZZ DEVELOPER
Also, if you don't enable outgoing sync, then changes made on RTC work items will never be reflected back to the external repository.

Regarding the implementation of outgoing sync, no outgoing "packets" are created and accumulated as a result of outgoing sync not occurring. Please see http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.connector.cq.doc/topics/c_how_items_candidates_outgoing_synch.html for more info.

Your answer


Register or to post your answer.