Status for Andrew DeFaria

• Documented PQA issues
• Installed old Clearquest on pcsjca-ccrmt03
• Investigated more about the DST Clearcase issue

Posted by at 5:15 PM | Permalink

• Documented new URL format
• Investigated the feasibility of accommodating a mapping of old URL link with old ID -> new URL

Clearquest Web URLs

With the old Clearquest ASP based Web Platform the following URL would direct you directly to the defected specified in <id>:

http://<server>/cqweb/url/default.asp?id=<id>

This link was often set in email messages generated by action hooks in the schema (e.g. when commitmentLevel's value changed).

With the new Clearquest Java based Web Platform this URL has changed. The new format is a lot longer due to the fact that it is also more flexible:

http://<Server>/cqweb/main?command=GenerateMainFrame&service=CQ&schema=<DBSETName>&contextid=<DBName>&entityDefName=<entityDefName<&entityID=>entityID>

Where:

Server: Name of web server (e.g. extranet.broadcom.com)
DBSETName: Connection ID (e.g. 2005.02.00)
DBName: Name of database (e.g. Cont)
entityDefName: Name of entity record (e.g. Defect)
entityID: ID to display

For example:

http://p4test/cqweb/main?command=GenerateMainFrame&service=CQ&schema=2005.02.00&contextid=Cont&entityDefName=Defect&entityID=Cont00012352

The action hooks in the schema need to change to generate this new URL if the new Clearquest Java based Web Platform is to be used. This will fix all future emails that are generated with such a link.

We cannot fix past emails that already exist in people's mail folders. A thought was given to the idea of configuring the web server such that it would allow the old links to work. I tried, believe me, to see if this was relatively doable. It is not.

Here's what I thought of doing:

1. Configure RWP so that http:///cqweb/url resolves to another place.
2. Configure RWP so that .asp files are considered cqperl scripts. Note RWP is Apache based with Java Tomcat Servelets. I do not think I can configure this RWP to handle true, bona fide ASP pages. Besides I know very little about ASP.
3. In this place write a default.asp that is actually a cqperl script. This script would take the id= parameter, look up the id under old_id then generate a redirect in the form of the new URL substituting the new ID.

Of course, all of this is non standard, thus unsupported by Rational. Additional, although I managed to do #1 and I'm quite sure I could do #3, I got stuck at #2. The problem is that Rational also doesn't support any Perl cgi stuff from RWP. In fact RWP is for Rational's Web Applications only - they don't even support you running static web pages/sites through RWP. So there is no mod_perl.so for me to load into Apache, let alone a mod_perl.so that supports cqperl -which is a non-standard Perl that only Rational supports.

And with this I think we just need to give up the hope of supporting old URL links to old ID numbers, fix it so that new URL links are of proper format and perhaps implement a simply query for "Look up by Old ID" for the customers.

Posted by at 2:00 PM | Permalink

• Worked on trying to test out LDAP Authentication

Posted by at 2:16 PM | Permalink

• Investigating PQA issue regarding email links
• Implementing cleanup of Dynamic Lists
• Handed off test DB backup to Vinh
• Investigated data conversion problems

PQA: Remaining Issues

The following issues came up at this meeting:

1. Requirement to support old style Email Link's (See below)
2. Update Production Web Server to latest Clearquest version (See below)
3. Remaining data conversion issues (Emailed Vinh asking for details)
4. Dynamic List cleanup (Emailed Vinh asking for updates)
5. Test DB hand off (Emailed Vinh pointing to backups of my converted database for him to test)

Vinh provided an example: http://extranet.broadcom.com/cqweb/url/default.asp?id=Prod00014218. There are several problems with this. First the default.asp indicates an IIS server and an ASP web application. The new version of RWP is not IIS based rather it is Apache based. I cannot find a default.asp in RWP at all. Thus the above style link will not work.

Vinh says that he generates through hooks in CQ. I suspect what is happening is this: When a defect changes state action hooks kick in and determine it's time to send email to notify the appropriate people that a change in state has happened. At this time Vinh's hooks change/generate these links. As such Vinh needs to change his hooks to generate new URLs that conform to the new Clearquest software. One question I have is how did Vinh come up with http:///url/default.asp?id= as a syntactical template meaning "Show this specific defect"? I cannot find where this is documented.

I tried http://p4test/url/default.asp?id= on p4test and that doesn't work. Perhaps this is just an issue of figuring out what the correct URL template is and changing the hook. The hook could also be modified to perhaps add links for http:////