Installing and Configuring Rational RequisiteWeb Version 2003.06.00

Installing and Configuring Rational RequisiteWeb Version 2003.06.00

For trademark and copyright information, see Legal Notices.

Introduction

Rational RequisiteWeb lets clients 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 access projects that use Microsoft Access, Microsoft SQL Server, or Oracle databases. RequisiteWeb must be installed on a Windows server.

Click here for information on new features in this release of RequisiteWeb.

This document contains the following sections:

RequisiteWeb System Requirements
Configuring the RequisiteWeb Server
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
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 SP2, SP3

Microsoft Windows 2000 Advanced Server SP2, SP3

Microsoft Windows .NET RC2

Note: The production release of Microsoft Windows 2003 was not available for final testing at the time this document was finalized. To obtain the latest information on Windows 2003 support, go to http://www.ibm.com/software/rational/.

NT Server 4.0, Service Pack 6A with security rollup package

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, we recommend 256 MB or more.

Disk space RequisiteWeb (includes system DLLs) - 40 MB

Microsoft Word
One of the following:

Microsoft Word 2000 SP2, SP3

Microsoft Word 2002 SP1, SP2

Note: Microsoft Word licenses are required for all concurrent RequisiteWeb users.

Oracle Database Client (to use projects located in Oracle databases)
Oracle 8.1.7, 9i R2

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 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 documents. To access RequisiteWeb from client machines, you must install one of the following Web browsers on the client system.

Microsoft Internet Explorer 5.5 SP1, SP2
Netscape Navigator 4.70 - 4.78 or 7.0

Note: For proper RequisiteWeb operation, you must set 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: Installing RequisiteWeb on a system that has J-Integra already installed may cause conflicts.

Note: If you are upgrading RequisiteWeb version 2002.05.0X or 2001A, 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 Oracle Client
Creating the RequisiteWeb User
Adding the ReqWebUser to the Local Administrator Group
Assigning DCOM Permissions to the Local Administrators Group
Installing RequisiteWeb on the Server
Editing the RequisiteWeb Configuration File
Enabling SSL (Secure Socket Layer)
Granting ReqWebUser Access to Network Projects

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: 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 this installation guide, 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/.NET RC2

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 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/.NET RC2

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. The Select Users or Groups dialog box opens. At the Look in box, select the domain where you created the ReqWebUser.

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 Select Users or Groups 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.
To Assign Access Permissions to the Local Administrators Group:

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.
Select the Default Security tab. Under Default Access Permissions, click the Edit Default button.
In the Registry Value Permissions dialog box, click Add.
At the Add Users and Groups dialog box, select your local machine from the List Names From list.
Select the Administrators group in the Names list and click Add.
At the Type of Access box, 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:

Select the Default Security tab. Under Default Launch Permissions, click the Edit Default button.
In the Registry Value Permissions dialog box, click Add.
At the Add Users and Groups dialog box, select your local machine from the List Names From drop-down list box.
Select the Administrators group in the Names list and click Add.
At the Type of Access field, select Allow Launch. Click OK twice to return to the Distributed COM Configuration Properties dialog box.
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, log on to the RequisiteWeb server as a local administrator. Use the Rational Solutions for Windows CD disc 1 to install RequisiteWeb. The Rational Software Setup Wizard guides you through the software installation. On each screen, click the Next button to proceed to the next screen. At the Product Selection screen, select Rational RequisitePro from the Rational Product list.

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.

At the Custom screen, expand the Web Server Components and select RequisiteWeb.

Installation Issue: Rational Installer Incompatible with Windows "Change Journal" Feature

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the Windows "Change Journal" (log) enabled on it. Rational is actively working with Microsoft to better understand and identify a fix for the problem.

Before installing any Rational Version 2003 product on a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions for the text "Change Journal". (RATLC00688306)
For more information about installing the RequisiteWeb server components, see the Rational Desktop Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD.
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

Change and redirect the default RWP HTTP port

Disable IIS

The following table explains how you can disable IIS. After you disable it, any programs using it will no longer work.

Step Windows NT 4.0 Windows 2000 Server/.NET RC2

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:

Change the default RWP HTTP port (80) in your rwp.conf file. Follow the instructions “To Change the Default RWP HTTP Port” in the Rational Server Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD.

Create a virtual directory for RequisiteWeb on your RequisiteWeb server:

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.

Right-click the Default Web Site and select New Virtual Directory.
In the Virtual Directory Creation Wizard, click Next and type ReqWeb as the alias.
Click Next and browse to and select
C:\Program Files\Rational\common\RWP\webapps2\ReqWeb and click Next.
Click Next and Finish to complete the wizard.

In the properties of your newly created Virtual Directory, select A redirection to a URL and redirect to: http://<server name>:<new port>/reqweb

