---

Installing and Configuring Rational RequisiteWeb Version 2002.05.20

---

For trademark and copyright information, see Legal Notices.

Introduction

Rational RequisiteWeb allows clients to read, create, and modify Rational RequisitePro project requirements across an intranet. RequisiteWeb uses the browsers Netscape Navigator and Microsoft Internet Explorer to provide platform-independent, thin-client access to RequisitePro project data. RequisiteWeb can only be installed on a Windows server.

This document contains the following sections:

• RequisiteWeb System Requirements
• Configuring the RequisiteWeb Server
• Configuring Web Server Components
• Testing RequisiteWeb
• Managing RequisitePro Projects for RequisiteWeb
• Configuring E-mail for Discussions
• Upgrading RequisiteWeb
• Uninstalling RequisiteWeb
• Known Issues
• Contact Information

RequisiteWeb System Requirements

Server Requirements

The following table summarizes the requirements for the RequisiteWeb server.

Item	Requirement
Operating System	One of the following: Microsoft Windows 2000 Server, Advanced Server NT Server 4.0, Service Pack 6A or later; NT 4.0 Option Pack
HTTP Server	One of the following: Internet Information Server (IIS) 4.0 and Microsoft Transaction Server (MTS) 2.0 Internet Information Services (IIS) 5.0
Processor	400 MHz or greater
Memory	128 MB. For projects with more than 10,000 requirements or Web sites with more than 10 concurrent users, 256 MB or more is recommended.
Disk space	RequisiteWeb (includes system DLLs) -- 40 MB
Other products	Microsoft Word 2000 Microsoft Word 2002 Note: Microsoft Word licenses are required for all concurrent RequisiteWeb users. Oracle, version 7.3.4, 8.1.5, 8.1.6, 8.1.7, client software (for accessing projects in an Oracle database). Microsoft Internet Explorer 5.01 SP2 or Higher

Note: The RequisiteWeb server cannot be implemented on a Primary Domain Controller or Backup Domain Controller and RequisiteWeb cannot be run on an ADSI enabled network. Novell networks are not supported.

RequisiteWeb Security Requirements

Use caution when modifying permissions on RequisiteWeb-related folders.

Client Requirements

To access RequisiteWeb from client machines, you must install one of the following Web browsers on the client system. No additional client installation is required for use of RequisiteWeb.

• Microsoft Internet Explorer 5.01 SP2 or Higher
• Netscape Navigator 4.51 or greater

Note: For proper RequisiteWeb operation, you must set your browser to allow cookies.

Configuring the RequisiteWeb Server

Before you configure RequisiteWeb, Microsoft Internet Information Server (IIS) and Microsoft Word must be installed on your Windows server. For more information on IIS, see Microsoft Servers at http://www.microsoft.com/servers.

Important: Do not install RequisiteWeb on a system that has J-Integra already installed.

Note: If you are upgrading RequisiteWeb version 2002.05.0X or 2001A, skip to the Upgrading RequisiteWeb section of this document.

This section describes installation and configuration of the RequisiteWeb components on your server. The following procedures are provided:

• Installing the Oracle Client
• Creating the RequisiteWeb User on the Windows Domain Server
• Adding the ReqWebUser to the Local Administrator Group
• Assigning DCOM Permissions to the Local Administrators Group
• Installing RequisiteWeb on the Server

Installing the Oracle Client

To access RequisitePro projects that are stored in an Oracle database, you must configure Oracle client software on the server.

Important: When setting up RequisiteWeb on a server, you must install the Oracle client software before installing RequisiteWeb if you are using Oracle version 8.1.7 or earlier.

Creating the RequisiteWeb User on the Windows Domain Server

RequisiteWeb requires that you create an administrative user, ReqWebUser, for accessing RequisiteWeb components

When you create the ReqWebUser user on the Windows domain server, be sure to log in to your Windows domain server as an administrator.

Step	NT 4.0	Windows 2000 Server
1	On the domain server, click Start > Programs > Administrative Tools (Common) > User Manager for Domains.	On the domain server, click Start > Programs > Administrative Tools > Computer Management.
2	Click User > New User.	Expand Domain Users and Groups. Right-click Users; select New User.
3	In the Username field, type ReqWebUser and type a password of your choice.	In the Username field, type ReqWebUser and type a password of your choice.
4	Clear the check box User must change password at next login, and select the check box Password never expires. Click Add; click Close.	Clear the check box User must change password at next login, and select the check box Password never expires. Click Create; click Close.
5	Click the Groups button. In the Not a Member Of list, select Domain Admins and click Add. Click OK twice.	Double-click the ReqWebUser. In the ReqWebUser Properties dialog box, select the Member Of tab and click Add. Select your domain from the Look in field. Select Domain Admins from the Name column and click Add. Click OK.
5	Close the User Manager application.	Close the Computer Management application.

Adding the ReqWebUser to the Local Administrator Group

Note: Be sure to log in to your RequisiteWeb server as an administrator for the following procedure.

