Topic
1 reply Latest Post - ‏2013-11-17T23:25:53Z by Dave-Robinson
GKellner
GKellner
258 Posts
ACCEPTED ANSWER

Pinned topic Question regarding rootless components

‏2013-11-11T12:46:38Z |

We are thinking about setting up a new project, where lots of rootless components will be used.

So a base architecture could look like:
10 PVOBs, containing the component definition for the rooted components.
10 Component VOBs where the components will reside.
One overlaying PVOB, containing the rootless components with their baselines.

Can rootless components or their baselines be easily removed in the overlaying PVOB, if they are out of support or canceled?

I have some concerns regarding DB size and performance, if there are to many meta data in.

As long as the rootless components are readonly, there shouldn't be any back-reference from the underlaying PVOB, isn't it?

greetings georg.

  • Dave-Robinson
    Dave-Robinson
    116 Posts
    ACCEPTED ANSWER

    Re: Question regarding rootless components

    ‏2013-11-17T23:25:53Z  in response to GKellner

    >>>  Can rootless components or their baselines be easily removed in the overlaying PVOB, if they are out of support or canceled?

    No.

    Except where "canceled" means you decided never to use it in a project.

    Anything that is "used" in UCM is very difficult to remove.

     

    >>> As long as the rootless components are readonly, there shouldn't be any back-reference from the underlaying PVOB, isn't it?

    Well, rootless components are implicitly read-only - they APPEAR read-only in every project in which they are used.

    However, making a baseline in a component is actually a modification of the component; so in that sense they are not really read-only.

     

    There are hyperlinks between baselines and the streams that use them. I'm not sure if this is what you mean by "back-reference".