2) In my project there are 3 teams handling each section of the
project. So I would like to know is it suffecient to create 3 Team Areas
within a Project Area to segregate the teams from each teams work.

This is appropriate if your teams want to follow a common process (e.g.
shared roles and permissions), if they want the same workitem
configuration, and if they should all have the same read access to
artifacts in the project area (more on this below).

3) How to restrict the viewability of one team's work from that of
other's in RTC.

You can configure read access in RTC for each project area, but you
cannot configure it for each team. If your teams should not be able to
view each other's work, you would probably be better off using separate
project areas.

- Jared
--------------------
Jazz Team Process

For all you ClearCase users, here's a page you might want to bookmark in
the online help for Rational Team Concert.

Cheers,
Geoff

---------------------------

Integrating > Rational Team Concert and Rational ClearCase > Using the
ClearCase Connector for Rational Team Concert source control

Jazz concepts for Rational ClearCase users

An understanding of how certain Rational Team Concert source control
concepts relate to similar ones in Rational ClearCase can help
Rational ClearCase users adapt to using Rational Team Concert source
control.
For a concise overview of Jazz terminology and concepts, see the Quick
reference or the Overview of Rational Team Concert source control.

In Jazz, a version-controlled file or folder is called a "versionable
item," which is analogous to an element in a VOB.
A versionable item is modified in the context of a "repository
workspace," which is analogous to a UCM development stream or a base
Rational ClearCase private branch. Changes you make in a repository
workspace are private to that workspace until you deliver them.
A projection of a repository workspace onto the local file system is
called a local workspace. A local workspace is analogous to a Rational
ClearCase view. If you are using the Eclipse client, the local workspace
is an Eclipse workspace. Any file or folder in the local workspace can
be modified, so there is no explicit checkout operation. This behavior
is similar to the auto-checkout behavior provided by existing Rational
ClearCase plug-ins for Eclipse. When you check in a file or folder, it
is assigned to a change set, which is analogous to the change set of a
UCM activity.
A Jazz stream tracks the history of a collection of "versionable items,"
and is analogous to a UCM integration stream.
When you are ready to make changes you have made in a workspace
available to other team members, you deliver them to a stream, just as
when changes made in a UCM development stream are ready to be seen by
other team members, you deliver them to a UCM integration stream.
When you want to record a particular configuration of a workspace or
stream, you create a "baseline" in that workspace or stream, just as you
create a UCM baseline in a UCM development or integration stream. Unlike
a UCM baseline, which is fixed to the stream in which it is created, a
Jazz baseline can be delivered from a workspace to a stream.
When you are ready to see the changes that have been delivered to a
stream, you accept those changes into your workspace. This is analogous
to rebasing a UCM development stream to see the changes that have been
delivered to a UCM integration stream. The accept operation lets you
accept all the changes from the stream, or a selected baseline from a
stream, just as the UCM rebase operation lets you specify the latest
configuration of the UCM integration stream, or a selected UCM baseline
of the UCM integration stream.
An accept operation can introduce conflicts, just as a UCM rebase can
introduce conflicts. Rational Team Concert source control provides merge
tooling to help resolve these conflicts.
A work item specifies issues to be addressed (for example, product
enhancement or defect-fixing requests), and is analogous to a
ClearQuest-enabled UCM activity. In particular, like a
ClearQuest-enabled UCM activity, a work item allows you to associate a
change set with a particular enhancement or defect fix, and to track
that change set as it flows through the overall development effort.
A project area defines a process and set of policies that apply to all
streams and work items in the project area, and is analogous to a UCM
project with its project policies.


On 5/20/2010 1:52 AM, gayatrivikram26 wrote:

Hi

I am very new to RTC and have gone through the Essentials of RTC
V2.0 book. I my role is to implement RTC in my project. I have
certain couple of queries. I was a ClearCase admin for quite a long
time and I am getting confused when I here the same terms like
stream, component etc in RTC.

1) I would like to know the actual function of stream and component
in RTC.
2) In my project there are 3 teams handling each section of the
project. So I would like to know is it suffecient to create 3 Team
Areas within a Project Area to segregate the teams from each teams
work.

3) How to restrict the viewability of one team's work from that of
other's in RTC.

4) I have a folder structure created in the Windows Explorer in my
local system for the file systems which has to be imported to RTC. I
tried using the Import Wizard and it is giving error. Please help me
out with this.

Thanks
Gayathri

On 5/20/2010 1:52 AM, gayatrivikram26 wrote:

Hi

I am very new to RTC and have gone through the Essentials of RTC
V2.0 book. I my role is to implement RTC in my project. I have
certain couple of queries. I was a ClearCase admin for quite a long
time and I am getting confused when I here the same terms like
stream, component etc in RTC.

See previous post with terminology section from the ClearCase
Synchronizer help page.

1) I would like to know the actual function of stream and component
in RTC.

An RTC stream serves the same purpose of a ClearCase UCM integration
stream. An RTC repository workspace serves the same purpose as a
ClearCase UCM developer stream. An RTC component is very similar to a
UCM component.

2) 3)

See Jared's responses.

4) I have a folder structure created in the Windows Explorer in my
local system for the file systems which has to be imported to RTC. I
tried using the Import Wizard and it is giving error. Please help me
out with this.

In general, you can use the RTC command line. Or you can
- use the File -> New -> Project... wizard to create a project from that
file system folder
- apply Team->Share Project to that root folder
- go to the Pending changes view and "undo" the creation of the .project
file in the root folder
- complete the change set (if you just want to check it in), or deliver
to your stream if you want to send the changes to your stream

You can use the Import Wizard (after you've created a project to import
into), but that would result in copying the tree from where it is on
disk to the new project, which is why I prefer the New -> Project
approach. BTW, what was the error you got?

In general folks, when something goes wrong, it is always good to
provide very explicit description of exactly what command you last
executed, and exactly what error message you got. "giving error"
doesn't give us much to work with (:-).

Cheers,
Geoff