Step	NT 4.0	Windows 2000 Server
1	On the Windows server, click Start > Programs > Administrative Tools (Common) > User Manager for Domains.	On the Windows server, click Start > Programs > Administrative Tools > Computer Management.
2	Click User > Select Domain, select your domain server, and type your machine name. Click OK.	Expand Local Users and Groups. Select Groups. Right-click Administrators and select Add to Group. In the Administrators Properties dialog box, click Add.
3	Under the Groups column, double-click Administrators.	The Select Users or Groups dialog box appears. At the Look in field, select the domain where you created the ReqWebUser.
4	In the Local Group Properties dialog box, click Add. Select your Domain Server in the List Names From drop-down list box. Select ReqWebUser in the Names list and click Add. Click OK.	Select the ReqWebUser and click Add.
5	Click OK in the Local Group Properties dialog box to close it.	Click OK to close the Select Users or Groups dialog box. Click OK to finish.
6	Close the User Manager application.	Close the Computer Management application.

Note: If any of your RequisitePro project files are located on a server other than the RequisiteWeb server, the ReqWebUser must have Change or Modify permission for the directory containing the RequisitePro (.rqs) project file on the remote file server.

We suggest that you add the ReqWebUser to the domain administrator group, to allow RequisiteWeb to gain easy access to shared network folders. However, if you have security concerns and prefer not to add the ReqWebUser to the domain administrators group, you can still configure RequisiteWeb to open RequisitePro projects on shared network folders. To do so, grant the ReqWebUser domain user both Read and Write permissions to those folders.

Assigning DCOM Permissions to the Local Administrators Group

RequisiteWeb uses the DCOM and a local user with Administrator permissions to launch Microsoft Word.

Note: If you have not already installed Microsoft Word, you must do so now.

Use DCOM to give the ReqWebUser user access and launch permissions for Microsoft Word and Microsoft Word Basic, if it appears in your DCOM application list. The following sections provide detailed instructions for these procedures.

To Assign Access Permissions to the Local Administrators Group:

1. On the Start menu, click Run, and type dcomcnfg

   Note: At this point you may see the DCOM Configuration Warning dialog box. Disregard the warning and proceed to the next step.

2. Select the Default Security tab. Under Default Access Permissions, click the Edit Default button.
3. In the Registry Value Permissions dialog box, click Add.
4. At the Add Users and Groups dialog box, select your local machine from the List Names From drop-down list box.
5. Select the Administrators group in the Names list and click Add.
6. At the Type of Access field, select Allow Access. Click OK twice to return to the Distributed COM Configuration Properties dialog box.

To Assign Launch Permissions to the Local Administrators Group:

1. Select the Default Security tab. Under Default Launch Permissions, click the Edit Default button.
2. In the Registry Value Permissions dialog box, click Add.
3. At the Add Users and Groups dialog box, select your local machine from the List Names From drop-down list box.
4. Select the Administrators group in the Names list and click Add.
5. At the Type of Access field, select Allow Launch. Click OK twice to return to the Distributed COM Configuration Properties dialog box.
6. Close DCOM and restart your system.

Installing RequisiteWeb on the Server

Note: If you are a current RequisiteWeb user, be sure to remove any earlier version of RequisiteWeb before you install the current release of RequisiteWeb on your server. Do not remove your ReqWeb virtual directory; instead, redirect it to the components in your new RequisiteWeb installation. Refer to Uninstalling RequisiteWeb for specific instructions. Be sure to retain your existing catalog.txt file. You must also reset your DCOM configuration settings for Word Document and, if it exists, Word Basic to their default values.

Note: To install RequisiteWeb, you must have a Rational license key. You can acquire and import the Rational license keys before or after installing Rational RequisitePro. If you install RequisiteWeb as part of a Rational Suite, you must select the appropriate Suite license usage order. In the Rational License Administrator, click Settings > License Usage Mapper. See Prioritizing Licenses on Your System (License Usage Mapper) in the Administering Licenses for Rational Software manual.

1. Log in to the RequisiteWeb Windows server as a local administrator.
2. Insert the Rational Solutions for Windows CD disc 1 into your system's CD drive. The setup program starts automatically. If autorun is disabled on your system, click Start > Run. Using the drive letter of your CD-ROM drive, type <drive:>\SETUP.EXE, where <drive:> is the drive letter of your CD-ROM drive. The Rational Software Setup wizard guides you through the software installation.
3. On each screen, click the Next button to proceed to the next screen. The Rational Software Setup program writes a log of the installation activities. The log file is located, by default, in C:\Program Files\Rational\RSSetup\RSSetup.log
4. At the Choose Product screen, select Rational RequisitePro under the Product list.
5. At the Select Configuration screen, click Custom.

   Note: If your database server is running on an international operating system, be sure that the install path does not include folders with double-byte character names.

6. At the Choose Features screen, select the Web Server Components check box.
7. Under the Web Server Components leave the RequisiteWeb check box selected
8. Select or clear the following optional check box:
   • The Sample Projects option, under the expanded RequisitePro options, allows you to include the RequisitePro Learning Project and QuarterByte Bank example projects. These projects are helpful for testing and learning RequisiteWeb.

Reboot Required

If files that are required for the installation are in use during the installation procedure, the Rational Windows Setup program may require that you reboot your system to complete the installation.

After rebooting, log in as the same user to complete the installation procedure.

Configuring Web Server Components

This section presents procedures for installing and configuring Web Server components on a Windows IIS Server. Be sure to log in as an administrator before you begin the installation process.

This section contains the following procedures:

