defaria.com/blogs/Status/archives/000461.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
  11
  12    <title>Status for Andrew DeFaria: PQA: URL Link Issue</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/000462.html" title="PQA: LDAP" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000463.html" title="PQA Issues/CQ 2002.05 setup" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000462.html">&laquo; PQA: LDAP</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000463.html">PQA Issues/CQ 2002.05 setup &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000461"></a>
  47                      <div class="entry" id="entry-461">
  48                         <h3 class="entry-header">PQA: URL Link Issue</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52   <li>Documented new URL format</li>
  53
  54   <li>Investigated the feasibility of accommodating a mapping of old URL link with old ID -> new URL</li>
  55 </ul>
  56                            </div>
  57                            <div id="more" class="entry-more">
  58                               <h2>Clearquest Web URLs</h2>
  59
  60 <p>With the old Clearquest ASP based Web Platform the following URL would direct you directly to the defected specified in &lt;id&gt;:</p>
  61
  62 <blockquote>
  63  http://&lt;<i>server</i>&gt;/cqweb/url/default.asp?id=&lt;<i>id</i>&gt;
  64 </blockquote>
  65
  66 <p>This link was often set in email messages generated by action hooks in the schema (e.g. when commitmentLevel's value changed).</p>
  67
  68 <p>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:</p>
  69
  70 <blockquote>
  71 http://&lt;<i>Server</i>&gt;/cqweb/main?command=GenerateMainFrame&service=CQ&schema=&lt;<i>DBSETName</i>&gt;&contextid=&lt;<i>DBName</i>&gt;&entityDefName=&lt;<i>entityDefName</i>&lt;&entityID=&gt;<i>entityID</i>&gt;
  72 </blockquote>
  73
  74 <p>Where:</p>
  75
  76 <blockquote>
  77 <i>Server</i>: Name of web server (e.g. extranet.broadcom.com)<br>
  78 <i>DBSETName</i>: Connection ID (e.g. 2005.02.00)<br>
  79 <i>DBName</i>: Name of database (e.g. Cont)<br>
  80 <i>entityDefName</i>: Name of entity record (e.g. Defect)<br>
  81 <i>entityID</i>: ID to display<br>
  82 </blockquote>
  83
  84 <p>For example:
  85
  86 <blockquote>
  87 </p>http://p4test/cqweb/main?command=GenerateMainFrame&service=CQ&schema=2005.02.00&contextid=Cont&entityDefName=Defect&entityID=Cont00012352
  88 </blockquote>
  89
  90 <p>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.</p>
  91
  92 <p>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.</p>
  93
  94 <p>Here's what I thought of doing:</p>
  95
  96 <ol>
  97   <li>Configure RWP so that http://<server>/cqweb/url resolves to another place.</li>
  98
  99   <li>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.</li>
 100
 101   <li>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.</li>
 102 </ol>
 103
 104 <p>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.</p>
 105
 106 <p>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.</p>
 107                            </div>
 108                         </div>
 109                         <p class="entry-footer">
 110                            <span class="post-footers">Posted by  on October 28, 2005  2:00 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000461.html">Permalink</a>
 111                         </p>
 112                      </div>
 113
 114
 115
 116
 117                   </div>
 118                </div>
 119             </div>
 120          </div>
 121       </div>
 122    </div>
 123 </body>
 124 </html>