I'd like to know the same. Additionally can someone describe the purpose of the CLONE and INTERNAL workspaces that get created?

This is documented in the on-line dynamic help in the "Resolving
conflicts during synchronization" section. In particular, this section
tells you about the "merge workspace" (owned by the team member that
resolves conflicts between the Jazz and ClearCase streams) and the
read-only "CLONE workspace" (which holds the pending changes from
ClearCase when there are conflicts to be resolved).

There is also an "INTERNAL workspace", but you don't need to know
anything about that (fyi, it is the workspace which the synchronization
algorithm uses to try to auto-merge changes from Jazz and ClearCase).

WRT Daan's question, changes from/to CC go through the synchronized
stream, not through the jazz-clearcase-workspace. The
jazz-clearcase-workspace is the place where you resolve any merge
conflicts between jazz and clearcase (see the on-line dynamic help for
details).

Cheers,
Geoff

dvdmunni wrote:

Where can we find some documentation on the inner-workings of the CC
connector ?

We have set up the CC connector and it is working fine, however the
use of the different workspaces/streams by the connector is not
entirely clear.

We have:
jazz stream = ProjectX_Jazz2CC
jazz clearcase workspace = ProjectX_Jazz2CC Sync Workspace

Next we do:
- create a workpace from the jazz-stream (ProjectX_Jazz2CC Workspace)
- change a file in this workspace and deliver the change
- do some changes in clearcase
- synchronise with clearcase

The effect is:
- Jazz changes are visible in clearcase (as expected)
- CC changes are available as incoming changeset on my
ProjectX_Jazz2CC Workspace (as expected)
- jazz and CC changes are NOT accepted in the
jazz-clearcase-workspace

The last point puzzles me, as I would have expected that all changes
from/to CC would go via the jazz-clearcase-workspace ?

thanks

Daan.