1. Adding a JSP Filter
2. Creating a Jakarta Virtual Directory on IIS
3. Configuring the Jakarta Virtual Directory
4. Creating a ReqWeb Virtual Directory on IIS
5. Starting the Tomcat Servlet Engine
6. Assigning DCOM Permissions for the ReqWebUser
7. Assigning Identity for the ReqWebUser
8. Editing the RequisiteWeb Configuration File
9. SSL (Secure Socket Layer)

Note: The instructions in this document assume that you are installing the RequisiteWeb application on your C:\ drive. Substitute the appropriate drive, if necessary, when performing all procedures. Folders that contain projects located on a network must be shared.

By default, local projects are created in the following directory:
C:\Program Files\Rational\RequisitePro\ReqWeb\Projects

Adding a JSP Filter

The following filter setting instructs IIS to process JSP pages using Tomcat.

1. Launch the Internet Services Manager by doing one of the following:
   • In Windows NT 4.0, click Start > Programs > Windows NT 4.0 Option Pack > Microsoft Internet Information Server > Internet Service Manager.
   • In Windows 2000 Server, click Start > Programs > Administrative Tools/Internet Services Manager.
2. Right-click the Default Web Site and select Properties.
3. At the ISAPI Filters tab, click Add.
4. Type the filter name: jakarta

   Note: The filter name, jakarta, must be lower case.

5. Browse to and select
   C:\Program Files\Rational\Jakarta-Tomcat\jakarta\isapi_redirect.dll

   Note: You may not be able to see the isapi_redirect.dll file. If not, type isapi_redirect.dll in the File name box.

6. Click OK to close the dialog boxes.
7. Leave the Internet Services Manager open.

Creating a Jakarta Virtual Directory on IIS

To configure a virtual directory for Jakarta Tomcat on your RequisiteWeb server:

1. Right-click the Default Web Site and select New > Virtual Directory.
2. In the Virtual Directory Creation Wizard, click Next and type an Alias: jakarta.

   Note: The alias, jakarta, must be lower-case.

3. Click Next and browse to and select
   C:\Program Files\Rational\jakarta-tomcat\jakarta
4. Click Next and make sure that only the Read, Run, and Execute options are checked if using Windows 2000 and that only the Read, Script, and Execute options are checked if using Windows NT.
5. Click Next and Finish to complete the wizard. Leave the Internet Services Manager open.

Configuring the Jakarta Virtual Directory

The following sets the anonymous user for the Jakarta virtual directory under IIS.

1. Right-click the jakarta virtual directory and select Properties.
2. At the jakarta Properties dialog box, select the Directory Security tab. In Anonymous Access and Authentication Control, click Edit.
3. At the Authentication Methods dialog box, select Allow Anonymous Access, clear all other check boxes, and click Edit.
4. In the Anonymous User Account dialog box, at the Username field, replace the default entry by typing: "Domain"\ReqWebUser, type your password, and clear all check boxes. Click OK .Leave the Internet Services Manager open.

Creating a ReqWeb Virtual Directory on IIS

To create a virtual directory for RequisiteWeb on your RequisiteWeb server:

1. Right-click the Default Web Site and select New Virtual Directory.
2. In the Virtual Directory Creation Wizard, click Next and type an Alias: ReqWeb.
3. Click Next and browse to and select
   C:\Program Files\Rational\jakarta-tomcat\webapps\ReqWeb
4. Click Next and make sure that only the Read and Run options are checked if using Windows 2000 and that only the Read and Script options are checked if using Windows NT.
5. Click Next and Finish to complete the wizard.

Step	Windows NT 4.0/IIS 4.0	Windows 2000 Server/IIS 5.0
1	Right-click the ReqWeb virtual directory (located under the Default Web Site) and select Properties.	Right-click the ReqWeb virtual directory (located under the Default Web Site) and select Properties.
2	At the Properties dialog box, click the Virtual Directory tab. Select Read permission; clear Write permission. Be sure that the Application Settings section contains the Name "ReqWeb". Clear the box Run in separate memory space. At the Permissions list, select Script.	At the Properties dialog box, click the Virtual Directory tab. Select Read permission; clear Write permission. Clear the Directory Browsing check box. Be sure that the Application Settings section contains the Application Name "ReqWeb". Accept Medium Application Protection.
3	Click Configuration. At the Application Configuration dialog box, click the App Options tab. Select Enable session state. Set ASP Script timeout to at least 90 seconds. Keep default values for all other settings. Click OK.	Click Configuration. At the Application Configuration dialog box, click the App Options tab. Select Enable session state and set Session timeout to 20 minutes. Set ASP Script timeout to at least 90 seconds. Keep default values for all other settings. Click OK.
4	At the Properties dialog box, click the Directory Security tab. In Anonymous Access and Authentication Control, click Edit.	At the Properties dialog box, click the Directory Security tab. In Anonymous access and authentication control, click Edit.
5	At the Authentication Methods dialog box, select Allow Anonymous Access, clear all other check boxes, and click Edit.	At the Authentication Methods dialog box, select Anonymous Access, clear all other check boxes, and click Edit.
6	In the Anonymous User Account dialog box, at Username field, replace the default entry by typing: "Domain"\ReqWebUser, and type a password of your choice. Clear the check box Enable Automatic Password Synchronization. Click OK twice.	In the Anonymous User Account dialog box, at Username field, replace the default entry by typing: "Domain"\ReqWebUser, and type a password of your choice. Clear the check box Allow IIS to control password. Click OK twice.
7	At the Properties dialog box, click the Documents tab. Select the Enable Default Document check box. Click Add. At the Add Default Document dialog box, type index.html. Click OK. At the Properties dialog box, on the Documents tab, select the index.html entry in the default document list. Use the up arrow to move that entry to the top of the list. Click OK. Note: If you are using SSL, skip step 8.	At the Properties dialog box, click the Documents tab. Select the Enable Default Document check box. Click Add. At the Add Default Document dialog box, type index.html. Click OK. At the Properties dialog box, on the Documents tab, select the index.html entry in the default document list. Use the up arrow to move that entry to the top of the list. Click OK. Note: If you are using SSL, skip step 8.
8	At the Properties dialog box, click the HTTP Headers tab. Check Enable Content Expiration and select Expire Immediately. Click OK.	At the Properties dialog box, click the HTTP Headers tab. Check Enable Content Expiration and select Expire Immediately. Click OK.

