It's all about the answers!

Ask a question

How to ensure unique names of components on the server and project area level in RTC

Adam Wereszczynski (92811932) | asked Oct 08 '15, 3:30 a.m.
edited Oct 20 '15, 10:26 a.m. by Chris McGee (50511117)
How can I ensure unique names of components on the server and project area level in IBM Rational Team Concert (RTC)?

The reason I'm asking is that I would like to be able to ensure that component names are unique across all Project Areas on one server, but in specific Project Areas only on another server.

Accepted answer

permanent link
Adam Wereszczynski (92811932) | answered Oct 08 '15, 3:46 a.m.
edited Oct 08 '15, 3:50 a.m.
There are two places in RTC when you can set options regarding component uniqueness:

  • Ensure Component Names are Unique option in Advanced Properties in Change and Configuration Management (CCM) application's admin panel.

    If this option is set to True, then each time when you create a new component, the component name has to be unique within entire repository.
    Otherwise you will get error message during creation and the component will not be created.

    By default, this option is set to False, which means component uniqueness can only be set on the Project Area level.

  • In the Project Area settings in the CCM admin panel or the RTC Eclipse Client, there is a precondition you can use:
    Process Configuration > Preconditions and Follow up Actions > Modify Component > Ensure
    Component Names are Unique

    The scope of this option is only the project area. It means that this option causes an error during
    component creation only if there is a component with the same name in the same workspace.
    It will not show error when there is already the component with the same name but in another project area. Additionally, you can limit checking this precondition only to certain group of users (option Who) or check it during certain iteration type or timeline or iteration (option When).

Both server side setting (point 1.) and precondition (point 2.) check component uniqueness only during creation of the component. It means that they do not affect any non-unique components created when the options were turned off.
David Lafreniere selected this answer as the correct answer

Your answer

Register or to post your answer.