Note: The following information only applies if you installed the IIS Lockdown tool with URLScan, which is generally in the C:\Windows\System32\Inetsrv directory. If there is not a URLScan folder in that directory, URLScan is not installed and you do not need to rename the Helix ALM CGI.

You can rename and run the Helix ALM CGI executable, ttcgi.exe, with a different extension. The CGI value is determined per web page by a dynamic field code: %CGIB%.

To ensure Helix ALM web clients work with the new extension, you need to rename the CGI, modify the registry, and update the CGI name in configuration files used by web clients.

Renaming the Helix ALM CGI

Locate and rename ttcgi.exe. The .exe is normally found in the scripts or cgi-bin directory on the web server. For example, C:\Inetpub\scripts\ttcgi.exe.

After you locate the CGI, rename the file to the desired three letter extension. The CGI is a script the web server needs to recognize and run, instead of treating it as a file to download. We recommend using the .cgi extension (ttcgi.cgi). If you choose another three letter extension, you need to modify your web server so it recognizes the extension. For example, in Apache, you need to add the new extension to the 'AddHandler cgi-script' line in the httpd.conf file.

Modifying the registry

In the Helix ALM Registry Utility, modify the CGI bin path field. For example:

/scripts/ttcgi.cgi

Note: On Unix, change the values in the /etc/ttpro.conf or /etc/ttstudio.conf files.

Updating Helix ALM Web configuration files

Provide the updated CGI name, with the correct extension, in the configuration file used to load and log in to Helix ALM web clients.

Editing the ttweb-config.js file

Note: The following information also applies to TestTrack 2013.1 - 2016.1.

During installation, Helix ALM writes out hard values for your CGI in the Helix ALM configuration file to load the login page. This function needs to be edited to load correctly after the CGI is renamed.

1. Open the ttweb-config.js file in a text editor and locate the following:
   TTWebConfig.cgiName = 'ttcgi.exe';
2. Change the cgiName value to use the correct extension. For example:
   TTWebConf.cgiName = 'ttcgi.cgi';
3. Save the file.

Editing the login.htm page (TestTrack 2013.0.2 and earlier only)

During installation, TestTrack writes out hard values for the CGI in the login.htm page to execute a function that opens the login page. This function needs to be edited for the login.htm page to work correctly after the TestTrack CGI is renamed.

1. Open the login.htm file in any HTML editor and locate the following:
   function openTestTrackWindow()
   {
   stringMyURL = new String('/scripts/ttcgi.exe?command=LoginScreen');
2. Change the newString value to use the correct extension. For example:
   function openTestTrackWindow()
   {
   stringMyURL = new String('/scripts/ttcgi.cgi?command=LoginScreen');
3. Save the file.

Editing the solosubmitlogin.htm file

If you use SoloSubmit, you also need to make the following changes in the login page file.

1. Open the solosubmitlogin.htm file in any HTML editor and locate the following:
   function gotoSoloSubmitWindow()
   {
   stringMyURL = new String('/scripts/ttcgi.exe?command=SoloSubmitScreen');
2. Change the newString value to use the correct extension. For example:
   function gotoSoloSubmitWindow()
   {
   stringMyURL = newString('/scripts/ttcgi.cgi?command=SoloSubmitScreen');
3. Save the file.

Additional help

If you make all changes above and are still prompted to download the CGI file when using web clients, you specified a file type not recognized by your web server. We recommend using the .cgi extension when renaming the ttcgi.exe. If you do not use the .cgi extension, you need to modify your web server so it recognizes the extension as a CGI program and runs it. See the web server documentation for help.