Starting the Tomcat Servlet Engine

To load the Tomcat servlet engine into IIS:

Stop and start the Internet Services Manager by doing one of the following:

• In Windows NT 4.0, open an MS-DOS shell and type the following:

  net stop w3svc

  net start w3svc

• In Windows 2000, right click your server name and select Restart IIS. The Stop/Start/Reboot dialog box appears. Select Restart Internet Services and click OK.

Assigning DCOM permissions for the ReqWebUser

Use DCOM to set the RQProxy.Connector identity to the ReqWebUser. The following section provides detailed instructions for this procedure.

Assigning Identity for the ReqWebUser:

1. On the Start menu, click Run, and type dcomcnfg
2. In the list of applications, select RqProxy.Connector and click Properties. The RqProxy.Connector Properties dialog box appears.
3. Select the Identity tab and click This user and Browse. Click the List Names From field and select your domain. Select the ReqWebUser entry. Click Add and OK.
4. Enter and confirm the ReqWebUser password that you defined when you created this user.
5. Click OK again to return to the Dristributed COM Configuration Properties dialog box.
6. Close DCOM and restart your system.

Editing the RequisiteWeb Configuration File

To configure the RWConfig file, execute the RWConfig Java utility as follows:

1. Open an MS-DOS shell and navigate to the following directory:

   C:\Program Files\Rational\jakarta-tomcat\ 
   webapps\ReqWeb\WEB-INF\classes 
   

2. Type the following at the MS-DOS prompt:

   set classpath=%classpath%;. 
   

3. Type the following command to execute the RWConfig Java utility:

   "C:\Program Files\Rational\common\java\jre\bin\java" RWConfig 
   

   Note: This procedure assumes that you have installed the RequisiteWeb application on your C:\ drive. Substitute the appropriate drive, if necessary, when performing this step.

4. For each setting (shown in the list below), accept the default or modify the value, as indicated.
   • `Install Type' is 1 --> Enter a value of 2.
   • `SSL' is False --> Accept the current value by pressing Enter.
   • `User ID' is <BLANK> --> Enter ReqWebUser.
   • Password is blank: To modify it press spacebar and Enter --> Press the spacebar and press Enter. Type and confirm your ReqWebUser password.
   • `Server Name' is <BLANK> --> Type the name of your RequisiteWeb server.
   • `Domain' is <BLANK> --> Enter the name of the domain where the ReqWebUser was created.
   • `RPXHTTP' is GenDoc/ --> Accept the current value by pressing Enter.
   • `RPXDocPath' is

     c:\Program Files\rational\Jakarta-Tomcat\webapps\reqweb\gendoc

     --> Accept the current value by pressing Enter.

     Note: This is the default location of temporary files generated by Microsoft Word. Modify this value if you have a different configuration.

   • `RPXCatalog' is

     c:\Program Files\Rational\RequisitePro\ReqWeb\Projects\catalog.txt

     -->Accept the current value by pressing Enter.

     Note: This is the default location of the RequisitePro projects catalog file on the server. Modify this value if you have a different configuration.

   • `Language' is en --> Press Enter to accept the default setting of "en" for English. Do not change this value unless your version of RequisiteWeb has been translated into your local language. This value is based on ISO639 language code standards. If you are using a Japanese version of RequisiteWeb, use the value "ja".
   • `Country' is US --> Press Enter to accept the default setting of "US" for United States. Do not change this value unless your version of RequisiteWeb has been translated into your local language. This value is based on ISO3166 country code standards. If you are using a Japanese version of RequisiteWeb, use the value "jp".

   Note: The RWConfig values are stored in the following file:

C:\Program Files\Rational\jakarta-tomcat\webapps\
ReqWeb\WEB-INF\classes\config.txt

SSL (Secure Socket Layer)

RequisiteWeb supports SSL, an encryption system developed by Netscape that protects the privacy of data exchanged between a Web site and an individual user. If you chose to use SSL with RequisiteWeb, you must perform the following procedure:

1. Navigate to the following directory:

   C:Program Files\Rational\Jakarta-tomcat\webapps\ReqWeb\WEB-INF\classes 
   

2. Using a text editor, open the config.txt file.
3. Search for the following statement in the config.txt file:

   	SSL=false 
   

