Installing and Configuring IBM Rational RequisiteWeb

V2003.06.13, September 2004

This file last updated: August 9, 2004

Material ID/Part Number: GI11-5902-03


(C) Copyright IBM Corporation. 1995, 2004. All Rights Reserved.

Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Corporation.

Legal Notices Information

The complete listing of IBM Rational Legal Notices is automatically installed with IBM Rational Suite products in <Install Path>\Rational\doc\legal_information.html. Optionally, the Legal Notices can be found on the "IBM Rational Solutions for Windows CD-ROM" at \doc\legal_information.html.


Scope

IBM(R) Rational(R) RequisiteWeb enables users to read, create, and modify IBM Rational RequisitePro(R) project requirements and documents across a network. RequisiteWeb uses the Microsoft Internet Explorer and Netscape Navigator browsers to provide platform-independent, thin-client access to RequisitePro project data. RequisiteWeb can access projects that use IBM DB2, Oracle, Microsoft SQL Server, or Microsoft Access databases. RequisiteWeb must be installed on a Windows server.

This document contains information on installing and configuring RequisiteWeb. It includes system requirements and known issues. Go to IBM Rational RequisiteWeb Service Release 2003.06.13 Release Notes for information on what's new and fixed defects in this release of RequisiteWeb, or if you are upgrading from:

Product changes described in this document and contained within this service release apply to:

These Release Notes are accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications Center at http://www.ibm.com/shop/publications/order. Search for "GI11-5902-03" to find the latest version of these Release Notes in the IBM Publications Center. (To search for the IBM Publications Center, go to http://www.ibm.com and enter "IBM Publications Center" in the Search field.)

Contents

What's New in This Release
RequisiteWeb System Requirements
Configuring the RequisiteWeb Server
Configuring RequisiteWeb for Internet Use
RequisiteWeb and IIS
Testing RequisiteWeb
Managing RequisitePro Projects in RequisiteWeb
Configuring E-mail for Discussions
Upgrading RequisiteWeb 2002.05.X and 2001A
Uninstalling RequisiteWeb
Known Issues
Contacting IBM Rational Software Support

What's New in This Release

RequisiteWeb Tabbed Requirement Properties pages

RequisiteWeb now offers access to all requirement properties through a set of tabbed pages that correspond to the Requirement Properties dialog box in the RequisitePro Windows client. This centralizes requirement creation and editing in a concise user interface. The tabbed pages include the following:

Creating Requirements in a RequisiteWeb Attribute Matrix

You can now create a new requirement from within an Attribute Matrix. The Create Requirement button appears at the bottom of each Attribute Matrix page, and provides access to the tabbed Requirement Properties pages. The new requirement defaults to the requirement type of the Attribute Matrix; it is displayed in the matrix after you save it. For more information, see the topic "Creating and modifying requirements" in the RequisiteWeb online Help.

Editing Requirements in a RequisiteWeb Attribute Matrix

You can now modify requirement attribute values directly in an Attribute Matrix. When you edit in an Attribute Matrix, each value you change is recorded as a separate revision history record. For more information, see the topic "Creating and modifying requirements" in the RequisiteWeb online Help.

RequisiteWeb Traceability Matrix

The Traceability Matrix provides an additional way to manage traceability, complementing the Attribute Matrix and Traceability Tree views that are already available in RequisiteWeb. The Traceability Matrix view presents the relationships between requirements of the same or different types. Use this matrix to view indirect relationships and suspect relationships. You can filter and sort the requirements that are displayed.

Editing Traceability in a RequisiteWeb Traceability Matrix

You can now work directly within a Traceability Matrix to add, remove, and modify a traceability relationship between two requirements. You can also add or remove suspect conditions for the traceability relationship. For more information, see the topic "Viewing and modifying traceability" in the RequisiteWeb online Help.

Simplified Configuration of Rational RequisiteWeb

