Which kind of artifacts can be linked in Doors 9.5.1.2?

Hi, from what I understand in Doors 9.5.1.2 I can add three type of links:

  1.  Standard/Internal links - which can point to internal resources(other objects)
  2. External links - links to external resources, files on the file system, URLs
  3. Collaboration links - links to other IBM systems like IBM Ratinal Composer ,etc.

 

But how to attach binary files(zip-s, exe-s, bat files) to an requirement? Does it has to be add on the local drive(where the Doors server runs) or can be on external file store? I can't find way how to do that?


Dinio - Wed Dec 02 11:13:20 EST 2015

Re: Which kind of artifacts can be linked in Doors 9.5.1.2?
mstanke - Thu Dec 03 04:01:08 EST 2015

Hello Dinio,

 

To link to any type of files you could use:
- External links which point to the exact network location. The exact network path has to be accessible for the users.
- You could also insert the required files as linked OLE'S or even embed these files as OLE to DOORS. Be careful to embed large files into DOORS as this has an affect on the size of the module.

 

Regards

Marcus

Re: Which kind of artifacts can be linked in Doors 9.5.1.2?
Dinio - Thu Dec 03 04:09:18 EST 2015

mstanke - Thu Dec 03 04:01:08 EST 2015

Hello Dinio,

 

To link to any type of files you could use:
- External links which point to the exact network location. The exact network path has to be accessible for the users.
- You could also insert the required files as linked OLE'S or even embed these files as OLE to DOORS. Be careful to embed large files into DOORS as this has an affect on the size of the module.

 

Regards

Marcus

The exact network path has to be accessible for the users.

I still do no understand If I created an object and add Ole as linke object(not embedded) and upload the artifact this file is not uploaded. I try with 1 GB file and the operation tooks bellow 30 seconds(when I embed 10MB file it takes over 1 minute) so I am sure that the file is add as link. But what happens when person on the other machine in different geolocation try to open this file? How he will be possible to do that, because the file is not physically on the Doors DB? I still can not understand.

 

Re: Which kind of artifacts can be linked in Doors 9.5.1.2?
mstanke - Thu Dec 03 04:48:26 EST 2015

Dinio - Thu Dec 03 04:09:18 EST 2015

The exact network path has to be accessible for the users.

I still do no understand If I created an object and add Ole as linke object(not embedded) and upload the artifact this file is not uploaded. I try with 1 GB file and the operation tooks bellow 30 seconds(when I embed 10MB file it takes over 1 minute) so I am sure that the file is add as link. But what happens when person on the other machine in different geolocation try to open this file? How he will be possible to do that, because the file is not physically on the Doors DB? I still can not understand.

 

Hello Dinio,

I don't understand this sentence "I still do no understand If I created an object and add Ole as linke object(not embedded) and upload the artifact this file is not uploaded. "
What do you upload in this case ? As if you create the linked OLE the file has to be already available on the desired location.

Remember if you add an embedded OLE the file will be made available in your DOORS DB. If you add a linked OLE it is just a link to a specified location.

 

I'll explain this on a few examples.
Let's say the location of your file is on C:\
- external link or linked OLE to c:\file.name  -> this file will not be available to other users
- in this case it is best to use embedded OLE for this file (but please not a 1Gb file)

Let's say the location of your file is on \\networkshare:
- external link or linked OLE to \\networkshare\\file.name  -> if the user can access the location "\\networkshare\\file.name" then he is able to open the file

 

Let's say the location of your file is on mapped network drive, e.g. Z:\ file.name
- external link or linked OLE to Z:\ file.name -> if other users have added the mapped network drive with the same location also to Z:\ then they can open it
- if they have added the mapped network drive with the same location but using a different drive letter e.g. X:\ then they cannot not access the file

 

Regards

Marcus

Re: Which kind of artifacts can be linked in Doors 9.5.1.2?
Dinio - Thu Dec 03 06:22:49 EST 2015

mstanke - Thu Dec 03 04:48:26 EST 2015

Hello Dinio,

I don't understand this sentence "I still do no understand If I created an object and add Ole as linke object(not embedded) and upload the artifact this file is not uploaded. "
What do you upload in this case ? As if you create the linked OLE the file has to be already available on the desired location.

Remember if you add an embedded OLE the file will be made available in your DOORS DB. If you add a linked OLE it is just a link to a specified location.

 

I'll explain this on a few examples.
Let's say the location of your file is on C:\
- external link or linked OLE to c:\file.name  -> this file will not be available to other users
- in this case it is best to use embedded OLE for this file (but please not a 1Gb file)

Let's say the location of your file is on \\networkshare:
- external link or linked OLE to \\networkshare\\file.name  -> if the user can access the location "\\networkshare\\file.name" then he is able to open the file

 

Let's say the location of your file is on mapped network drive, e.g. Z:\ file.name
- external link or linked OLE to Z:\ file.name -> if other users have added the mapped network drive with the same location also to Z:\ then they can open it
- if they have added the mapped network drive with the same location but using a different drive letter e.g. X:\ then they cannot not access the file

 

Regards

Marcus

Thanks ,for the answer mstanke . I understand what I needed.