![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Installing DOORS 7.1 to a Production/Failover Environment Topic Summary: Production/Failover Environment for DOORS Created On: 2-Feb-2005 14:26 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks Louie but not exactly what I'm after. I'm referring specifically to the DOORS SERVER install - nothing to do with client software. In summary all I'm really looking for is a list of all the files of a DOORS SERVER installation that contain entries or values specific to the host/server on which ot is installed. e.g. the license.dat file lists the hardware id and hostname of the server. Which other files record these values? | |
![]() |
|
Any help appreciated.
We currently have Synergy Change/CM installed on a Solaris 8 server (Oracle DB) with the application and data files residing on SAN storage. The only files stored locally are the license files (host specific) and a few config files which specifically name the host or IP address. We have a failover server whose SAN is constantly sync'd with production and again the only files stored locally on this server are the license or config specific files to allow us to failover. We now need to address the same issues for a DOORS 7.1 installation. In addition to the license file(s) which other host specific files need to be stored locally? Are there any other issues - native to DOORS - which should also be taken into account? I have submitted a support call for this but am posting here just in case there was anyone out there who had already performed something similar. Thanks Ciaran |
|
![]() |
|
![]() |
|
I'm sure I don't quite understand, but maybe then following helps.
When installing a DOORS client you have two choices [1] Typical install puts the client files (doors.exe etc) on your client machine. The DOORS client makes requests to the DOORS data service on the server. [2] Workstation install points your client machine to another machine, lets call it the DOORS workstation, where the DOORS client files (doors.exe etc.) resides. When you start DOORS it goes to the workstation to download doors.exe and off you go. You need to install the DOORS client on the Workstation client first. Notice that this Workstation install is slower than the Typical install since you have to download the DOORS client each time you run DOORS. The only advantages that come to mind of this [2] Workstation install over the [1] Typical install are [a] it saves disk space on your client; whoopie, and you can upgrade or modify the client install rather easily, rather than patching everyone's computer. I don't know how many files are associated with a Workstation install, but its not very many. - Louie |
|
![]() |
|
![]() |
|
Thanks Louie but not exactly what I'm after.
I'm referring specifically to the DOORS SERVER install - nothing to do with client software. In summary all I'm really looking for is a list of all the files of a DOORS SERVER installation that contain entries or values specific to the host/server on which ot is installed. e.g. the license.dat file lists the hardware id and hostname of the server. Which other files record these values? |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.