Configuring your Web server for RequisiteWeb is quick and easy, requiring just five steps: Install the application, specify your username, configure SSL(optional), reboot the machine, and add your projects to the project list.

You can customize the RequisiteWeb Login Page and footer to accommodate your company's needs.

Document Authoring in RequisiteWeb

In RequisiteWeb, you can now create, modify, and delete documents. When you create a document, RequisiteWeb references the new document in the project database. You can take a document offline and modify its content in Microsoft Word, just as you can with RequisitePro.

Configuring RequisiteWeb for Internet Use

Your organization's customers, contractors, and remote team members can now access RequisiteWeb using the Internet. Internet access to live requirements data using RequisiteWeb provides timely, invaluable feedback between your development team and other requirements stakeholders. See the section Configuring RequisiteWeb for Internet Use in this document for guidance on configuring a firewall and proxy server to enable secure access to RequisiteWeb through the Internet.

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 Server 2003 (Enterprise and Standard Editions)
Microsoft Windows 2000 Server SP2, SP3, SP4
Microsoft Windows 2000 Advanced Server SP2, SP3, SP4
Microsoft Windows NT Server 4.0, Service Pack 6A with security roll up package

Processor 500 MHz or greater
Memory 256 MB. For projects with more than 10,000 requirements or Web sites with more than 10 concurrent users, we recommend additional memory.
Disk space RequisiteWeb (includes system DLLs) - 40 MB
Microsoft Word

One of the following:
Microsoft Word 2000 SP2, SP3
Microsoft Word 2002 SP1, SP2
Microsoft Office Word 2003

Note: A license for Microsoft Word is required for each concurrent RequisiteWeb user.

Oracle Database Client (to use projects located in Oracle databases)

IBM DB2 client software (to use projects located in DB2 databases)

compatible with: Oracle 8.1.7, 9i R2, 10g

compatible with: DB2 UDB version 8.1 FixPak 5 or later


Note: RequisiteWeb cannot be installed on a Primary Domain Controller or Backup Domain Controller. RequisiteWeb cannot be run on an ADSI enabled network or a Novell network. RequisiteWeb can be used with SQL Server 2000 "Named Instances."

Client Requirements

Microsoft Word must be installed on the client system in order to edit offline Word documents. To access RequisiteWeb from client machines, you must install one of the following Web browsers on the client system.

Note: For proper RequisiteWeb operation, you must configure your browser to allow cookies and enable JavaScript.

Configuring the RequisiteWeb Server

Before you configure RequisiteWeb, Microsoft Word must be installed on your Windows server.

Note: If you are upgrading RequisiteWeb v2002.05.0X or 2001A, go to the Upgrading RequisiteWeb 2002.05.X and 2001A section of this document.

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

Installing the DB2 or Oracle Client

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

Important: If you are using Oracle version 8.1.7, you must install the Oracle client software before installing RequisiteWeb.

Creating the RequisiteWeb User

RequisiteWeb requires that you create a RequisiteWeb user. The RequisiteWeb user can be given any name. For the purposes of these instructions, the user will be called ReqWebUser. This user will be granted the necessary permissions for RequisiteWeb to operate properly. If all RequisitePro projects that are accessible through RequisiteWeb are located on drives local to the RequisiteWeb server, create ReqWebUser as a local user on the RequisiteWeb server. However, if any of the projects accessible through RequisiteWeb are located on network file shares within your domain, create ReqWebUser as a domain user on your primary domain controller server and grant rights to your project directory.

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

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
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 Local Users and Groups. Right-click Users; select New User.
3 In the Username box, type ReqWebUser and type a password. In the Username box, type ReqWebUser and type a password.
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 Close the User Manager application. Close the Computer Management application.

Adding the ReqWebUser to the Local Administrator Group

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

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
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 In the Groups column, double-click Administrators.

A user selection dialog box opens.

For Windows 2000 Server:
At the Look in box, select the domain where you created the ReqWebUser.