4. Replace SSL=false with SSL=true.
5. Save and close the config.txt file.
6. Stop and start the Internet Services Manager by doing one of the following:
   • In Windows NT 4.0, open an MS-DOS shell and type the following:

     net stop w3svc

     net start w3svc

   • In Windows 2000, click Start > Programs > Administrative Tools/Internet Services Manager. Right click your server name and select Restart IIS. The Stop/Start/Reboot dialogue box appears. Select Restart Internet Services and click OK.

Reboot Required

At this point you must restart your system. After rebooting, log in as the same user to complete the installation procedure.

Testing RequisiteWeb

To test a RequisitePro project in RequisiteWeb:

1. Open your browser.

Note: Do not use Netscape 4.X when testing RequisiteWeb from the web server machine.

2. Set the URL address to the full path to the login page in the RequisiteWeb virtual directory; for example: http://<server name>/reqweb

   Note: Be sure to use the server name rather than an IP address.

3. Navigate to that address. The RequisiteWeb login page appears.
4. Select a RequisitePro project that contains documents from the Project list. If your project does not appear on the list, refer to the procedure Managing RequisitePro Projects for RequisiteWeb.
5. Type your RequisitePro User name and Password and click Log in.
6. Click a package icon in the Explorer, select a document and open it. When the document opens, RequisiteWeb has been properly installed.

   Note: If the Microsoft Word installer appears, you must allow it to complete.

Managing RequisitePro Projects for RequisiteWeb

Although RequisiteWeb provides features for accessing and editing requirements and documents in projects, you must use the full RequisitePro PC client application to create projects and documents. RequisitePro offers project templates and other management tools for creating and modifying project structure and security. For more information, refer to the Rational RequisitePro User's Guide or the RequisitePro online help.

Using the RequisiteWeb Project Catalog

RequisiteWeb uses a catalog text file to provide access to RequisitePro projects. By default, the file contains entries for the RequisitePro Learning Project and another sample project. The projects that are listed in your catalog file appear in the Projects drop-down list box on the RequisiteWeb logon page.

To add your own projects to the catalog, you must type the full path for the project file, which has a .rqs extension. For instructions on modifying the catalog, see Editing the RequisitePro Projects Catalog.

Editing the RequisitePro Projects Catalog

To edit the catalog, perform the following procedure on the RequisiteWeb server:

1. Navigate to the directory:
   C:\Program Files\Rational\RequisitePro\ReqWeb\Projects

   Note: If your projects are installed in a directory other than C:\ you must edit the catalog.txt file to reflect the correct installation directory.

2. Using a text editor, open the catalog.txt file.
3. Create an entry on each line with the full path to the RequisitePro project file. Copy the format of the default project entries.

   Note: Use a full path for local projects on the RequisiteWeb server. To access projects on another server, you must specify a Universal Naming Convention (UNC) path to the shared folder containing the RequisitePro .rqs file. For example, \\server_name\full_path\my_project.rqs

4. Save and close the catalog.txt file.

Note: To view updates to the catalog.txt file, you must log off RequisiteWeb and then select a project at the RequisiteWeb project "log in" page.

Database Projects

RequisiteWeb can open SQL Server- and Oracle-based projects that are not physically located on the RequisiteWeb server; however, the ReqWebUser domain user must have Change or Modify permission for the directory containing the RequisitePro (.rqs) project file on the remote project server.

To access RequisitePro projects that are stored in an Oracle database, you must configure Oracle client software on the server. Refer to the sections "Setting Up PCs for Oracle Access" in the Rational RequisitePro Installation Guide. That section refers to a RequisitePro installation on a client PC; you must perform that procedure on the RequisiteWeb server.

Configuring E-mail for Discussions

To configure e-mail for RequisitePro discussions, refer to the Rational RequisitePro Installation Guide. You use the same Rational E-mail Reader session for both RequisitePro and RequisiteWeb; however, note the following requirements when configuring the Rational E-mail Reader for both RequisitePro and RequisiteWeb:

• You must run the Rational E-mail Reader on a different server than the RequisiteWeb server.
• To enable e-mail for RequisiteWeb discussions, you must configure discussion e-mail using the SMTP protocol option in the Rational E-mail Reader. The MAPI protocol option is not supported for RequisitePro or RequisiteWeb.
• The E-mail Setup option on the RequisitePro Tools menu does not configure e-mail for RequisiteWeb discussions. Use the Rational E-mail Reader, as described in the Rational RequisitePro Installation Guide, to configure e-mail for RequisiteWeb discussions.

Upgrading RequisiteWeb 2002.05.0X and 2001A

To upgrade from RequisiteWeb 2002.05.0X or 2001A to RequisiteWeb 2002.05.20 you must first uninstall RequisiteWeb as decribed in the Uninstalling RequisiteWeb section below, then proceed with the install as decribed in the Installing RequisiteWeb on the Server section of this document.

Uninstalling RequisiteWeb

This section describes how to remove RequisiteWeb from a RequisiteWeb server. Before you remove RequisiteWeb from your system, make sure that no one is using RequisiteWeb or any associated files. You will not be able to remove files that are in use.

RequisiteWeb installs a new project catalog containing paths to new sample projects. Be sure to make a copy of your existing catalog.txt file before removing RequisiteWeb. If you are upgrading from an earlier release of RequisiteWeb, the catalog.txt file should be located in the following default directory: C:\Program Files\Rational\RequisitePro\ReqWeb\projects

