![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Configuration files -- what are they? Topic Summary: Created On: 24-Oct-2003 17:52 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Good luck with configuration files. The Configuration file section demonstrates rather nicely that the DXL manual is truely a "Reference Manual" and not a "Learning Manual". The configuration files are stored subdirectories under the <data dir>/conf/ folder; presumably on the server. Note that the "/conf" folder is sibling of "/hierarchy". But the location is not of interest to the DXL writer unless he wants to clear out the directory of old configuration files. Subfolder "/u10000001.dir" seems to be the "confSystem" area, but who cares. There is no format for configuration files: manage their contents yourself. The writing DXL must coordinate with the Reading DXL. I use just text formatting with CRs because I'm a little dense on formatting issues and its easier to debug; even if it uses more bytes. Many of my configuration files have nothing in them: its the existence of the file that matters. I comment on the "ConfType" constants: confUser Each doors user gets its own confUser area (see "doorsname()") confSysUser Each network user gets its own confSysUser area (see "username()") confSystem Everyone shares the same area. confTemp Everyone shares the same area, but this one is labeled "temp". confProjUser Each doors user gets is own area, but this one is different than "confUser" above. Examples: Network user "Landale" logs in as DOORS user "The Master" and creates 3 configuration files all named "Test"; one each in "confUser", "confSysUser", and "confSystem". Then "Landale" logs in as "The Slave" and tests the existence of these conf files. The one in "confUser" will NOT exist but the other two will exist. Other users will only see the one in "confSystem". You can artificially create configuration files unique for each PROJECT by appending the project name onto some base file name, and storing them in the confSystem area. Almost all of my configuration files are of this type. - Louie | |
![]() |
|
Hello,
I have run across some scripts that make use of configuration files. Although I found the section (4) in the DXL Reference Manual that describes how to access config files, there is no indication of what they are or if they have a defined format. So I have the following questions: 1. Are the contents of these files free-format, left to the discretion of the DXL writer? I'm thinking not because the manual does indicate that the DOORS Tip Wizard uses one of these files. If not, where is the format defined? 2. Has anyone else out there constructed any config files, and if so, what do you use them for? 3. Where would I expect the user, system, shared, temp, and project configuration areas to reside on a typical installation? Your help is much appreciated. Thanks, Greg |
|
![]() |
|
![]() |
|
Good luck with configuration files. The Configuration file section demonstrates rather nicely that the DXL manual is truely a "Reference Manual" and not a "Learning Manual".
The configuration files are stored subdirectories under the <data dir>/conf/ folder; presumably on the server. Note that the "/conf" folder is sibling of "/hierarchy". But the location is not of interest to the DXL writer unless he wants to clear out the directory of old configuration files. Subfolder "/u10000001.dir" seems to be the "confSystem" area, but who cares. There is no format for configuration files: manage their contents yourself. The writing DXL must coordinate with the Reading DXL. I use just text formatting with CRs because I'm a little dense on formatting issues and its easier to debug; even if it uses more bytes. Many of my configuration files have nothing in them: its the existence of the file that matters. I comment on the "ConfType" constants: confUser Each doors user gets its own confUser area (see "doorsname()") confSysUser Each network user gets its own confSysUser area (see "username()") confSystem Everyone shares the same area. confTemp Everyone shares the same area, but this one is labeled "temp". confProjUser Each doors user gets is own area, but this one is different than "confUser" above. Examples: Network user "Landale" logs in as DOORS user "The Master" and creates 3 configuration files all named "Test"; one each in "confUser", "confSysUser", and "confSystem". Then "Landale" logs in as "The Slave" and tests the existence of these conf files. The one in "confUser" will NOT exist but the other two will exist. Other users will only see the one in "confSystem". You can artificially create configuration files unique for each PROJECT by appending the project name onto some base file name, and storing them in the confSystem area. Almost all of my configuration files are of this type. - Louie |
|
![]() |
|
![]() |
|
Thanks, Louie. I appreciate your insight, and will try to decipher how they're being used.
- Greg |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Configuration files -- what are they?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.