For Windows Server 2003:
Click Advanced. Click Locations and select the domain where you created the ReqWebUser. Click OK. Click Find Now.

4 In the Local Group Properties dialog box, click Add. Select your Domain Server from the List Names From list. 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 dialog box. Click OK to finish.
6 Close the User Manager application. Close the Computer Management application.

Assigning DCOM Permissions to the Local Administrators Group

RequisiteWeb uses DCOM to start Microsoft Word. To achieve this, the ReqWebUser should be a member of the Administrators group on the RequisiteWeb server.

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

For Windows Server 2003:

To Assign Access Permissions to the Local Administrators Group (in Windows Server 2003):

  1. On the Start menu, click Run, and type dcomcnfg.
    The Component Services dialog box appears.
  2. Expand Console Root > Component Services > Computers.
  3. Right-click My Computer and select Properties.

  4. Note: If you see the DCOM Configuration Warning dialog box, close the warning and proceed to the next step.
  5. Select the Default COM Security tab. In Access Permissions, click Edit Default.
  6. In the Access Permission dialog box, click Add.
  7. At the Select Users or Groups dialog box, click Locations.
  8. At the Locations dialog box, select your local machine from the Location list. Click OK.
  9. At the Select Users or Groups dialog box, click Advanced. Click Find Now.
  10. In the Name list, select the Administrators group and click OK. Click OK.
  11. At the Access Permission box, verify that the Allow Access check box is selected.
  12. Click OK to return to the My Computer Properties dialog box.

To Assign Launch Permissions to the Local Administrators Group (in Windows Server 2003):

  1. At the Default COM Security tab, in Launch Permissions, click Edit Default.
  2. At the Launch Permission dialog box, verify that the Launch Permission Allow check box is selected.
  3. Click OK twice.
  4. Close the Component Services dialog box and restart your system.

For Windows 2000 Servers and Windows NT Server:

To Assign Access Permissions to the Local Administrators Group (in Windows 2000 and NT):

  1. On the Start menu, click Run, and type dcomcnfg.
    Note: If you see the DCOM Configuration Warning dialog box, close the warning and proceed to the next step.
  2. Select the Default Security tab. In Default Access Permissions, click Edit Default.
  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 list.
  5. Select the Administrators group in the Names list and click Add.
  6. At the Type of Access box, select Allow Access.
  7. Click OK twice to return to the Distributed COM Configuration Properties dialog box.

To Assign Launch Permissions to the Local Administrators Group (in Windows 2000 and NT):

  1. Select the Default Security tab. In Default Launch Permissions, click Edit Default.
  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. For details, see Uninstalling RequisiteWeb 2002.05.X and 2001A.

To install the RequisiteWeb server components:

  1. Log on to the RequisiteWeb server as a local administrator.
  2. Use the Rational Solutions for Windows CD disc 1 to install RequisiteWeb. 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.
  4. At the Product Selection screen, select Rational RequisitePro from the Rational Product list.

  5. 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 Custom screen, expand the Web Server Components and select RequisiteWeb.

Installation issues:

Microsoft Windows 2000 NTFS "Change Journal" defect can cause file system corruption during installation of Rational products

Under certain circumstances, file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has enabled the Windows "Change Journal" (log). This corruption is caused by a defect in Windows 2000.

Before you install any Rational Version 2003 product on a computer that is running Windows 2000:

  1. Disable all virus detection software.
  2. Read IBM Support Technote 1135295. Go to http://www-1.ibm.com/support/us/search/index.html and search for "Rational Installer Change Journal."
  3. Read Microsoft Knowledge Base article 820888 at http://support.microsoft.com/default.aspx?scid=kb;[LN];820888. This article includes information about an update from Microsoft that fixes the defect.

  4. (RATLC00688306)

Note: Using non-DNS-supported characters, such as an underscore, in the RequisiteWeb server's name can cause the login screen to refresh itself and clear the username and password. (RATLC00058265)

