MDG Doors LINK --> KO ?

[Monsieur]

here is my menu.


here is what the help says


Do i have to configure something somewhere? because the help don't talk about it.

Some one has a clue on how to make this link word? cause i really don't get it. :-?

[qwerty]

Long time ago I used it. You need some installer for the MDG and a license key IIRC.

q.

[Aaron B]

These other menu option will only appear after you have successfully linked a package with a DOORS module.

- Open a project
- Select a package in the Project Browser window
- Select Extensions | Connect External Project | DOORS

follow the instructions link the selected package with an open DOORS module.  Once the package is linked, you should see the additional options under the DOORS menu.

[SysEngineer]

Dear sirs,

I also have a problem with MDG link for DOORS in Enterprise architect  and I urgently need your help.

I'am using the version 11 of Enterprise Architect and IBM Rational Doors as Requirement Management Tool and I have a licence for MDG Link for doors (version 2.1.0)


Now I would import requirements from doors to Enterprise Architect model, the source Module in DOORS is open but the import into EA doesn't work like the description in the User Guide.

Using right mouse click in the target package in my EA model, I could not find the context menu option add-in -> connect external project, With Extensions it is also not available.

What am I doing wrong? how can I use the MDG Link import option and how does it work?
P.S. A colleague of mine used with the EA version 10 and with the same MDG link for Doors licence and it worked.

Thank you for your help!

[Gary]

Make sure you have a module open with a view selected before you select Connect External Project -> DOORS.
Sometimes restarting EA helps.
I have found with colleagues that it either works or does not with no reason as to either. All have the MDG installed.

Gary

[Monsieur]

Dear sirs,

I also have a problem with MDG link for DOORS in Enterprise architect  and I urgently need your help.

I'am using the version 11 of Enterprise Architect and IBM Rational Doors as Requirement Management Tool and I have a licence for MDG Link for doors (version 2.1.0)


Now I would import requirements from doors to Enterprise Architect model, the source Module in DOORS is open but the import into EA doesn't work like the description in the User Guide.

Using right mouse click in the target package in my EA model, I could not find the context menu option add-in -> connect external project, With Extensions it is also not available.

What am I doing wrong? how can I use the MDG Link import option and how does it work?
P.S. A colleague of mine used with the EA version 10 and with the same MDG link for Doors licence and it worked.

Thank you for your help!

Can you state wich version of Doors are you using? and if it 32 or 64bits?

[Monsieur]

These other menu option will only appear after you have successfully linked a package with a DOORS module.

- Open a project
- Select a package in the Project Browser window
- Select Extensions | Connect External Project | DOORS

follow the instructions link the selected package with an open DOORS module.  Once the package is linked, you should see the additional options under the DOORS menu.

So that's mean do you need the heavy Doors client installed in your machine.
Does it work on a citrix server or a windows 2003 server for exemple?

[Aaron B]

Correct.  You need to have the full DOORS client installed locally.  AFAIK it will not work via virtualization such as Citrix.  The add-in needs to access the DOORS ActiveX/COM API in order to function, which doesn't seem to work via Citrix from what I've seen.

[Monsieur]

These other menu option will only appear after you have successfully linked a package with a DOORS module.

- Open a project
- Select a package in the Project Browser window
- Select Extensions | Connect External Project | DOORS

follow the instructions link the selected package with an open DOORS module.  Once the package is linked, you should see the additional options under the DOORS menu.

Is there some kind of limitation behind this process? EA crash each time i try on a module composed with a relatively big number of requirements. :-?
Is there a way that headings generate package? (most of DOORS user work that way...)

[Aaron B]

Not aware of any issues resulting in a crash.  Please submit a bug report and maybe include an export of your DOORS module if possible.

No option available at this time to have headings imported as Packages.

[Monsieur]

Not aware of any issues resulting in a crash.  Please submit a bug report and maybe include an export of your DOORS module if possible.

No option available at this time to have headings imported as Packages.

Sorry, "no can do".
I have a lead on what can be the problem:
How does EA react to custom fields, calculated field or calculated columns (well, specifically on any piece of DXL)  :-?

[Monsieur]

Not aware of any issues resulting in a crash.  Please submit a bug report and maybe include an export of your DOORS module if possible.

No option available at this time to have headings imported as Packages.

Sorry, "no can do".
I have a lead on what can be the problem:
How does EA react to custom fields, calculated field or calculated columns (well, specifically on any piece of DXL)  :-?

Update : The Link now works (on DOORS 9.6.0.1 32bit version)!
You just have to be, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, VERY patient + When you import you always loose control of EA (This plugin is greedy in ressources)  and sometimes, also of DOORS (didn't find out when and why but it happens, seems random)
I'm happy