Add your previous catalog.txt entries to the new catalog file that is installed with the new version of RequisiteWeb in the default directory: C:\Program Files\Rational\RequisitePro\ReqWeb\Projects

For more information, see Managing RequisitePro Projects for RequisiteWeb.

For specific instructions on uninstalling RequisiteWeb, see one of the following sections below:

• Removing RequisiteWeb 2002.05.0X
• Removing RequisiteWeb 2001A

Removing RequisiteWeb 2002.05.0X

To remove RequisiteWeb from a Windows NT or Windows 2000 server, you must have Windows administrator privileges on that machine. Use the following instructions to:

• Delete the ReqWeb and Jakarta virtual directories
• Remove the Jakarta ISAPI filter
• Restart the IIS Admin Service
• Remove the RequisiteWeb program files

Delete the ReqWeb and Jakarta Virtual Directories

1. Launch the Internet Services Manager by doing one of the following:
   • Click Start > Run, and type inetmgr. Click OK.
   • In Windows NT 4.0, click Start > Programs > Windows NT 4.0 Option Pack > Microsoft Internet Information Server > Internet Service Manager.
   • In Windows 2000 Server, click Start > Programs > Administrative Tools/Internet Services Manager.
2. Select the Default Web Site and click the Stop button on the toolbar.
3. Right-click the ReqWeb virtual directory and select Delete.
4. Right-click the Jakarta virtual directory and select Delete. Leave the Internet Services Manager open.

Remove the Jakarta ISAPI filter

1. Right-click the Default Web Site and select Properties. The Default Web Site Properties dialog box appears. Click the ISAPI Filters tab and select the jakarta filter.
2. Click Remove and click OK to close the dialog box.

Restart the IIS Admin Service

Perform the instructions in the following table. Refer to the column that corresponds to your operating system.

Step	Windows NT 4.0	Windows 2000
1	Close the Internet Service Manager.	In the Internet Services Manager, right-click the server name.
2	At the Start/Run command line, type cmd.	Select Restart IIS.
3	In the MS-DOS window, type the following: net stop w3svc net start w3svc.	At the Stop/Start/Reboot dialog box, select Restart Internet Services on <server name>.
4	Type exit to close the MS-DOS window.	Click OK to close the dialog box. Close the Internet Services Manager.

Remove RequisiteWeb 2002.05.0X

Use the Add/Remove Programs function in the Windows Control Panel to select and remove the Rational product you installed. After the uninstall process is complete and you have restarted your machine, check to see if the C:\Program Files\Rational directory is still present on the server. If so, delete the Rational directory and its subdirectories. You must also perform the following steps to edit your System Variables:

1. On the start menu, click Settings > Control Panel. In the Control Panel, double-click the System icon. The System Properties dialog box appears.
2. Do one of the following:
   • In Windows 2000, at the Advanced tab, click Environment Variables.
   • In Windows NT, click the Environment tab.
3. Locate the PATH system variable and remove the following from your PATH directory:

   C:\Program Files\Rational\common\java\jre\bin 
   

Removing RequisiteWeb 2001A

To remove RequisiteWeb from a Windows NT or Windows 2000 server, you must have Windows administrator privileges on that machine. Use the following instructions to:

• Stop and remove the RqTomact Service
• Remove the ReqWeb and Jakarta virtual directories
• Remove RequisiteWeb 2001A
• Remove the Tomcat_Home and Java_Home system variables

Stop and Remove the RqTomcat Service

Step	Windows NT 4.0	Windows 2000
1	Go to Start > Settings > Control Panel > Services.	Go to Start > Settings > Control Panel > Administrative Tools > Services.
2	Locate and select the RqTomcat service.	Locate the RqTomcat service and double-click the icon to display the Properties dialog box.
3	In the Services window, click the Stop button.	On the General tab under Service status, click the Stop button. Click OK and close the Services window.
4	Click Close to finish.	Click OK to close the dialog box. Close the Internet Services Manager.

After you stop the RqTomcat service you must perform the following steps to remove the service from your system:

1. Open an MS-DOS shell and navigate to the following directory:

   C:\Program Files\Rational\jakarta-tomcat\bin 
   

2. Type the following at the MS-DOS prompt:

   jk_nt_service -R RqTomcat 
   

3. Close the MS-DOS shell

Remove the ReqWeb and Jakarta Virtual Directories

1. Launch the Internet Services Manager by doing one of the following:
   • In Windows NT 4.0, click Start > Programs > Windows NT 4.0 Option Pack > Microsoft Internet Information Server > Internet Service Manager.
   • In Windows 2000 Server, click Start > Programs > Administrative Tools > Internet Services Manager.
2. Under the Default Web Site, locate the ReqWeb and Jakarta virtual directories. Right-click each of the directories and select delete.
3. Right-click the Default Web Site and select Properties.
4. At the ISAPI Filters tab, locate the jakarta filter. Right-click the jakarta filter and select delete.
5. Click OK and close the Internet Services Manager.

Remove RequisiteWeb 2001A

Use the Add/Remove Programs function in the Windows Control Panel to select and remove the Rational product you installed. After the uninstall process is complete and you have restarted your machine, check to see if the following directories are still present on the server:

C:\Program Files\Rational\RequisitePro
C:\Program Files\Rational\jakarta-tomcat

If so, delete both directories and their subdirectories.

Remove the Tomcat_Home and Java_Home System Variables