For more information about installing the RequisiteWeb server components, see the IBM Rational Desktop Products Installation Guide, which is available on the IBM Rational Solutions for Windows Online Documentation CD-ROM and at the IBM Publications Center (http://www.ibm.com/shop/publications/order) (To search for the IBM Publications Center, go to http://www.ibm.com and enter "IBM Publications Center" in the Search field.)

Editing the RequisiteWeb Configuration File (optional)

Edit the RequisiteWeb configuration file to relocate the catalog.txt file. This file is used to locate RequisitePro projects.

To use customized RequisiteWeb settings, open the following file in a text editor (the default location is shown):
C:\Program Files\Rational\common\rwp\webapps2\ReqWeb\WEB-INF\classes\config.txt

Considerations:

Setting Description Default
RPXCatalog The path to the project catalog file that is used to locate RequisitePro projects. For example:
RPXCatalog=C:\Program Files\Rational\RequisitePro\ReqWeb\Projects\catalog.txt
<blank>

Enabling SSL (Secure Socket Layer)

RequisiteWeb supports SSL, an encryption system that ensures the confidentiality of data exchanged between RequisiteWeb and a client Web browser. To use SSL with RequisiteWeb, follow the instructions in chapter 9 "Customizing the Rational Web Platform" in the IBM Rational Server Products Installation Guide to enable SSL. This guide is available on the IBM Rational Solutions for Windows Online Documentation CD-ROM and at the IBM Publications Center (http://www.ibm.com/shop/publications/order).

Note: If you are using a proxy server, it is not necessary to configure RWP to enable SSL. Instead, enable SSL on the proxy server.

Granting ReqWebUser Access to Network Projects

Use the instructions in this section if you have projects on network file shares within your domain that are accessible through RequisiteWeb.

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
1 Click Start > Settings > Control Panel > Services. Click Start > Settings > Control Panel > Administrative Tools > Services.
2 Locate and double-click the Rational Web Platform, ReqWeb servlet engine service to display the Service dialog box. Locate the Rational Web Platform, ReqWeb servlet engine service and double-click the icon to display the Properties dialog box.
3 In the Service window under Log On As, click This Account and enter the ReqWebUser and password that you created. Click OK to close the Service window. Select the Log On tab and click This account. Enter the ReqWebUser and password that you created and click Apply. Click OK and close the Rational Web Platform window.
4 Stop and start the Rational Web Platform, ReqWeb servlet engine service and start the Rational Web Platform, HTTP server service to finish. Start or restart the Rational Web Platform, ReqWeb servlet engine service to finish.

Reboot Required

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

Configuring RequisiteWeb for Internet Use

This section describes how to configure your network to provide Internet access to RequisiteWeb. In addition to the overview below, the following procedures are provided:

Your organization's customers, contractors, and remote team members can now access RequisiteWeb using the Internet. Internet access to live requirements data using RequisiteWeb provides timely, invaluable feedback between your development team and other requirements stakeholders.

When configuring Internet access for RequisiteWeb, you must take careful steps to protect your organization’s intellectual property and infrastructure. For this reason, we recommend setting up a firewall to protect your corporate network. You should use a reverse proxy server to monitor and control all access across the firewall between the Internet and resources such as RequisiteWeb on your corporate network. This central access point allows you to focus on securing the proxy server instead of securing every machine on your corporate network. A proxy server also conceals information on your corporate network from Internet users, including the names, locations, and implementation details of resources.

Note: Network security, firewall configuration, and proxy server configuration are complex issues requiring the attention of trained IT staff.

The following steps summarize the configuration tasks for providing Internet access to RequisiteWeb:

  1. Install and configure firewall software or hardware to protect your corporate network from unauthorized access. The firewall should allow Internet users to connect to the proxy server using HTTP or HTTPS.
  2. Identify and configure an appropriate reverse proxy server. This machine will be publicly exposed to the Internet via one network interface and connected to your corporate network (LAN or WAN) on another interface. This machine can also act as the firewall by running the appropriate software.
  3. Select, install, and configure reverse HTTP proxy software to provide access to RequisiteWeb from the Internet. To protect the confidentiality of your requirements data, configure this software to require Internet users connecting to RequisiteWeb to use the encrypted HTTPS protocol.

This document provides guidance on configuring the following reverse HTTP proxy software solutions to work with RequisiteWeb:

Using IBM HTTP Server as a Reverse Proxy Server

To provide access to RequisiteWeb using the IBM HTTP server as a reverse proxy server:

  1. Install IBM HTTP Server version 2.0.42.2 or higher on the proxy server. Note that version 2.0.42.2 requires a patch, as described above.
  2. Note: See the IBM HTTP Server documentation for detailed installation instructions.

  3. Configure the IBM HTTP Server to load the necessary modules by including the following lines in the server configuration context in httpd.conf:
  4. LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_http_module modules/mod_proxy_http.so

  5. Configure the IBM HTTP Server to use secure connections. See the section “Getting started quickly with secure connections” in the IBM HTTP Server documentation.
  6. Configure the IBM HTTP Server to act as a reverse proxy to RequisiteWeb as shown in the following example.

The following is an example excerpt from the server configuration context of httpd.conf that configures the IBM HTTP Server to proxy requests for RequisiteWeb to a server named “rw.rational.com”:

  
<IfModule mod_proxy.c>
   # Disable forward proxy requests
   ProxyRequests Off

   # Allow requests from selected hosts or domains
   <Proxy *>
       Order Allow,Deny
       #Allow from rational.com
   </Proxy>

   # Configure access to RequisiteWeb
   ProxyPass /ReqWeb http://rw.rational.com/ReqWeb
   ProxyPass /reqweb http://rw.rational.com/reqweb
   ProxyPassReverse /ReqWeb http://rw.rational.com/ReqWeb
   ProxyPassReverse /reqweb http://rw.rational.com/reqweb
   ProxyPass /ReqWebSetup http://rw.rational.com/ReqWebSetup 
</IfModule>

Note: You must specify your own “Allow from” directive, based on which hosts you want to allow to access RequisiteWeb.

Note: You must replace “rw.rational.com” with the actual name of the RequisiteWeb server on your corporate network.

Caution: The above example allows unencrypted HTTP access to RequisiteWeb. To require encrypted HTTPS connections, move the above configuration lines into the virtual host context of the virtual host used for secure connections. A virtual host context for secure connections usually contains KeyFile and SSLEnable directives and looks like this:

# Accept connections on port 443
  Listen 443

# Create a virtual host for secure connections
<VirtualHost _default_:443>
  # Set the key database file containing certificate
     KeyFile "C:/Program Files/IBM HTTP Server 2.0/key.kdb"
  # Enable SSL
    SSLEnable
  ...
  # move RequisiteWeb proxy directives here to require HTTPS
</VirtualHost>

Using Apache 2 as a Reverse Proxy Server

  1. Install Apache 2 on the proxy server, including the following modules:
  2. Note: In order to obtain a binary version of Apache 2 that contains mod_ssl, you will most likely need to build Apache 2 from source. See the Apache 2 documentation at http://www.apache.org.

  3. Configure Apache 2 to load the necessary modules by including the following lines in the server configuration context in httpd.conf:
  4. LoadModule ssl_module modules/mod_ssl.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_http_module modules/mod_proxy_http.so

  5. Configure mod_ssl as normal. See the documentation for your release of Apache 2.
  6. Configure Apache 2 to act as a reverse proxy to RequisiteWeb. The following is an example excerpt from the server configuration context of httpd.conf that configures Apache to proxy requests for RequisiteWeb to a server named “rw.rational.com”:
  7. <IfModule mod_proxy.c>
      # Disable forward proxy requests
        ProxyRequests Off
    
      # Allow requests from selected hosts or domains
        <Proxy *>
          Order Allow,Deny
          #Allow from rational.com
        </Proxy>
    
      # Configure reverse proxy requests for RequisiteWeb
        ProxyPass /reqweb http://rw.rational.com/ReqWeb
        ProxyPass /ReqWeb http://rw.rational.com/ReqWeb
        ProxyPassReverse /reqweb http://rw.rational.com/ReqWeb
        ProxyPassReverse /ReqWeb http://rw.rational.com/ReqWeb
        ProxyPass /ReqWebSetup http://rw.rational.com/ReqWebSetup
    
      # Require SSL between browsers and the proxy server for ReqWeb
        <Location ~ "^/(ReqWeb|reqweb)">
           SSLRequireSSL
        </Location>
    </IfModule>
    

    Note: You must specify your own “Allow from” directive, based on which hosts you want to allow to access RequisiteWeb.

    Note: You must replace “rw.rational.com” with the actual name of the RequisiteWeb server on your corporate network.

    Note: The “SSLRequireSSL” directive is optional. Comment it out if you do not want to require encrypted HTTPS connections.

Determining the URL to RequisiteWeb

After you configure your proxy server to access RequisiteWeb, your proxy server appears as if it is a RequisiteWeb server to your Internet users. Internet users can access RequisiteWeb using a URL starting with “http://”or “https://”, followed by the fully qualified Internet host name of the proxy server, such as “rw.rational.com”, and ending with “/ReqWeb”or “/reqweb”.

Local users within your corporate LAN or WAN can use the same URL or replace the fully qualified name of the proxy server with the internal name of the proxy server or the RequisiteWeb server. Using the internal name of the RequisiteWeb server provides the best performance because it bypasses the proxy server; however, RequisiteWeb administrators may prefer that all users access RequisiteWeb using the proxy server host name, because this allows the administrator to replace the RequisiteWeb server or change its name transparently.

RequisiteWeb and IIS

RequisiteWeb uses the Rational Web Platform (RWP). Because RWP and Internet Information Services (IIS) can conflict with one another, you must choose one of the following options to run RequisiteWeb on a system with IIS running:

Disable IIS

The following table explains how you can disable IIS if it is running on your system. After you disable it, any programs using it will no longer work.

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
1 Click Start > Settings > Control Panel > Services. Click Start > Settings > Control Panel > Administrative Tools > Services.
2 Locate and select the World Wide Web Publishing service. Locate the World Wide Web Publishing service and double-click the icon to display the Properties dialog box.
3 In the Services window, click the Stop button and change the Startup type to Disabled. On the General tab under Service status, click the Stop button and change the Startup type to Disabled. Click OK and close the Services window.
4 Click Close to finish. Click OK to close the dialog box. Close the Internet Services Manager.

Change and redirect the default RWP HTTP port

The following steps let RequisiteWeb and IIS coexist. To change and redirect the default RWP HTTP port:

  1. Change the default RWP HTTP port (80) in your rwp.conf file. Follow the instructions “To Change the Default RWP HTTP Port” in the IBM Rational Server Products Installation Guide, which is available on the IBM Rational Solutions for Windows Online Documentation CD-ROM and at the IBM Publications Center (http://www.ibm.com/shop/publications/order).
  2. Create a virtual directory for RequisiteWeb 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/Windows Server 2003, 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 ReqWeb as the alias.
    4. Click Next and browse to and select
      C:\Program Files\Rational\common\RWP\webapps2\ReqWeb and click Next.
    5. Click Next and Finish to complete the wizard.
  3. In the properties of your newly created Virtual Directory, select A redirection to a URL and redirect to: http://<server name>:<new port>/reqweb
  4. Close the Internet Services Manager and restart the Rational Web Platform. Follow the instructions in “Starting and Stopping the Rational Web Platform” in the IBM Rational Server Products Installation Guide.

Testing RequisiteWeb

To test your installation of RequisiteWeb:

  1. Open a Web browser.
  2. Set the URL address to "http://<server name>/reqweb" on your RequisiteWeb server and press Enter.
    Note: If your Internet Explorer window is blank, select Tools > Internet Options. At the Security tab, add RequisiteWeb to your list of trusted sites. Refresh your browser view of RequisiteWeb, if necessary.
  3. 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.
  4. Type your RequisitePro user name and password and click Log in.
  5. Select a document in the Explorer and open it. If the document opens correctly, the test has succeeded; RequisiteWeb has been properly installed.
    Note: If the Microsoft Word installer dialog box opens, you must allow it to complete.

Managing RequisitePro Projects in RequisiteWeb

Although RequisiteWeb provides features for accessing and editing requirements and documents and creating documents in projects, you must use RequisitePro to create projects. RequisitePro offers project templates and other management tools for creating and modifying project structure and security. For more information, see Rational RequisitePro User's Guide or RequisitePro 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 sample projects. The projects that are listed in your catalog appear in the Projects list on the RequisiteWeb log In page.

To add your own projects to the catalog, you must type the full path for the project file, which has an .rqs extension.

Note: Be sure that all projects that are listed in the Web server catalog.txt are accessible at all times. If any project in this file is unavailable, Web server performance for available projects may be affected.

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

  1. Navigate to the directory (by default):
    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 with the full path to the RequisitePro project file (.rqs).
    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 out of RequisiteWeb and then pull down the project field on the RequisiteWeb project "log in" page.

Database Projects

RequisiteWeb can open 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.

Note: To execute the provided SQL Server database scripts, you must be logged in as "sa" or as a user with "System Administrator" and "Security Administrator" privileges.

To access RequisitePro projects that are stored in a DB2 or an Oracle database, you must configure the database client software on the server. For more information, see the manual IBM Rational Desktop Products Installation Guide, which is available on the IBM Rational Solutions for Windows Online Documentation CD-ROM and at the IBM Publications Center at http://www.ibm.com/shop/publications/order.

Configuring E-mail for Discussions

Use the Rational E-mail Reader application to configure e-mail for all discussion participants with a valid e-mail address in their RequisitePro user information. The Rational E-mail Reader application is included with your Rational Software installation at the following default location:
c:\Program Files\Rational\common\mailreader.exe
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:

Upgrading RequisiteWeb 2002.05.X and 2001A

To upgrade from RequisiteWeb 2002.05.X or 2001A to RequisiteWeb 2003.06.X, you must first uninstall RequisiteWeb as described in the following section, and then proceed with the install as described 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

After you install RequisiteWeb 2003.06.X, 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 2003.06.X

To remove RequisiteWeb 2003.06.X:

  1. Use the Add/Remove Programs function in the Windows Control Panel to select and remove the Rational product you installed.
  2. Using dcomcnfg, remove the Local Administrators Group from "Default launch permissions" and "Default access permissions".
  3. If permanently uninstalling RequisiteWeb, remove the ReqWebUser.
  4. RequisitePro project data, backup files, and log files may still exist on the server. The log files will be located at C:\Program Files\Rational\common\rwp\logs\.

Removing RequisiteWeb 2002.05.X

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

Delete the ReqWeb and Jakarta Virtual Directories

  1. Start the Internet Services Manager by doing one of the following:
  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 opens. 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 to restart the IIS admin service. Refer to the column that corresponds to your operating system.

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
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.X

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 whether the C:\Program Files\Rational directory is still present on the server. If it is, 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 opens.
  2. Do one of the following:
  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 2001A from a Windows NT, Windows 2000 Server, or Windows Server 2003 system, you must have Windows administrator privileges on that machine. Use the following instructions to:

Stop and Remove the RqTomcat Service

Step Windows NT 4.0 Windows 2000 Server/Windows Server 2003
1 Click Start > Settings > Control Panel > Services. Click Start > Settings > Control Panel > Administrative Tools > Services.
2 Locate and select the RqTomcat service. Locate the RqTomcat service and double-click the icon to open 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. Start the Internet Services Manager by doing one of the following:
  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 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

After using Add/Remove Programs in the Windows Control Panel to remove RequisitePro and the uninstall process is complete (including restarting the server), 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:
  3. Locate the TOMCAT_HOME and JAVA_HOME system variables and delete them from your system.

Note: You must also reset your DCOM configuration settings for Word Document and Word Basic (if present), to their default values.

To complete the upgrade process, go 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.

Installation Issues

See the section Installing RequisiteWeb on the Server for information on installation issues.

Working with Documents

When taking a document offline, do not use your browser's back button. (RATLC00017928)

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 an 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.

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, see the 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 box 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)

When downloading documents for viewing or offline authoring using some browser versions, the File Download dialog box may display an incorrect file name. This display does not affect the actual file. (RATLC00017588)

Other Document Viewing Conditions

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

Creating Documents

When creating a document, the user selects a document type that references a RequisitePro outline; the outline determines the formatting and structure of the new document. If the outline is removed or renamed, a blank document is created in RequisiteWeb. (RATLC00018356)

You must specify a Universal Naming Convention (UNC) path in the Directory field on the Create Document page when creating a document in RequisiteWeb; for example, \\server_name\full_path\my_document. When specifying the local drive in the document directory, it is local to the webserver. (RATLC00018322)

Document Authoring

RequisiteWeb users cannot create or update a requirement hierarchy (parent and child relationships) in requirements that are located in documents.

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

When you use the manually hyphenate option in Microsoft Word, requirements are not displayed properly in the Attribute Matrix. (18168)

Requirement attributes that use the URL link type to link to a file with UNC path are functional in the Internet Explorer browser, but fail in Netscape. ( RATLC00719661)

Filtering Views in RequisiteWeb

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)

Expanding Packages

When viewing an Oracle-based project in RequisiteWeb, if you attempt to open a package that contains more than 1,000 elements of a particular type (documents, requirements, or views), an error occurs. To fix this condition, reorganize the package in RequisitePro to avoid grouping more than 1,000 elements of a type in one package. (RATLC00016736)

User Preferences and Resolution Settings

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

Some RequisiteWeb menus can truncate at an 800 x 600 display resolution. Changing your display settings to a higher resolution resolves this issue. (RATLC00016987)

Running RequisiteWeb on International Operating Systems

Do not install RequisiteWeb into a directory with double-byte characters. (RATLC00058552)

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 and valid URL characters.

Word-Linked Files

Requirements in Word documents must link to external files using the UNC for the link references in order for you to view the linked files in RequisiteWeb.

If RequisiteWeb detects a requirement 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)

In Netscape when trying to download an offline document to the same location as the original document, you will not receive an error saying that you cannot overwrite a read-only file, even though the original document is set to read-only when you take the document offline. As a result, the document will not be downloaded. (18547)

Hidden text contained within requirement text is not displayed when viewing requirement properties in Netscape 7.0. (RATLC00056727)

Taking a document with a double-byte character name offline using Netscape 4.51 corrupts the file name and document type extension. (RATLC00057743)

In Netscape 7.1, if you disable cookies from within a RequisiteWeb project using the tools option "Cookie Management->Block Cookies from this website," you may not be able to log on to the project in subsequent sessions. (RATLC00725153)

In Netscape 7.0, when taking a document offline, the Open and Save As functions fail. The Save As function appends a .jsp extension to the document, making it unreadable. To workaround this issue, save the document and rename it to remove the .jsp extension. (RATLC00723453)

Contacting IBM Rational Software Support

The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support homepage can be found at www.ibm.com/software/support.

Voice Support is available to all current contract holders via a telephone number in your country (where available). For specific country phone numbers, please refer to the IBM Software Support Handbook, Appendix B: Contact Information, found at www.ibm.com/software/support.