![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Changing Licenses Topic Summary: Created On: 22-Mar-2006 16:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We've got some clients who used totally different DOORS databases. Using a new DOORS Icon featuring the "-d" switch, we can direct them to whichever DB they need to use OK.
I notice that when we do this we use the same licensing. However, they also need to switch licensing; use license A when using DB A, and license B when using DB B. In v6 I had some luck updating the registry [HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager] value ; "DOORS_LICENSE_FILE"="7192@MyDOORSServer". Users switching DB would first initiate the corresponding simple Registry update file. This no longer works for v7.1. I know about the License Manager and modifying Environment Variable "LM_LICENSE_FILE"; but modifying that doesn't seem realistic; although I suppose I could try a DOS Batch file using the "set" command. Could anyone please explain the internal process of choosing a License with a view to allowing me to change it on demand? - Louie |
|
![]() |
|
![]() |
|
Louie,
I had the same problem with DOORS 7.1, and solved it by ensuring our users start DOORS via a .vbs script, with the following lines included: -------------- On Error Resume Next WshShell.RegDelete("HKLM\SOFTWARE\FLEXlm License Manager\TELELOGIC_LICENSE_FILE") Set ProcessEnvironment = WshShell.Environment("PROCESS") ProcessEnvironment("SECURITY") = "SOFT" ProcessEnvironment("TELELOGIC_LICENSE_FILE") = "19353@xxxxxxxx.yyyy.com" ---------------- Deleting the TELELOGIC_LICENSE_FILE registry entry was essential before setting it, as it accumulates by default, and uses the first entry in the accumulated ";" delimited string of license servers. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Thought I had this working in v6 where I simply updated the DOORS_LICENSE_FILE variable there in the FlexLM spot. Updating the TELELOGIC_LICENSE_FILE worked, but as soon as you started DOORS this value was reset to some value that, oddly, doesn't appear ANYWHERE else in the Registry. I'm currently searching my ENTIRE hard drive looking for any file that contains this string.
Doesn't your VBS script need to start DOORS after this? - Louie |
|
![]() |
Telelogic DOORS
» Administration
»
Changing Licenses
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.