Installing the DOORS client that is to administer the DOORS system
The IBM® Engineering Requirements
Management DOORS®
(DOORS)
client runs on Windows systems only. To install DOORS, a
DOORS
administrator first installs the client that is to be used to administer the DOORS
system. Then, the administrator installs the database server and sets up the administrator and
database manager accounts on the client. At that point, team members who are not administrators can
install the client on their computers.
Before you begin
- Make sure that you meet the system, licensing, and other requirements. To view a checklist of installation prerequisites, see Installation preparation for DOORS.
- If you are installing on Windows 2012, Windows 2008, or Windows 7 systems, you must log in to the administrator account or run as an administrator. To run as an administrator, right-click the installer file and then click Run as Administrator.
- If you are installing the client and database server on the same computer and are using the client to administer DOORS, install the client first. Then, install the database server.
- You must know the port number and server name that you intend to use for the database server. You need this information when you install the client. The port number must be higher than 1023; the default is 36677.
About this task
The DOORS client for Windows systems is now large address aware, which means that it has more virtual address space. The client can address up to 4 GB of memory on 64-bit versions of Windows systems. You do not need to modify the operating system to benefit from the large address aware capability
Procedure
What to do next
After you install the client and log in to the DOORS database server for the first time, the client disappears while the user index is created and stored on the server. The client connection is visible on the server and in the Windows Task Manager, but not on the screen. After the user index is complete, the client reappears and the login operation is completed. The delay does not occur in subsequent login operations.