1. On the start menu, click Settings > Control Panel. In the Control Panel, double-click the System icon. The System Properties dialog box appears.
2. Do one of the following:
   • In Windows 2000, at the Advanced tab, click Environment Variables.
   • In Windows NT, click the Environment tab.
3. Locate the TOMCAT_HOME and JAVA_HOME system variables and delete them from your system.

To complete the upgrade process, skip to the Installing RequisiteWeb on the Server section of the document and proceed with the rest of the instructions.

Note: Restore back up projects and your catalog.txt file to their original locations.

Known Issues

Many of the issues listed below include "workarounds" that you should implement when configuring your RequisiteWeb server or client browsers.

Accessing RequisiteWeb Pages and Projects

• In some cases, when a user opens the RequisiteWeb log in page, the browser displays the source code for the page rather than the interpreted HTML. Verify that the isapi_redirect.dll is properly installed and configured. (14040)
• After you install or upgrade RequisiteWeb, you may not be able to see the projects that are not located on your RequisiteWeb server in the Projects drop-down list box, even though they are listed in your catalog.txt file. To refresh the project list, run the DCOM configuration application by typing dcomcnfg at the Start > Run command line. The DCOM application appears. Close the DCOM application. Check your projects list in RequisiteWeb. For more information see Managing RequisitePro Projects for RequisiteWeb. (14785)
• While using RequisiteWeb, closing the browser without clicking the "Log Out" button may result in an error. A user temp file is created in the ReqPro project folder whenever someone logs onto the project via ReqWeb. When you select the "Log Off" button from ReqWeb, this temp file is correctly cleared. However, if the browser is closed without clicking the "Log Out" button, then the temp file is not automatically cleared. Exclusive access cannot be gained to the project while this temp file is present. The temp file cannot be removed unless either the ReqWeb server is re-booted, or the RqTomcat process is stopped and restarted.
• When you launch a browser from another browser and login in at the exact same time, both browsers attempt to share the same session causing IIS to crash. (15035)

Viewing and Downloading Documents

Download vs. View

RequisiteWeb gives you the ability to download requirements documents and save them to disk in Microsoft Word format. On the Documents page in RequisiteWeb, click a file name in the Download File column.

When downloading a document, you have the options of opening or saving the document. Opening the document at this point may cause a program failure or erroneous display. Be sure to save the document to disk, and then open it using Microsoft Word. If a "Navigation Canceled" page or blank page is displayed after you save the document, click the Back button or the Documents icon to return to the documents list.

Note: To view the document in your browser, click the document name in the Explorer. The requirements document is converted to HTML and appears in RequisiteWeb.

If you cancel a document download operation from the download dialog box, and then select the download option in RequisiteWeb again, the document may be displayed in the browser yet not be presented in the download dialog box. To fix this condition, refer to Microsoft Knowledge Base article Q162059 at http://support.microsoft.com/support/kb/articles/Q162/0/59.asp (8740)

When you download a document in Netscape, spaces and other HTML special characters in the document name are replaced by HTML character codes. These characters are a result of the URL encoding that RequisiteWeb applies to the address of the document. Netscape displays the HTML character codes in the file name field of the document Save As dialog box. When you save the document, the characters are replaced by the original spaces and/or special characters. (7186)

Other Document Viewing Conditions

Other conditions may prevent you from viewing project documents in RequisiteWeb:

