Abstract: The IBM Rational Developer for System z (RDz) Server Health Checklist is a guide to aid with the installation and configuration of RDz. This document is a supplement and not a replacement for the existing RDz publications.

Here are two great new videos out of Rational User Education have been released! IBM Rational DOORS: Collecting Metrics for Better Results, Parts 1 and 2 with George Siampos. This has been a very popular and broadly attended video seminar which should prove useful for anyone using DOORS:

There have been a few queries asking why organizations should use at least one Team Area with all same members as in a Project, using IBM Rational Team Concert (RTC).

The requirement for end users maybe something similar:

We have small projects only about 20 members per each and we don't need separate project members into teams.
Is there any reason why we should use at least one team with all same members as is in project?
Or can we just use only project without creating teams at all, if we don't need more than one team?
Is there like some reporting or source control aspect which might be missed if at least one Team Area is not used in projects?

--> The following details provide some basic information about Team Areas and their usage in RTC:

Creation of Team Areas is optional and not mandatory. It is up to the discretion of the users to analyze and see if having a team area is required or not.
Having at least a single team area or not will not have any impact on either reporting or source control aspects of RTC.
Team Area is more of an encapsulation model sorts to encapsulate users into a particular team and a specific iteration/Release.

For example:
Assume the Product Development team consists of a Development line and Maintenance line.

Here one might want to create two teams and add users accordingly, such that Development line users will have access to Development Project
Area and Maintenance line users will have access to Patch/Fix-Pack Project Areas only. In such cases, using Team Areas will help.

Otherwise based on the need, users can go ahead and use the single Project Area for an entire team of small size.
The advantage of this is, it will reduce the overhead on the administration aspects for a Team Area.

--> Here is what the Team Area serves:
*****
Having a team area is optional, but most projects of moderate to high complexity will have one or more team areas.
A team area serves these functions:

Defines the users (team members) on the team and specifies their roles.
Defines the timeline in which the team is participating.
Customizes the project process to the needs of the team.

Rational Team Concert allows for a hierarchy of team areas to accommodate more complex projects and large teams with varying needs
within the project. Any contributor to a project can participate in one or more team areas.
*****

One of our own Technical Support Engineers and content creators has his own blogon developerWorks and is now delivering some great ClearCase specific information to help address issues he discovers in the course of his job supporting the product.

Pedro Luiz Teixeira de Moura is just getting started with his blog, but already has some quality posts in his back pocket of the archives for you to check out: