Installing and Configuring Rational RequisiteWeb

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 describes how to set up that configuration.

This document contains the following sections:

Configuring the RequisiteWeb Server

Before you configure the RequisiteWeb server, 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.

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

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 a version of Oracle earlier than Oracle 8.1.7.

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 ReqWeb user on the Windows domain server, be sure to log on to your Windows domain server as an administrator.

Creating a Domain User
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 on 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 logon and select the check box Password never expires. Click Add. Clear the check box User must change password at next logon 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.
6 Close the User Manager application. Close the Computer Management application.

Adding the ReqWeb User to the Local Administrator Group

Note: Be sure to log on to your RequisiteWeb server as a local user for the following procedure.

Adding the ReqWebUser to the Local Administrators
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 menu. 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 Windows server, the ReqWebUser must have Change or Modify permission for the directory containing the RequisitePro (.rqs) project file on the remote file server.

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.
  1. Select the Default Security tab. Under Default Access 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 menu.
  4. Select the Administrators group in the Names list and click Add.
  5. 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 menu.
  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: For current RequisiteWeb users, be sure to remove any earlier version of RequisiteWeb prior to installing 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 on 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. Select or clear the following optional check boxes:
    • If you plan to use this machine for creating and managing RequisitePro projects, leave the RequisitePro check box selected. If you plan to use this machine only for hosting RequisiteWeb, you can clear it.
    • Leave the Rational Synchronizer check box unmarked.
    • 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.
    • The Oracle Setup and SQL Server Setup options are required for database administrators who are configuring Oracle or SQL Server databases for RequisitePro projects.

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 on as the same user to complete the installation procedure.

To complete your RequisiteWeb install, 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.

Note: If you do not install your Rational product in the default C:\ directory, you must edit your wrapper.properties file as follows:

Configuring Web Server Components

This section presents procedures for installing and configuring Web Server components on a Windows IIS Server. Be sure to log on as an administrator before you begin the installation process. These instructions assume that you have installed Microsoft IIS on your system and that it is running. For more information on IIS, see Microsoft Servers at http://www.microsoft.com/servers.

This section contains the following procedures:

  1. Configuring the Tomcat Servlet Engine
  2. Testing Tomcat
  3. Creating a ReqWeb Virtual Directory on IIS
  4. Creating a Jakarta Virtual Directory on IIS
  5. Adding a JSP Filter

Note: The instructions in this document assume that you are installing Windows applications on your C:\ drive. Substitute the appropriate drive, if necessary, when performing all procedures.

Configuring the Tomcat Servlet Engine

To configure Tomcat on your Windows IIS server:

  1. Open an MS_DOS shell and navigate to the following directory:
    C:\Program Files\Rational\jakarta-tomcat\bin
  2. Within this directory type the following:
    tomcat_svc
  3. Close the MS_DOS shell.
  4. Run Tomcat as a service and make the RqTomcat service start automatically during the system start up by completing one of the following sets of procedures depending on your system:
Step Windows NT Windows 2000
1 Go to Start > Settings > Control Panel > Services. Go to Start > Settings > Control Panel > Administrative Tools > Services.
2 Locate the RqTomcat service and double-click on the icon to display the Properties dialog box. Locate the RqTomcat service and double-click on the icon to display the Properties dialog box.
3 Select Automatic under Startup type. On the General tab, select Automatic in the Startup type drop-down menu.
4 Under Log On As select This account. Select the Log On tab and then select This account.
5 In the This account and Password dialog boxes, type the name and password of the domain and the domain user that is used for RequisitePro (e.g. "Domain"\ReqWebUser). Note: You must replace the "Domain" entry with the correct RequisiteWeb domain. Click OK. In the This account and Password dialog boxes, type the name and password of the domain and the domain user that is used for RequisitePro (e.g. "Domain"\ReqWebUser). Note: You must replace the "Domain" entry with the correct RequisiteWeb domain.
6 In the services window, click the Start button. On the General tab under Service status, click the Start button.
7 Click Close to finish. Click OK to finish.

Note: If you receive an error message while attempting to run the Tomcat service, refer to the Troubleshooting section of this document.

Testing Tomcat

To verify that Tomcat is installed and configured correctly, open a browser on your RequisiteWeb Windows server and enter the following URL address: http://localhost:8080/servlet/SnoopServlet

Note: The URL is case sensitive.

Snoop Servlet is a Tomcat web page that displays information about your Tomcat installation. The words "Snoop Servlet" should appear at the top of the displayed web page. If they do not, check the steps for installing Tomcat (above), or refer to the Troubleshooting section of this document.

Once your Tomcat test is complete you must locate the RequisiteWebInstall.html, RequisiteWebUNIXInstall.html, RequisiteWebWindowsInstall.html, and copyright.html files on your Rational Solutions for Windows CD and copy them to the following directory:

C:\Program Files\Rational\Jakarta-tomcat\webapps\ReqWeb

Note: If you installed Tomcat to a directory other than C: you must copy these files to the directory that Tomcat was installed.

Creating a ReqWeb Virtual Directory on IIS

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

  1. Launch the Internet Service 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 New Virtual Directory.
  3. In the Virtual Directory Creation Wizard, click Next and type an Alias: ReqWeb.
  4. Click Next and browse to and select C:\Program Files\Rational\jakarta-tomcat\webapps\ReqWeb
  5. Click Next. If you are using Windows 2000, make sure that only the Read and Run options are checked; if you are using Windows NT, make sure that only the Read and Script options are checked.
  6. Click Next and Finish to complete the wizard.

Creating a Jakarta Virtual Directory on IIS

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

  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 New > Virtual Directory.
  3. In the Virtual Directory Creation Wizard, click Next and type an Alias: jakarta.
Note: The alias, jakarta, must be lower-case.
  1. Click Next and browse to and select C:\Program Files\Rational\jakarta-tomcat\jakarta
  2. Click Next. If you are using Windows 2000, make sure that only the Read, Run, and Execute options are checked; if you are using Windows NT, make sure that only the Read, Script, and Execute options are checked.
  3. Click Next and Finish to complete the wizard. Leave the Internet Services Manager open.

Adding a JSP Filter

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

  1. Right-click on the Default Web Site and select Properties.
  2. At the ISAPI Filters tab, click Add.
  3. Type the filter name: jakarta
Note: The filter name, jakarta, must be lower-case.
  1. 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.
  1. Click OK to close the dialog boxes.
Note: To test your JSP filter, right-click on the Default Web Site, select Properties ,and click the ISAPI Filters tab. A green up-arrow should appear next to jakarta under the Status column.
  1. Leave the Internet Services Manager open.
ReqWeb Virtual Directory Configuration in IIS
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.
9 Close the Internet Service Manager. Close the Internet Services Manager.


Testing RequisiteWeb

To test a RequisitePro project in RequisiteWeb:

  1. Open your browser.
  2. Set the URL address to the full path to the logon 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 logon 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 On.
  6. Click the Documents icon, 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 guide Using Rational RequisitePro 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 on the RequisiteWeb logon page.

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

Accessing Projects on Different Servers

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

RequisiteWeb can open projects that are not physically located on the RequisiteWeb server; however, in this case the ReqWebUser domain user must have Change or Modify permission for the directory containing the RequisitePro (.rqs) project file on the remote project server.

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

Important: You must install the Oracle client software before installing the JDK if you are using a version of Oracle that is earlier than 8.1.7.

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
  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 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.
  4. Save and close the catalog.txt file.

Note: In order to view updates to the catalog.txt file, users must log off RequisiteWeb and then select a project at the RequisiteWeb project logon page.

Configuring E-mail for Discussions

To configure e-mail for RequisitePro discussions, refer to the guide Installing Rational RequisitePro. 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:

Uninstalling RequisiteWeb

This section describes how to remove RequisiteWeb from a RequisiteWeb server. Prior to removing 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:\Inetpub\wwwroot\reqweb

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.

Removing RequisiteWeb

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:

Removing or Redirecting the ReqWeb Virtual Directory

  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 on the ReqWeb virtual directory and select Properties. The ReqWeb Properties dialog box appears. Click the Virtual Directory tab.
  4. Depending on whether you are upgrading or simply removing RequisiteWeb from your system, do one of the following:
    • If you are upgrading to a new version of RequisiteWeb, do not delete your ReqWeb virtual directory. After you have installed your new version of RequisiteWeb, you will redirect the ReqWeb virtual directory to the new path, described in Creating a ReqWeb Virtual Directory on IIS.
    • If you are not upgrading, but simply removing all RequisiteWeb components from your system, click Remove and click OK to close the dialog box.

Stopping 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 Advanced Server
1 Close the Internet Service Manager. In the Internet Services Manager, right-click on 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 iisadmin /y and press Enter. At the Stop/Start/Reboot dialog box, select Stop Internet Services on <server name>.
4 The following message appears: "The IIS Admin Service was stopped successfully." The C:\ prompt appears after the command is successfully executed. Type exit to close the MS-DOS window. Click OK to close the dialog box. Close the Internet Services Manager.

Removing the rqTomcat Service

Open an MS_DOS shell and navigate to the following directory:

C:\Programm Files\Rational\Jakarta-tomcat\bin

Type and execute the following command:

jk_nt_service.exe -R rqtomcat

Removing the RequisiteWeb Program

Use the Add/Remove Programs function in the Windows Control Panel to select and remove RequisitePro. After the uninstall process is complete, check to see whether the C:\Program Files\Rational\RequisitePro\ReqWeb directory is still present on the server. If it is, delete the ReqWeb directory and its subdirectories.

Restarting the Web Publishing 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 Advanced Server
1 In the MS-DOS window, type the following: net start w3svc and press Enter. In the Internet Services Manager, right-click on your server name.
2 The following message appears: "The World Wide Web Publishing Service was started successfully." The C:\ prompt appears after the command is successfully executed. Select Restart IIS. At the Stop/Start/Reboot dialog box, select Restart Internet Services on <server name>.
3 Type exit to close the MS-DOS window. Click OK to close the dialog box and close the Internet Services Manager.

Note: You must remove JAVA_HOME and TOMCAT_HOME system variables to complete the uninstall process.

Troubleshooting

Tomcat

If you receive an error message while attempting to run the Tomcat service, right-click on My Computer and choose properties. In the System Properties dialog box, select the Advanced tab and choose Environment Variables. Check the following values under System variables:

  1. java_home
    This should point to the jre installed with your Rational product. By default the location is C:\Program Files\Rational\common\java\jre1.2.2
  2. tomcat_home
    This should point to the Tomcat installed with your Rational product. By default the location is C:\Program Files\Rational\jakarta-tomcat
  3. path
    This should include the java executable installed with your Rational product. By default the location is C:\Program Files\Rational\common\java\jre1.2.2\bin
  4. In your Windows Explorer navigate to C:\Program Files\Rational\jakarta-tomcat\bin. Using a text editor, open the wrapper.properties file and check your java_home and tomcat_home paths.

Known Issues

Note that 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

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 using Microsoft Internet Explorer, 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. After saving the document, if a "Navigation Canceled" page or blank page is displayed, click the Back button or the Documents icon to return to the documents list.

Note: To view the document immediately in your browser, click the document name in the Document column. The requirements document is converted to HTML and displayed 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 and RequisiteWeb fails to present 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 downloading 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 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

The following are other conditions that may prevent successful viewing of project documents in RequisiteWeb:

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 potentially 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

RequisiteWeb Requirements

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 on again. (13860)

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)

Running RequisiteWeb on International Operating Systems

Word-Linked Files

File Naming

Netscape 6

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: ratlinfo@us.ibm.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!