I have also not been able to get this to work. The on-line help has
bugs (submitted work item 141254).
But even after adjusting the parameters based on the "help" for
repotools, I still get an error: " URISyntaxException: Illegal character
in query at index 102"

Submitted work item 141255 for this.

Cheers,
Geoff

On 12/3/2010 4:38 PM, pwagstro wrote:

I'm trying to use repotools-ccm.sh to remove an archived project area
from an RTC 3.0 server. The problem that I've been having is that I
can't figure out what the contextURL parameter is supposed to be set
to. Say I have a project in RTC called "TestProject" and
RTC's url is https://server.example.com:9443/ccm, what is the proper
setting for contextURL. I've been poking around but I haven't had
much luck with it.

Here's some examples of things that I've tried:

contextURL=https://server.example.com:9443/ccm/TestProject
contextURL=https://server.example.com:9443/ccm/
contextURL=TextProject
contextURL=

I'm sure I've tried many more.

Any hints on how to use this wonderful new feature of RTC 3.0?

This is what worked for me and an archived PA:
repotools-ccm.bat -deleteProjectAreaResources
repositoryURL=https://rtc:9443/ccm adminUserId=jtsadmin
adminPassword=jtsadmin
contextURL=https://rtc:9443/ccm/process/project-areas/_1hcSgPthEd-maY-Pawkt3w


I use the word "worked" cautiously - that means the repotools command
ran without errors - the PA is still visible/accessible in
https://rtc:9443/ccm/admin#action=com.ibm.team.process.manageArchivedProjectAreas.

So I'm not quite sure what that command actually did:-)


On 4/12/2010 8:38 AM, pwagstro wrote:

I'm trying to use repotools-ccm.sh to remove an archived project area
from an RTC 3.0 server. The problem that I've been having is that I
can't figure out what the contextURL parameter is supposed to be set
to. Say I have a project in RTC called "TestProject" and
RTC's url is https://server.example.com:9443/ccm, what is the proper
setting for contextURL. I've been poking around but I haven't had
much luck with it.

Here's some examples of things that I've tried:

contextURL=https://server.example.com:9443/ccm/TestProject
contextURL=https://server.example.com:9443/ccm/
contextURL=TextProject
contextURL=

I'm sure I've tried many more.

Any hints on how to use this wonderful new feature of RTC 3.0?

Yes, when switching to the UUID form, I see the same behavior ... script
says it succeeds, but nothing appears to be deleted.

Freddy: Just for interests sake ... how did you come up with that URL
for the project area?

Cheers,
Geoff

On 12/5/2010 3:29 PM, Freddy wrote:

This is what worked for me and an archived PA:
repotools-ccm.bat -deleteProjectAreaResources
repositoryURL=https://rtc:9443/ccm adminUserId=jtsadmin
adminPassword=jtsadmin
contextURL=https://rtc:9443/ccm/process/project-areas/_1hcSgPthEd-maY-Pawkt3w


I use the word "worked" cautiously - that means the repotools command
ran without errors - the PA is still visible/accessible in
https://rtc:9443/ccm/admin#action=com.ibm.team.process.manageArchivedProjectAreas.


So I'm not quite sure what that command actually did:-)


On 4/12/2010 8:38 AM, pwagstro wrote:
I'm trying to use repotools-ccm.sh to remove an archived project area
from an RTC 3.0 server. The problem that I've been having is that I
can't figure out what the contextURL parameter is supposed to be set
to. Say I have a project in RTC called "TestProject" and
RTC's url is https://server.example.com:9443/ccm, what is the proper
setting for contextURL. I've been poking around but I haven't had
much luck with it.

Here's some examples of things that I've tried:

contextURL=https://server.example.com:9443/ccm/TestProject
contextURL=https://server.example.com:9443/ccm/
contextURL=TextProject
contextURL=

I'm sure I've tried many more.

Any hints on how to use this wonderful new feature of RTC 3.0?

Magic, the dark and ancient kind:-)
1. Got "https://rtc:9443/ccm/process/project-areas" from
https://rtc:9443/ccm/rootservices
2. Got "https://rtc:9443/ccm/process/project-areas/..." from
https://rtc:9443/ccm/process/project-areas

But the archived project areas don't show up there so I went to
https://rtc:9443/ccm/admin#action=com.ibm.team.process.manageArchivedProjectAreas,
grabbed the URL for an archived project area eg.
https://rtc:9443/ccm/admin#action=com.ibm.team.process.editArchivedProjectArea&itemId=_1hcSgPthEd-maY-Pawkt3w
and used the ID from it.

There's probably an easier way:-)


On 6/12/2010 1:56 PM, Geoffrey Clemm wrote:

Yes, when switching to the UUID form, I see the same behavior ... script
says it succeeds, but nothing appears to be deleted.

Freddy: Just for interests sake ... how did you come up with that URL
for the project area?

Cheers,
Geoff

On 12/5/2010 3:29 PM, Freddy wrote:
This is what worked for me and an archived PA:
repotools-ccm.bat -deleteProjectAreaResources
repositoryURL=https://rtc:9443/ccm adminUserId=jtsadmin
adminPassword=jtsadmin
contextURL=https://rtc:9443/ccm/process/project-areas/_1hcSgPthEd-maY-Pawkt3w



I use the word "worked" cautiously - that means the repotools command
ran without errors - the PA is still visible/accessible in
https://rtc:9443/ccm/admin#action=com.ibm.team.process.manageArchivedProjectAreas.



So I'm not quite sure what that command actually did:-)

I notice no resolution/answer has appeared here yet, and I challenge the Jazz/RTC developers/SMEs on the subject. I have spent several hours trying to resolve this issue using all (internal and external) resources I know, but this is like playing Monkey Island with no clues.

Main challenges:
1) What is the contextURL? How do we find the correct contextURL of an archived project?
2) Is the command supposed to run on a running server or not? Somewhere it says "stop the server", other places "run against an online server".
3) Is the reindexing something you should do or must do (if you ever get anything deleted)? It's unclear from the few different sources of information.

Today I had to ask sysadmin at my customer's site for more diskspace on the virtual server, since I have filled the repository with trial and experimentation data. He was not impressed when I told him I was unable to remove garbage data without having to remove everything by dropping and recreating the databases.

This is a MUST HAVE operation. All customer will sooner or later have wast amounts of data to remove.