Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Share/distribute scripts
Topic Summary: I need to know how to share/distribute dxl files between users
Created On: 27-Sep-2004 20:02
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Ross Morgan, on Thursday, September 30, 2004 3:28 PM

Answer:
unfortunately the DOORS DB server doesn't serve DXL.

the best way to update DXL is to include a version check in the code and download the latest from a common "conf" directory on the server.

confDownloadFile("/dxldir/some.dxl,sFilename,confSystem)

one way to get the code onto the client machine in the first place is to attach a trigger to a module which downloads the DXL code from the server and installs it.

Trigger t = trigger("installsomeDXL",module,post,open,10,sTrigDXL)

 27-Sep-2004 20:02
User is offline View Users Profile Print this message


Adam Terrenzio

Posts: 14
Joined: 24-Nov-2003

I have some custom DXL that I am using from a user-defined menu. I have shared this with other doors users, but via email and they had to install it on their own clients.

I made a change to my DXL, but obviously others don't see this change until I email it out and have them overwrite the files again. So every time I make a tweek to the code, another email blast goes out. There has got to be another way!

Can you use the server to distribute DXL to the users folder? Can you put DXL scripts on the server? Has anyone got a better solution than spam?

Thanks,
Adam.

Adam Terrenzio
Software Developer, Research and Development, MKS Inc., www.mks.com
Waterloo, ON, Canada; Tel: (519)883-3216; Fax: (519)884-8861
Report this to a Moderator Report this to a Moderator
 28-Sep-2004 11:48
User is offline View Users Profile Print this message


Ross Morgan

Posts: 74
Joined: 15-Apr-2004

Answer Answer
unfortunately the DOORS DB server doesn't serve DXL.

the best way to update DXL is to include a version check in the code and download the latest from a common "conf" directory on the server.

confDownloadFile("/dxldir/some.dxl,sFilename,confSystem)

one way to get the code onto the client machine in the first place is to attach a trigger to a module which downloads the DXL code from the server and installs it.

Trigger t = trigger("installsomeDXL",module,post,open,10,sTrigDXL)

Report this to a Moderator Report this to a Moderator
 28-Sep-2004 15:20
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Morgan has an interesting concept for auto-downloading the DXL to the clients; featuring a triggered "pull". You'd need a clever Trigger to know what's new, what's changed, and what's deleted. Pushing via terminal services, I suppose, would work also but that looks tough to manage.

We've been using the deploy-on-a-server approach. Build a suitable file hierarchy and adjust the user's "addins" and "projectaddins" variables to point to them. Thus, DOORS Explorer (projectaddins) and DOORS modules (addins and projectaddins) menus get build when you open them with the current versions of the menus and scripts at that time. Admin updates is just changing the files on the server. BTW, the "sever" is some common network place the users can access, and may or may not be the same as the "DOORS Server".

See the DXL Manual "The DXL Library and Addins menus" for enough information to get you confused. Its pretty complicated to get set up. But once set up all you need is a *.reg registry update file posted with your DXL. Advertise this to folks via SPAM email, that if they want these addins they should double-click on the registry update file.

Goodman seemed to have a solution where you one-time modify the client's install such that the "formal.dxl" file includes specific "createMenu" and "createItem" commands. This allows you to decide real-time which modules have access to which addins (you may have 'requirement' addins for requirement modules, and 'test' addins for test modules). Administering this approach looks like a nightmare.

- Louie

Report this to a Moderator Report this to a Moderator
 30-Sep-2004 15:31
User is offline View Users Profile Print this message


Adam Terrenzio

Posts: 14
Joined: 24-Nov-2003

Both interesting answers. I guess anoter way would be to seperate the DXL into many files. Then use some version control tool for the location of the scripts and put a "resync" command (provided the SCM tool has a command line interface or something) in at the start of the script which would fetch fresh versions of the other files before executing functions. As long as changes were committed to the repository, everyone would receive the updates.

Thanks for your suggestions.

Adam.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.