Close the Internet Services Manager and restart the Rational Web Platform. Follow the instructions in “Starting and Stopping the Rational Web Platform” in the Rational Server Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD.

Editing the RequisiteWeb Configuration File (optional)

Edit the RequisiteWeb configuration file to:

Customize your document location.

Customize your Web access to document locations.

Relocate your catalog.txt.

Enable SSL.

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

Considerations:

Rational Web Platform must be restarted for configuration changes to take effect. Follow the instructions for “Starting and Stopping the Rational Web Platform” in the Rational Server Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD.

We recommend that you back up the config.txt file before making changes.

We recommend that you contact RequisiteWeb customer support before you change any config.txt settings not listed in this table.

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

Setting Description Default

RPXDocPath The path to the directory where RequisiteWeb temporarily stores Word documents (also known as the “GenDoc” directory). From the GenDoc directory, client Web browsers download documents (Word format) or read them for display (HTML format). For example:

RPXDocPath=C:\Program Files\Rational\common\rwp\webapps2\ReqWeb\GenDoc

Note: If you change the RPXDocPath directory, you must make a corresponding change to the RPXHTTP variable below. The converse also applies. <blank>

RPXHTTP The URL that client Web browsers use to access the RPXDocPath directory. If you enter a relative URL, it will be relative to “http://<servername>/ReqWeb”. For example:

RPXHTTP=GenDoc/
-or-
RPXHTTP=http://<anotherlocation>/GenDoc/

Note: This setting is case-sensitive. GenDoc/

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>

SSL Set SSL to true if SSL is enabled. This setting affects whether hyperlinks in HTML-format documents use HTTP or HTTPS. For example:

SSL=true false

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:

Stop the Rational Web Platform. Follow the instructions for “Starting and Stopping the Rational Web Platform” in the Rational Server Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD.

Set SSL to true in the RequisiteWeb configuration file (see above table).

Remove all files and directories in the GenDoc directory. By default, this is C:\Program Files\Rational\common\rwp\webapps2\ReqWeb\GenDoc

Follow the instructions for configuring the Rational Web Platform in the Rational Server Products Installation Guide to enable SSL.

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/.NET RC2

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.

Testing RequisiteWeb

To test your installation of RequisiteWeb:

Open a Web browser.
Set the URL address to "http://<server name>/reqweb" on your RequisiteWeb server and press enter.
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.
Type your RequisitePro user name and password and click Log in.
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. For instructions on modifying the catalog, see Editing the RequisitePro Projects Catalog.

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:

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.

Using a text editor, open the catalog.txt file.
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

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

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 an Oracle database, you must configure the Oracle client software on the server. See the section "Setting Up PCs for Oracle Access" in the Rational Desktop Products Installation Guide included on the Rational Solutions for Windows Online Documentation CD. 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

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:

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.

To complete the Rational E-mail Reader setup for SMTP protocol, you need the following information from your e-mail administrator:
- SMTP Server name
- POP3 Server name
- E-mail address; one for each RequisitePro project
- POP3 server login and password for the e-mail address

Be sure to specify a Log File Path on the Reader Information and Options tab in the Rational E-mail Reader.

When configuring email with the Rational ClearQuest Mail service, you must stop the service before configuring and restart the service when done.

For network-based projects, you must configure the properties of the Rational ClearQuest Mail service on the Log On tab. Select This account and enter your domain username and password. When browsing for an account name, see the "examples" link in the Select User dialog box.

The E-mail Setup option on the RequisitePro Tools menu does not configure e-mail for RequisiteWeb discussions. Use the Rational E-mail Reader to configure e-mail for RequisiteWeb discussions.

Upgrading RequisiteWeb 2002.05.X and 2001A

To upgrade from RequisiteWeb 2002.05.X or 2001A to RequisiteWeb 2003.06.00, 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.00, 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.00

Removing RequisiteWeb 2002.05.X

Removing RequisiteWeb 2001A

Removing RequisiteWeb 2003.06.00

Note: Your existing webapps2 directory, located in the default directory: C:\Program Files\Rational\common\RWP\, will be deleted when you uninstall RequisiteWeb. To preserve your configuration files or any other files in your webapps2 directory, you must relocate those files before uninstalling RequisiteWeb.

Use the Add/Remove Programs function in the Windows Control Panel to select and remove the Rational product you installed.

Using dcomcnfg, remove the Local Administrators Group from "Default launch permissions" and "Default access permissions".

If permanently uninstalling RequisiteWeb, remove the ReqWebUser.

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 or Windows 2000 Server/.NET RC2, 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
Uninstall the RequisiteWeb program files

Delete the ReqWeb and Jakarta Virtual Directories

Start 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/.NET RC2, click Start > Programs > Administrative Tools/Internet Services Manager.

