Yes, once you have specified that a given file or folder should be
synchronized in a given sync stream, changes to that file or folder
(or any file/folder that is a member of that folder) should be
automatically detected and synchronized. (If this isn't happening, it
is a bug).

In particular, you shouldn't have to select those files and folders
again, in order to get them synchronized.

To confirm that the changed files were really in your list of
files/folders to be synchronized, could you invoke the "select
files/folders to synchronize" operation on your sync stream, and
verify that the list of files/folders you see listed there actually
contain the files that were changed?

Cheers,
Geoff
Ralph Schoon wrote:

Hi,

I am working with RTC and CC at a customer and I am a bit confused
about
the usage model.
The help does not really help me. TN0006: Deploying Rational Team
Concert into a ClearCase/ClearCase Environment is good to get
started,
but I am missind some vital information.
We are running base cc and RTC

We were able to synchronize RTC with ClearCase. Once we had that
running, we did some changes in RTC and some in CC.
We delivered the changes to the synchronized stream.
We re-ran the synchronization which finalized in an impressing time.
We
checked and could see no files where touched.
As a summary the only time we saw changes coming in and going out
where when we explicitely selected directories to be synchronized.

My assumption was the synchronization once set up would automatically
detect changes in files under synchronization.
Is that assumption wrong?
In addition I browsed the help and some material available "How would
users work" with synchronization. But frankly that did not help me
much. Especially clarifying the questions above. My strategy would be
right now:

1. Not submit any changes to the synchronized stream during
development
- develop on some integration stream.
2. When integration with changes in CC is needed, import changes to
RTC
using "Select files to synchronize" selecting the root folder.
3. Change flow target to synchronized stream.
4. Resolve conflicts and merge.
5. Synchronize out selecting the root folder in "Select files to
synchronize".
Any best practices already known?

Thanks,

Ralph

One confusion that I have seen is someone selecting a file/folder to
be synchronized in one sync stream, and then performing a sync in
another sync stream ... each sync stream has its own list of
files/folders to be synchronized.

But it could of course be a bug (:-).

Cheers,
Geoff
Ralph Schoon wrote:

Thanks Geof,

this is very helpful. We checked several times that the folders to be
synchronized indeed represented the main folder representing the vob.
In our case the files/folders are di_swep/di_swep (di_swep
representing
the vob).
I will try to steal some time next week at the customers site to
verify
the behavior against what is expected. If I can reproduce that I will
open a workitem.
Ralph
Yes, once you have specified that a given file or folder should be
synchronized in a given sync stream, changes to that file or folder
(or any file/folder that is a member of that folder) should be
automatically detected and synchronized. (If this isn't happening,
it is a bug).

In particular, you shouldn't have to select those files and folders
again, in order to get them synchronized.

To confirm that the changed files were really in your list of
files/folders to be synchronized, could you invoke the "select
files/folders to synchronize" operation on your sync stream, and
verify that the list of files/folders you see listed there actually
contain the files that were changed?

Cheers,
Geoff
Ralph Schoon wrote:
Hi,

I am working with RTC and CC at a customer and I am a bit confused
about
the usage model.
The help does not really help me. TN0006: Deploying Rational Team
Concert into a ClearCase/ClearCase Environment is good to get
started,
but I am missind some vital information.
We are running base cc and RTC
We were able to synchronize RTC with ClearCase. Once we had that
running, we did some changes in RTC and some in CC.
We delivered the changes to the synchronized stream.
We re-ran the synchronization which finalized in an impressing
time.
We
checked and could see no files where touched.
As a summary the only time we saw changes coming in and going out
where when we explicitely selected directories to be synchronized.
My assumption was the synchronization once set up would
automatically
detect changes in files under synchronization.
Is that assumption wrong?
In addition I browsed the help and some material available "How
would
users work" with synchronization. But frankly that did not help me
much. Especially clarifying the questions above. My strategy would
be
right now:
1. Not submit any changes to the synchronized stream during
development
- develop on some integration stream.
2. When integration with changes in CC is needed, import changes to
RTC
using "Select files to synchronize" selecting the root folder.
3. Change flow target to synchronized stream.
4. Resolve conflicts and merge.
5. Synchronize out selecting the root folder in "Select files to
synchronize".
Any best practices already known?
Thanks,

Ralph