• You cannot view documents in RequisiteWeb if their file names contain a pound symbol (#). The # character has special significance in HTML, so the RequisiteWeb browser cannot correctly interpret document file names that contain this character. (8623)
• If the RequisitePro project contains documents with similar names, which are only distinguishable by international fonts (for example, abc.tst and ábc.tst), RequisiteWeb may fail to distinguish between the documents. An error message similar to the following will be displayed:

  Error creating viewable document: 
  Error updating ReqPro document into HTML. 
  Error creating HTML document. 
  The folder that this Web page would use to organize supporting files is already reserved for use in the current location. Please choose a different name or location for this Web page. 
  (8307) 
  

• Microsoft Word contains a known issue that prevents successful conversion of special characters in Word to HTML. This problem causes RequisiteWeb to "lock-up" when the user clicks a hyperlink to a document in RequisiteWeb.
  Resolution: Refer to Microsoft KnowledgeBase article Q174315 on the Microsoft technical support Web site at http://support.microsoft.com/support/kb/articles/Q174/3/15.asp.
• If you install Microsoft Internet Explorer version 4 with Service Pack 1 (IE4 SP1) on the RequisiteWeb server, the HTML converter will no longer be available in Microsoft Word. In this case, an error message appears when the user attempts to view a document in RequisiteWeb.
  Resolution: Refer to Microsoft KnowledgeBase article Q193736 on the Microsoft technical support Web site at http://support.microsoft.com/support/kb/articles/Q193/7/36.asp
• If the RequisitePro project document when viewed in RequisiteWeb, contains significant formatting problems, refer to the following articles in the Microsoft KnowledgeBase:
  - WD2000: Limitations of Converting from Word Document Format to Web Page Format; at the Microsoft KnowledgeBase Web site (http://support.microsoft.com/support/search), there are several other HTML conversion articles for your review. These can be located by searching on the keywords wd2000, kbconversion, and kbhtml.
• A view created in RequisitePro may not include requirement name and text when opened in RequisiteWeb. To correct the error, modify the properties of the view in RequisiteWeb to show name and text. (19251)

Security for RequisiteWeb Documents

Documents that are viewed or downloaded using RequisiteWeb are converted from RequisitePro format to Microsoft Word or HTML formats. Therefore, these copies can be viewed by unauthorized users on the RequisiteWeb server using MS Word or a web browser.

If document security is an issue, be sure to limit access to the GenDoc directory on the RequisiteWeb server.

Note: The ReqWebUser user must have create/read/write permissions for the GenDoc directory.

RequisiteWeb Discussions

• When you remove multiple requirements from a discussion in RequisiteWeb, some requirements may not be removed. (15401)
• When you remove multiple participants from a discussion in RequisiteWeb, some participants may not be removed. (15376)

RequisiteWeb Requirements

• The requirement history shown in the "Last Saved" section of the Requirement page may not list all attributes. (14311)
• When you use the manually hyphenate option in Microsoft Word, requirements are not displayed properly in the Attribute Matrix. (18168)
• If you insert an image into requirement text, the requirement is not displayed in an Attribute Matrix. (18171)

Modifying Requirement Traceability in RequisiteWeb

• If you create a circular traceability relationship, RequisiteWeb displays an appropriate error message. To continue editing the requirement, you must view a different requirement or log out of the project and log in again. (13860)
• In the "traced-from" and "traced-to" columns, internal requirement tags (from the current project) are being displayed as external requirement tags (having a project prefix). (16026)
• If you have a project containing traceability to a disconnected external project, you may have problems seeing local views. (16053)
• You cannot display the traceability of a requirement that has cross project traceability links to a disconnected project. (16060)

Filtering Views in RequisiteWeb

• You can filter a view on Trace To or Trace From criteria, but not both; if you attempt to do so, an error message is displayed. (15373)
• When filtering views, the sort rank numbers are not retained when sorting by multiple attributes with the document position as the first one. However, the sort rank does function properly. (15500)
• When you filter a view, if you select "Not traced-from" or "Not traced-to" in the "Operator" column, you will not be able to use the Filter button, which opens the page that allows you to add when-traced criteria. (16102)
• A saved view with the "Unique ID" field selected on the client will not be visible on the web. In order to view the "Unique ID" field, you must reconfigure the view on the web by selecting the "Unique ID" field again and save the view. (16391)

User Preferences

Preferences are stored in cookies, not in the database. As a result, set preferences are browser specific and not user specific. (15983)

Running RequisiteWeb on International Operating Systems

• Do not install RequisiteWeb into a directory with double-byte characters. (15532, 26496)
• When double-byte characters are used in the project path, project name, or document names and you are running Netscape on the simplified Chinese version of Windows, you cannot download a requirements document in RequisiteWeb; instead, the Documents page in RequisiteWeb is downloaded. (11601)
• Do not use double-byte characters in RequisiteWeb project user names. (15442)
• Using double-byte characters in RequisiteWeb project names with SSL enabled may cause files to fail and may compromise project security. (18033)
• Do not use double-byte numerical attribute values in RequisiteWeb requirements. (15425)
• When you use double-byte characters in Netscape 4.7 or earlier, you must use your own default fonts and not document-specified fonts. (18162)
• When you use double-byte characters in Netscape 4.7 the characters will not be visible in the "requirement display" window. (14757)
• RequisiteWeb only supports characters contained in the servers character set. (16725)

File Naming

• Your files must be named using valid Windows file names.
• Your files must be named using valid URL characters.

Word-Linked Files

• Requirements in Word documents must link to external files using the Uniform Naming Convention (UNC) for the link references in order for you to view the linked files in RequisiteWeb.
• If RequisiteWeb detects a tag within a requirement text, only the requirement tag appears as a hyperlink.
• Word-linked files must be stored in the same network domain. RequisiteWeb cannot display Word-linked files that are stored in separate network domains. (16996)
• Attempting to view a document containing a Word-linked file that has been removed from or moved to a different file system will cause your web server to freeze.

Netscape

• In Netscape 4.X, if you resize the browser window while the packages in the Explorer are expanded, all packages are collapsed. Reopen the packages as needed. (15567)
• You must change the following setting when using Netscape 6.01 to verify that changes made to a document in RequisitePro are immediately available in RequisiteWeb:
  • From the Edit menu select Preferences, expand the Advanced category list and select Cache. Under the Compare the page in the cache to the page on the network heading select the Every time I view the page option.
• In Netscape 6, the back button may not always work. (17555)
• In Netscape 6, the Back to the Top link in the Discussion section does not work. (17438)

Installing RequisiteWeb

This defect applies to RequisiteWeb installations using Windows NT 4.0 SP 6a or Windows 2000 Advanced Server and JRE version 1.3.0. When any user logs off the server, the IIS service is terminated. For assistance, contact Rational technical support. (RATLC00030933)

Contact Information

Rational Software Corporation

Corporate Headquarters:

Rational Software Corporation
18880 Homestead Road
Cupertino, CA 95014
Toll-free: 800-728-1212
Telephone: 408-863-9900
Fax: 408-863-4120
E-mail: info@rational.com

Technical Support:

Telephone: 1-800-433-5444 or 408-863-5000 (outside the U.S. and Canada)
Fax: 408-863-4300
E-mail: support@rational.com
Web site: http://www.rational.com

Visit our Web site for more information about us!