Select the Default Web Site and click the Stop button on the toolbar.
Right-click the ReqWeb virtual directory and select Delete.
Right-click the Jakarta virtual directory and select Delete. Leave the Internet Services Manager open.

Remove the Jakarta ISAPI filter

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.
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/.NET RC2

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:
On the start menu, click Settings > Control Panel. In the Control Panel, double-click the System icon. The System Properties dialog box opens.
Do one of the following:

In Windows 2000 Server/.NET RC2, at the Advanced tab, click Environment Variables.
In Windows NT, click the Environment tab.
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 or Windows 2000 Server/.NET RC2, you must have Windows administrator privileges on that machine. Use the following instructions to:

Stop and remove the RqTomcat Service
Remove the ReqWeb and Jakarta virtual directories
Uninstall RequisiteWeb 2001A
Remove the TOMCAT_HOME and JAVA_HOME system variables

Stop and Remove the RqTomcat Service

Step Windows NT 4.0 Windows 2000 Server/.NET RC2

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:
Open an MS-DOS shell and navigate to the following directory:
C:\Program Files\Rational\jakarta-tomcat\bin
Type the following at the MS-DOS prompt:
jk_nt_service -R RqTomcat
Close the MS-DOS shell.
Remove the ReqWeb and Jakarta Virtual Directories

Start 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/.NET RC2, click Start > Programs > Administrative Tools > Internet Services Manager.

Under the Default Web Site, locate the ReqWeb and Jakarta virtual directories. Right-click each of the directories and select delete.
Right-click Default Web Site and select Properties.
At the ISAPI Filters tab, locate the jakarta filter. Right-click the jakarta filter and select delete.
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 whether the following directory is still present on the server:
C:\Program Files\Rational

If so, delete the directory and all subdirectories.

Remove the TOMCAT_HOME and JAVA_HOME System Variables

On the start menu, click Settings > Control Panel. In the Control Panel, double-click the System icon. The System Properties dialog box appears.
Do one of the following:

In Windows 2000 Server/.NET RC2, at the Advanced tab, click Environment Variables.
In Windows NT, click the Environment tab.

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:
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 has 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 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)
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)
Use a full path for documents located on the RequisiteWeb server. To access documents on another server, you must specify a UNC path to the shared folder containing documents (for example, \\server_name\full_path\my_document.doc). When specifying the local drive in the document name, it is local to the Web server, not the client. (RATLC00018322)

Document Authoring

Web Document Authoring users can not create or update hierarchy.

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)

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

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. (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)

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

Rational Customer 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!

Item	Requirement
Operating System	One of the following: Microsoft Windows 2000 Server SP2, SP3 Microsoft Windows 2000 Advanced Server SP2, SP3 Microsoft Windows .NET RC2 Note: The production release of Microsoft Windows 2003 was not available for final testing at the time this document was finalized. To obtain the latest information on Windows 2003 support, go to http://www.ibm.com/software/rational/. NT Server 4.0, Service Pack 6A with security rollup package
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, we recommend 256 MB or more.
Disk space	RequisiteWeb (includes system DLLs) - 40 MB
Microsoft Word	One of the following: Microsoft Word 2000 SP2, SP3 Microsoft Word 2002 SP1, SP2 Note: Microsoft Word licenses are required for all concurrent RequisiteWeb users.
Oracle Database Client (to use projects located in Oracle databases)	Oracle 8.1.7, 9i R2

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

Step	Windows NT 4.0	Windows 2000 Server/.NET RC2
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.	The Select Users or Groups dialog box opens. At the Look in box, select the domain where you created the ReqWebUser.
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 Select Users or Groups dialog box. Click OK to finish.
6	Close the User Manager application.	Close the Computer Management application.

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

Setting	Description	Default
RPXDocPath	The path to the directory where RequisiteWeb temporarily stores Word documents (also known as the “GenDoc” directory). From the GenDoc directory, client Web browsers download documents (Word format) or read them for display (HTML format). For example: RPXDocPath=C:\Program Files\Rational\common\rwp\webapps2\ReqWeb\GenDoc Note: If you change the RPXDocPath directory, you must make a corresponding change to the RPXHTTP variable below. The converse also applies.	<blank>
RPXHTTP	The URL that client Web browsers use to access the RPXDocPath directory. If you enter a relative URL, it will be relative to “http://<servername>/ReqWeb”. For example: RPXHTTP=GenDoc/ -or- RPXHTTP=http://<anotherlocation>/GenDoc/ Note: This setting is case-sensitive.	GenDoc/
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>
SSL	Set SSL to true if SSL is enabled. This setting affects whether hyperlinks in HTML-format documents use HTTP or HTTPS. For example: SSL=true	false

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

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

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