Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EPF » Integration with ClearCase
Integration with ClearCase [message #43926] Fri, 12 October 2007 19:53 Go to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

I just was set up with ClearCase and I am using a dynamic view. Should I
be using snapshot views? How do I check out a file from within EPFC with a
dynamic view? With a snapshot view (if dynamic is not applicable).

Are there any other suggestions that you have for converting my current
library into ClearCase?

Thank you,
Sevon
Re: Integration with ClearCase [message #43956 is a reply to message #43926] Fri, 12 October 2007 20:07 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

This may be a somewhat redundant questions, but in your "Using Eclipse
Process Framework Composer with a Version Control System" Document found
at:

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/doc s/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?co ntent-type=text%2Fhtm&root=Technology_Project&view=c o#_Appendix_C:_Support

Under the Appendix B, under "Creating a View," step one says to:

1. Use the perspective menu in the upper right-hand corner to switch to
the ClearCase perspective.

Where is this ClearCase perspective? I only know of a CVS perspective, is
that the same thing? Is there something that I am missing?

Thanks!
Re: Integration with ClearCase [message #43986 is a reply to message #43956] Fri, 12 October 2007 20:32 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Sevon.
We integrated a lot of the content in this document into the 1.2 online help
now. Check it out and let us know if is helpful. It covers all the topics
below. In your case it seems that you have not yet installed the ClearCase
client (which needs to be provided by your local administrator so that it
fits your ClearCase version) into EPF Composer.

a.. Integration with Rational ClearCase
a.. Installing and configuring Rational ClearCase
a.. Installing and configuring Rational CCRC
a.. Creating a ClearCase view
a.. Creating a view
a.. Using ClearCase dynamic views
a.. Adding a new library to ClearCase
a.. Adding an existing library to ClearCase
a.. Importing a library configuration with ClearCase
a.. Adding a plug-in to ClearCase
a.. Creating a new configuration with ClearCase
a.. Adding a content package to ClearCase
a.. Adding a new method element to ClearCase
a.. Editing method elements with ClearCase
a.. Deleting method elements with ClearCase
a.. Moving method elements with ClearCase
a.. Creating a capability pattern with ClearCase
a.. Multi-User scenarios with ClearCase
a.. Disabling Rational CCRC
a.. Version control for specific files
a.. Common actions impact on specific files

"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:6c39971ac737dc4349e13f3749243b29$1@www.eclipse.org...
> This may be a somewhat redundant questions, but in your "Using Eclipse
> Process Framework Composer with a Version Control System" Document found
> at:
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/doc s/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?co ntent-type=text%2Fhtm&root=Technology_Project&view=c o#_Appendix_C:_Support
>
> Under the Appendix B, under "Creating a View," step one says to:
> 1. Use the perspective menu in the upper right-hand corner to switch to
> the ClearCase perspective.
> Where is this ClearCase perspective? I only know of a CVS perspective, is
> that the same thing? Is there something that I am missing?
>
> Thanks!
>
Re: Integration with ClearCase [message #44043 is a reply to message #43986] Sat, 13 October 2007 18:00 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

Peter,

I've created my ClearCase View and opened it in the composer. I can open
the files (through the VOB) now in the EPFC, but I cannot edit them (which
I believe means I cannot check them out). When I try to write something I
get these 2 error messages:

Read-only File Encountered
File 'XXXX' is read-only. Do you wish to make it writeable?

Then I click Yes

Edit Element
IUPA0015E: Cannot edit element
Reason:
File 'XXXX' is read-only

Any Advise? All of the information in the Help file I believe is the same
as was located in the paper whose link I attached in the previous post. It
is useful, except that I do not know how to switch to the "ClearCase
Perspective", which I think is why I can't edit the file. Is it the same
as the CVS Perspective? or did I do something wrong?

Thanks, and happy Saturday :)
Sevon
Re: Integration with ClearCase [message #44139 is a reply to message #44043] Mon, 15 October 2007 14:47 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello.
What you are seeing is indeed EPFC's 'native' way of dealing with read-only
files. You must install a ClearCase (Eclipse) plugin to be able to use it
CC functions such as check-out. Hence, you need to contact your local CC
administrators and ask them what clients in what versions for what server
versions they provide. They might recommend to use the SCM plug-in
(recommended for on-site usage; i.e. server and clients are nearby) or CCRC
plug-in (recommended for WAN usage). Depending on their recommendation you
need to follow the instructions of the online help pages 'Installing and
Configuring Rational ClearCase' or 'Installing and Configuring Rational
CCRC' before you can use your view from within EPFC. Note, the url's listed
in the online help pages are the default IBM ones. Your administrators
might you provide you with their own URLs to their install areas.

Peter.


"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:9d8498daa25e76ad9278c3c96a8c632d$1@www.eclipse.org...
> Peter,
>
> I've created my ClearCase View and opened it in the composer. I can open
> the files (through the VOB) now in the EPFC, but I cannot edit them (which
> I believe means I cannot check them out). When I try to write something I
> get these 2 error messages:
>
> Read-only File Encountered
> File 'XXXX' is read-only. Do you wish to make it writeable?
>
> Then I click Yes
>
> Edit Element
> IUPA0015E: Cannot edit element
> Reason:
> File 'XXXX' is read-only
>
> Any Advise? All of the information in the Help file I believe is the same
> as was located in the paper whose link I attached in the previous post. It
> is useful, except that I do not know how to switch to the "ClearCase
> Perspective", which I think is why I can't edit the file. Is it the same
> as the CVS Perspective? or did I do something wrong?
>
> Thanks, and happy Saturday :)
> Sevon
>
Re: Integration with ClearCase [message #44170 is a reply to message #44139] Mon, 15 October 2007 19:44 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

Yay!! It works. Thank you very much.

-Sevon :)
Re: Integration with ClearCase [message #44306 is a reply to message #44139] Wed, 17 October 2007 14:09 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

I still have a couple questions about using ClearCase.

Because all of the content items in the folder are referenced in
pligin.xmi, or library.xmi, ClearCase Checks out those items, along with
every other items attached to it. This is not useful because then it keeps
others from being able to check out anything in the plug-in, which defeats
the purpose of even having Config Control.

So we worked around this by deleting library.xmi and plugin.xmi from the
VOB and added it to each of the Views. Now, when you edit, no one else's
library.xmi or plugin.xmi gets updated, which created a new set of
problems because library&plugin.xmi cannot find newly created content or
content with changed names.

So now, we have everyone working out of the same view, which is
essentially the same as having no CM systems at all, but with all the
extra CM hassle, which is still not what we want, but at least we are up
and running again for teh short term.

Checking out everything "unreserved" and putting library.xmi and
plugin.xmi back into the VOB under CM is our only remaining option. So my
question is how well does that work? Are there any potential complications
associated with using the unreserved funtionality? Can you set up CC so
that it always check them out unreserved to save clicking 3 extra times
every time you check out something?

Thanks,
Sevon
Re: Integration with ClearCase [message #44429 is a reply to message #44306] Wed, 17 October 2007 18:24 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Sevon.
What you are trying to do would be comparable with two developers editing
the same source code file at the same time. To be able to do that you need
a compare-and-merge editor that would show you all conflicts the two people
created and let's you choose how to resolve this. Unfortunately, we do have
an editor like that (but hope that someone would be interested in developing
and contributing such an editor to the project).

However, you can create multiple plugins that are used by different content
authors. For example, I know of many users that create a plugin per
discipline plus a common base plugin in which they introduce 'stubs' for
shared elements; for example work products that are used and produced in
more than one discipline. Such a work product would be defined as an empty
element in the base and then Contribution variability would be used by the
disciplines to fill the work product with content from the discipline plugin
that would own it. Other discipline plugins can then reference the base
work product (e.g. tasks as inputs). When you publish the base and its
contribution will be published as one element because of the variability
relationship.

This approach for a content architecture also provides an inherent
governance for your method authoring team as it assigns clear
responsibilities for who can change which element instead of having everyone
change everything all at the same time creating content that is
inconsistently structured, for which conflicts need to be resolved, and
which requires constant refactoring.

Check-out the online help for a description of all files that get checked
out. The plugin.xmi file is basically storing the whole 'model' for the
plugin, i.e. the name and ids for all elements, packages, categories created
plus all their relationships. The idea is that there is a method designer
role owning this file which makes all modeling decisions on a coherent set
of tightly coupled/dependent method elements; which is what we call a method
plugin. The other .xmi files are content and process files which can be
checked-out by other content authoring users who do not model, but write the
rich text content. You see the implied usage and governance model for EPFC
is that there is a (or a small numbers) of designers/architects who performs
the modeling part and a larger number of content authors who document the
method elements by filling in and writing the rich text.

The library.xmi file is your central plugin registry that stores ids and
references for all your plugins. This file is indeed a bottleneck file for
parallel development as everyone who wants to add a new plugin or
configuration needs to check this file out. IBM Rational Method Composer
does not require this file as it has been designed as an extension to EPF
Composer to address such enterprise and larger team development needs.

Hope this helps,
Peter.



"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:c296825cad32dcbb6ac4d1811e4ad4d5$1@www.eclipse.org...
>I still have a couple questions about using ClearCase.
> Because all of the content items in the folder are referenced in
> pligin.xmi, or library.xmi, ClearCase Checks out those items, along with
> every other items attached to it. This is not useful because then it keeps
> others from being able to check out anything in the plug-in, which defeats
> the purpose of even having Config Control.
>
> So we worked around this by deleting library.xmi and plugin.xmi from the
> VOB and added it to each of the Views. Now, when you edit, no one else's
> library.xmi or plugin.xmi gets updated, which created a new set of
> problems because library&plugin.xmi cannot find newly created content or
> content with changed names.
>
> So now, we have everyone working out of the same view, which is
> essentially the same as having no CM systems at all, but with all the
> extra CM hassle, which is still not what we want, but at least we are up
> and running again for teh short term.
> Checking out everything "unreserved" and putting library.xmi and
> plugin.xmi back into the VOB under CM is our only remaining option. So my
> question is how well does that work? Are there any potential complications
> associated with using the unreserved funtionality? Can you set up CC so
> that it always check them out unreserved to save clicking 3 extra times
> every time you check out something?
>
> Thanks,
> Sevon
>
Re: Integration with ClearCase [message #584848 is a reply to message #43926] Fri, 12 October 2007 20:07 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

This may be a somewhat redundant questions, but in your "Using Eclipse
Process Framework Composer with a Version Control System" Document found
at:

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/doc s/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?co ntent-type=text%2Fhtm&root=Technology_Project&view=c o#_Appendix_C:_Support

Under the Appendix B, under "Creating a View," step one says to:

1. Use the perspective menu in the upper right-hand corner to switch to
the ClearCase perspective.

Where is this ClearCase perspective? I only know of a CVS perspective, is
that the same thing? Is there something that I am missing?

Thanks!
Re: Integration with ClearCase [message #584862 is a reply to message #43956] Fri, 12 October 2007 20:32 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Sevon.
We integrated a lot of the content in this document into the 1.2 online help
now. Check it out and let us know if is helpful. It covers all the topics
below. In your case it seems that you have not yet installed the ClearCase
client (which needs to be provided by your local administrator so that it
fits your ClearCase version) into EPF Composer.

a.. Integration with Rational ClearCase
a.. Installing and configuring Rational ClearCase
a.. Installing and configuring Rational CCRC
a.. Creating a ClearCase view
a.. Creating a view
a.. Using ClearCase dynamic views
a.. Adding a new library to ClearCase
a.. Adding an existing library to ClearCase
a.. Importing a library configuration with ClearCase
a.. Adding a plug-in to ClearCase
a.. Creating a new configuration with ClearCase
a.. Adding a content package to ClearCase
a.. Adding a new method element to ClearCase
a.. Editing method elements with ClearCase
a.. Deleting method elements with ClearCase
a.. Moving method elements with ClearCase
a.. Creating a capability pattern with ClearCase
a.. Multi-User scenarios with ClearCase
a.. Disabling Rational CCRC
a.. Version control for specific files
a.. Common actions impact on specific files

"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:6c39971ac737dc4349e13f3749243b29$1@www.eclipse.org...
> This may be a somewhat redundant questions, but in your "Using Eclipse
> Process Framework Composer with a Version Control System" Document found
> at:
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/doc s/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?co ntent-type=text%2Fhtm&root=Technology_Project&view=c o#_Appendix_C:_Support
>
> Under the Appendix B, under "Creating a View," step one says to:
> 1. Use the perspective menu in the upper right-hand corner to switch to
> the ClearCase perspective.
> Where is this ClearCase perspective? I only know of a CVS perspective, is
> that the same thing? Is there something that I am missing?
>
> Thanks!
>
Re: Integration with ClearCase [message #584894 is a reply to message #43986] Sat, 13 October 2007 18:00 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

Peter,

I've created my ClearCase View and opened it in the composer. I can open
the files (through the VOB) now in the EPFC, but I cannot edit them (which
I believe means I cannot check them out). When I try to write something I
get these 2 error messages:

Read-only File Encountered
File 'XXXX' is read-only. Do you wish to make it writeable?

Then I click Yes

Edit Element
IUPA0015E: Cannot edit element
Reason:
File 'XXXX' is read-only

Any Advise? All of the information in the Help file I believe is the same
as was located in the paper whose link I attached in the previous post. It
is useful, except that I do not know how to switch to the "ClearCase
Perspective", which I think is why I can't edit the file. Is it the same
as the CVS Perspective? or did I do something wrong?

Thanks, and happy Saturday :)
Sevon
Re: Integration with ClearCase [message #584935 is a reply to message #44043] Mon, 15 October 2007 14:47 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello.
What you are seeing is indeed EPFC's 'native' way of dealing with read-only
files. You must install a ClearCase (Eclipse) plugin to be able to use it
CC functions such as check-out. Hence, you need to contact your local CC
administrators and ask them what clients in what versions for what server
versions they provide. They might recommend to use the SCM plug-in
(recommended for on-site usage; i.e. server and clients are nearby) or CCRC
plug-in (recommended for WAN usage). Depending on their recommendation you
need to follow the instructions of the online help pages 'Installing and
Configuring Rational ClearCase' or 'Installing and Configuring Rational
CCRC' before you can use your view from within EPFC. Note, the url's listed
in the online help pages are the default IBM ones. Your administrators
might you provide you with their own URLs to their install areas.

Peter.


"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:9d8498daa25e76ad9278c3c96a8c632d$1@www.eclipse.org...
> Peter,
>
> I've created my ClearCase View and opened it in the composer. I can open
> the files (through the VOB) now in the EPFC, but I cannot edit them (which
> I believe means I cannot check them out). When I try to write something I
> get these 2 error messages:
>
> Read-only File Encountered
> File 'XXXX' is read-only. Do you wish to make it writeable?
>
> Then I click Yes
>
> Edit Element
> IUPA0015E: Cannot edit element
> Reason:
> File 'XXXX' is read-only
>
> Any Advise? All of the information in the Help file I believe is the same
> as was located in the paper whose link I attached in the previous post. It
> is useful, except that I do not know how to switch to the "ClearCase
> Perspective", which I think is why I can't edit the file. Is it the same
> as the CVS Perspective? or did I do something wrong?
>
> Thanks, and happy Saturday :)
> Sevon
>
Re: Integration with ClearCase [message #584953 is a reply to message #44139] Mon, 15 October 2007 19:44 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

Yay!! It works. Thank you very much.

-Sevon :)
Re: Integration with ClearCase [message #585018 is a reply to message #44139] Wed, 17 October 2007 14:09 Go to previous messageGo to next message
Eclipse User
Originally posted by: Sevon.Vanbebber.baesystems.com

I still have a couple questions about using ClearCase.

Because all of the content items in the folder are referenced in
pligin.xmi, or library.xmi, ClearCase Checks out those items, along with
every other items attached to it. This is not useful because then it keeps
others from being able to check out anything in the plug-in, which defeats
the purpose of even having Config Control.

So we worked around this by deleting library.xmi and plugin.xmi from the
VOB and added it to each of the Views. Now, when you edit, no one else's
library.xmi or plugin.xmi gets updated, which created a new set of
problems because library&plugin.xmi cannot find newly created content or
content with changed names.

So now, we have everyone working out of the same view, which is
essentially the same as having no CM systems at all, but with all the
extra CM hassle, which is still not what we want, but at least we are up
and running again for teh short term.

Checking out everything "unreserved" and putting library.xmi and
plugin.xmi back into the VOB under CM is our only remaining option. So my
question is how well does that work? Are there any potential complications
associated with using the unreserved funtionality? Can you set up CC so
that it always check them out unreserved to save clicking 3 extra times
every time you check out something?

Thanks,
Sevon
Re: Integration with ClearCase [message #585068 is a reply to message #44306] Wed, 17 October 2007 18:24 Go to previous messageGo to next message
Peter Haumer is currently offline Peter Haumer
Messages: 228
Registered: July 2009
Senior Member
Hello Sevon.
What you are trying to do would be comparable with two developers editing
the same source code file at the same time. To be able to do that you need
a compare-and-merge editor that would show you all conflicts the two people
created and let's you choose how to resolve this. Unfortunately, we do have
an editor like that (but hope that someone would be interested in developing
and contributing such an editor to the project).

However, you can create multiple plugins that are used by different content
authors. For example, I know of many users that create a plugin per
discipline plus a common base plugin in which they introduce 'stubs' for
shared elements; for example work products that are used and produced in
more than one discipline. Such a work product would be defined as an empty
element in the base and then Contribution variability would be used by the
disciplines to fill the work product with content from the discipline plugin
that would own it. Other discipline plugins can then reference the base
work product (e.g. tasks as inputs). When you publish the base and its
contribution will be published as one element because of the variability
relationship.

This approach for a content architecture also provides an inherent
governance for your method authoring team as it assigns clear
responsibilities for who can change which element instead of having everyone
change everything all at the same time creating content that is
inconsistently structured, for which conflicts need to be resolved, and
which requires constant refactoring.

Check-out the online help for a description of all files that get checked
out. The plugin.xmi file is basically storing the whole 'model' for the
plugin, i.e. the name and ids for all elements, packages, categories created
plus all their relationships. The idea is that there is a method designer
role owning this file which makes all modeling decisions on a coherent set
of tightly coupled/dependent method elements; which is what we call a method
plugin. The other .xmi files are content and process files which can be
checked-out by other content authoring users who do not model, but write the
rich text content. You see the implied usage and governance model for EPFC
is that there is a (or a small numbers) of designers/architects who performs
the modeling part and a larger number of content authors who document the
method elements by filling in and writing the rich text.

The library.xmi file is your central plugin registry that stores ids and
references for all your plugins. This file is indeed a bottleneck file for
parallel development as everyone who wants to add a new plugin or
configuration needs to check this file out. IBM Rational Method Composer
does not require this file as it has been designed as an extension to EPF
Composer to address such enterprise and larger team development needs.

Hope this helps,
Peter.



"Sevon Vanbebber" <Sevon.Vanbebber@baesystems.com> wrote in message
news:c296825cad32dcbb6ac4d1811e4ad4d5$1@www.eclipse.org...
>I still have a couple questions about using ClearCase.
> Because all of the content items in the folder are referenced in
> pligin.xmi, or library.xmi, ClearCase Checks out those items, along with
> every other items attached to it. This is not useful because then it keeps
> others from being able to check out anything in the plug-in, which defeats
> the purpose of even having Config Control.
>
> So we worked around this by deleting library.xmi and plugin.xmi from the
> VOB and added it to each of the Views. Now, when you edit, no one else's
> library.xmi or plugin.xmi gets updated, which created a new set of
> problems because library&plugin.xmi cannot find newly created content or
> content with changed names.
>
> So now, we have everyone working out of the same view, which is
> essentially the same as having no CM systems at all, but with all the
> extra CM hassle, which is still not what we want, but at least we are up
> and running again for teh short term.
> Checking out everything "unreserved" and putting library.xmi and
> plugin.xmi back into the VOB under CM is our only remaining option. So my
> question is how well does that work? Are there any potential complications
> associated with using the unreserved funtionality? Can you set up CC so
> that it always check them out unreserved to save clicking 3 extra times
> every time you check out something?
>
> Thanks,
> Sevon
>
Re: Integration with ClearCase [message #975752 is a reply to message #584862] Wed, 07 November 2012 22:56 Go to previous messageGo to next message
Naveen Jain is currently offline Naveen Jain
Messages: 2
Registered: September 2012
Junior Member
Dear Peter,
I am not able to access the page you haev mentioned.
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.epf/docs/Using%20EPF%20with%20a%20Version%20Control%20System.rtf?content-type=text%2Fhtm&root=Technology_Project&view=co#_Appendix_C:_Support
I want to integrate EPF Composer to Clearcase.
Please send me the detailed instructions at naveenjain@eaton.com
Re: Integration with ClearCase [message #996746 is a reply to message #975752] Wed, 02 January 2013 15:26 Go to previous message
Bruce MacIsaac is currently offline Bruce MacIsaac
Messages: 30
Registered: July 2009
Member
I believe integration with Clearcase is the same as with Rational Method Composer.
See this RMC community page for information:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/W6b0a089a62f3_4493_bcc1_ebe60a2ebb41/page/Using%20RMC%20with%20Version%20Control%20Systems
Previous Topic:EPF/OpenUP in MAC
Next Topic:"Contributes" content variability
Goto Forum:
  


Current Time: Sat Aug 30 00:27:01 EDT 2014

Powered by FUDForum. Page generated in 0.07246 seconds