![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL Scripts location Topic Summary: DXL Scripts location Created On: 13-Apr-2006 19:22 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Does anyone know if it's possible to store the DXL scripts on the server so everyone can access them when using DOORS.
Currently we have to run a registery patch for all DOORS users which points to the addins directory on a network drive. We have different locations using DOORS which have different network drives. |
|
![]() |
|
![]() |
|
In the doors help file -- search for command line swtiches
|
|
![]() |
|
![]() |
|
Daxesh, We're in a similar situation here. I don't know of a way to have the scripts stored on the server -- aside from literally sharing a folder on the server's drive and having people map it. Doesn't seem wise to me to do it that way, and that's not much different from a network drive. |
|
![]() |
|
![]() |
|
Hi Daxesh,
I think the problem is that your using a network drive reference to point to the location. Rather than using a network drive reference it's better to use a share name and path reference as this doesn't use a drive label which as you have pointed out can vary from user to user. If you've not seen one of these before, a share name and path reference has the syntax: \\<Host Name>\<share name>\<path to target folder relative to share name>. You need to get one of your IT people to configure a share on the parent folder to where your DOORS addins folder is located on the central server. So your share may look something like this: \\regulus\doors\addins. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
thanks for the reply,
our IS dept won't lets us have the hostname/sharename because "Shares are frowned upon due to virus activities and connectivity concerns". The scripts needs to be accessed by Germany, Poland, India and USA. The scripts are located in USA. I tried setting up a "SureSync" to copy from one location to another but this fails as the scripts are referencing files in the local directory (e.g. "#include <L:\Doors_DXL_Scripts\addins\CustomScritps\directoryName.inc>"). As of now, I copy the scripts onto the different drive/location then modify the "L:\..." to say "D:\..." and also change the registery entry for addins path. |
|
![]() |
|
![]() |
|
Remember that it is not necessary to quote absolute paths in your #include statements, for example if the addins environment on the client machine includes the directory 'D:\DOORS_DXL_Scripts\addins', then the statement '#include <CustomScripts\directoryName.inc>' will look in 'D:\DOORS_DXL_Scripts\addins\CustomScripts' for the file called 'directoryName.inc'. You may be able to use this to aviod having to modify the scripts to suit the local drive mappings.
|
|
![]() |
|
![]() |
|
Inculde file is a bad examaple. I have other files like ".dot" file or ".bmp" file which do not open when running the script from the Menu. I have figured out a way to get the files path from the Registry by using the getRegistry function. This will work for all users.
|
|
![]() |
|
![]() |
|
You can put them on any server to which the user can access through Windows Explorer. If the user can see your "\\DoorsServer" then put them there, perhaps in "\\DoorsServer\DXL-Addins". Our DOORS server is regrettably isolated from all such contact except via Ports, so we cannot deploy the DXL on that server. Realistically, if you have a netword-divers DOORS work force you WANT to make multiple-deploys, where each such group goes to the DXL that's close ..err.. I mean fast on the network. DXL deployment would mean knowing about and updating all such locations.
- Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL Scripts location
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.