CC connector use cases
I have these use cases for the CC connector. Can you help answer how Jazz will address them? I will add more later.
1. Check in/out of documents or files in Jazz or CC UCM repository. Change in one gets reflected in the other repository in a timely manner. 2. Execute same peer review process of design documents in either repository. 3. Jazz and CC UCM enforce the same project level security (e.g. project A users can not see project B files, etc.). 4. Users can use Jazz web interface to access CC artifacts in a WAN environment without performance issues. 5. Support synchronization of any artifact from CC regardless it is a Eclipse project or not (for example, we store design documents in UCM components, we have .NET project, etc.). 6. Support the ability to check in/out synchronized CC files (e.g. documents and not limited to source code) in the Jazz web UI. |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 13 '07, 8:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
gdang wrote:
I have these use cases for the CC connector. Can you help answer how The versions currently selected by a particular stream get transferred between Jazz and CC when a "synchronize" operation is executed. In beta2, you define the frequency with which a synchronize happens using the "Schedule Synchronization" operation in the ClearCase Workspaces view. Normally, this would be run once a night (the ClearCase stream is locked during the synchronize operation). It could be scheduled more frequently, but a synchronize operation place a load on the ClearCase server, so you don't want it running continuously, especially if you are synchronizing a large number of streams).
Yes, but I don't see how this relates to the ClearCase Connector. Perhaps you could expand on this a bit? 3. Jazz and CC UCM enforce the same project level security (e.g. In beta2, Jazz security is mostly focused on controlling who can write to the repository. Read protection is primarily at the repository level. For 1.0, this should be enhanced by finer-grained read-protection. Note that the primary interaction between the ClearCase Connector and Jazz or CC is that the sync operation runs as a particular user (defaults to "ccsync" but can be customized for each stream). So the sync will fail if the ccsync user does not have sufficient read/write privileges to perform the sync. 4. Users can use Jazz web interface to access CC artifacts in a WAN Jazz does not provide any new web interface to CC artifacts, but the Jazz client does include an embedded web browser page, so you can use that browser to access any existing web interfaces to ClearCase. 5. Support synchronization of any artifact from CC regardless it is a This is workitem 30924, currently scheduled for M5 6. Support the ability to check in/out synchronized CC files (e.g. See answer to #4. |
Yes, but I don't see how this relates to the ClearCase Connector. Perhaps you could expand on this a bit? - currently, we have custom peer review record types in CQ that allow reviewer to review design documents. How can I do that in the Jazz interface? Do I need to synchronize those record types as Jazz workitem? Even then, I am not sure how Jazz and CQ connector synchronize the workflow state? 3. Jazz and CC UCM enforce the same project level security (e.g. In beta2, Jazz security is mostly focused on controlling who can write to the repository. Read protection is primarily at the repository level. For 1.0, this should be enhanced by finer-grained read-protection. Note that the primary interaction between the ClearCase Connector and Jazz or CC is that the sync operation runs as a particular user (defaults to "ccsync" but can be customized for each stream). So the sync will fail if the ccsync user does not have sufficient read/write privileges to perform the sync. - what I am trying to ask is that today, CC allows you to use domain group access control to secure the VOB such that the VOB is secured by project group. How is this security mechanism work in Jazz world. I am trying to understand the Jazz project security model and how the replicated/synchronized cc objects are secured on the Jazz side. 4. Users can use Jazz web interface to access CC artifacts in a WAN Jazz does not provide any new web interface to CC artifacts, but the Jazz client does include an embedded web browser page, so you can use that browser to access any existing web interfaces to ClearCase. - are you refering to http://<server>/jazz/web? Does this interface allow me to "check in/out" the replicated CC object in the jazz repo? |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 04 '08, 5:48 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
gdang wrote:
2. Execute same peer review process of design documents in either All reasonable questions, but CQ Connector (not CC Connector) issues, correct? I'll start a new thread on this topic (I'll title it "Using the CQ Connector for a peer review process"). 3. Jazz and CC UCM enforce the same project level security (e.g. The synchronized CC objects are stored in the Jazz repository as if they were created by the user performing the synchronize. For a discussion on the Jazz security model, let's start a separate thread (since it is independent of the CC Connector). 4. Users can use Jazz web interface to access CC artifacts in a WAN Ah, I misunderstood your question ... I thought you were asking how to access the (original) CC artifacts, but you were instead asking about how to access the (replica/clone) of the CC artifact in the Jazz repository. Since the replica/clone of the CC artifact is just a standard Jazz SCM artifact, you'd access them the same way you'd access any other Jazz SCM artifact. In beta2, there is initial support for web access to Jazz SCM artifacts. See the "New source control web UI" topic in the beta2 "New and Noteworthy" page: <https://jazz.net/downloads/DownloadDocument.jsp?href=betas/data/0.6Beta2/jazz-news-0.6Beta2-part1.html> Cheers, Geoff To access the Jazz clone of the CC object, y |
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.