We have multiple DOORS databases on different servers and there is a need to link requirements between them. Other than using external links has anyone found a different method of achieving this (OSLC would have been nice)
Chris Palmer - Wed Nov 12 10:12:41 EST 2014 |
Re: Multiple DOORS Databases Hi In this case, OSLC cannot help because OSLC is only a different interface technique to the doors database. You can use an "OSLC-Client" instead of the standard doors client. But this client does not enable you to make better, longer larger or nicer or other links. You can only create links as before. Inside of the OSCL-Client a doors object for example can be adressed by an OSLC-Link. But this link only can help you inside the OSCL-World. Of cource, if you are using Rational Team Concert (https://jazz.net/products/rational-team-concert/) you are allways inside this world and here it migth be possible to include two ore more databases. Do you use team concert? If not, the only chance is to mirror some module from one database to the other. Best regards Wolfgang |
Re: Multiple DOORS Databases Wolfgang Uhr - Wed Nov 12 10:56:41 EST 2014 Hi In this case, OSLC cannot help because OSLC is only a different interface technique to the doors database. You can use an "OSLC-Client" instead of the standard doors client. But this client does not enable you to make better, longer larger or nicer or other links. You can only create links as before. Inside of the OSCL-Client a doors object for example can be adressed by an OSLC-Link. But this link only can help you inside the OSCL-World. Of cource, if you are using Rational Team Concert (https://jazz.net/products/rational-team-concert/) you are allways inside this world and here it migth be possible to include two ore more databases. Do you use team concert? If not, the only chance is to mirror some module from one database to the other. Best regards Wolfgang Hi Wolfgang, We do use both RTC and RQM with OSLC hence my bracketed comment, we are also looking at using something like Raphsody to link to the databases and do some form of comparison etc. there. We have also linked a DOORS database to external applications like Requirements Central again with OSLC so it seems strange that you can't link 2 DOORS databases together. I'm sure someone must have had this problem to solve before. Looks like I will need to get the DXL manual out again.
|
Re: Multiple DOORS Databases Chris Palmer - Wed Nov 12 11:16:07 EST 2014 Hi Wolfgang, We do use both RTC and RQM with OSLC hence my bracketed comment, we are also looking at using something like Raphsody to link to the databases and do some form of comparison etc. there. We have also linked a DOORS database to external applications like Requirements Central again with OSLC so it seems strange that you can't link 2 DOORS databases together. I'm sure someone must have had this problem to solve before. Looks like I will need to get the DXL manual out again.
Hello Chris A new Dxl-manual cannot help you. If you connect to two different databases, you have two different doos clients. If you want to use some "Joined database feature", you have to use a multi database doors client, but there is no one. For my opinion, the best way is to mirror the modules which shall be linked from one database to the other. Let us Assume ModuleA in Database A and ModuleB in DatabaseB shall be linked Start a nighly batch routine, which performs Exchange ex- and imports. Export ModulA and import it in Database B and Export ModulB and import it in A. In the time Horizont of a day the module data are actual and you can link them. I assume that this method will be the fastest method to solve the problem. Best regards Wolfgang |
Re: Multiple DOORS Databases Hi Chris, If your objective is only to link requirements in 2 DOORS Databases, then it should be possible to do it using OSLC. Like how you'd have added RQM/RTC as Remote server, you need to add the other DOORS Database details. It should just work with out of the box functionality. So, in DB A, go to Local Keys, and create a key/secret. In DB B, add a Remote server using the local key created earlier. Add the Collaboration link type (I think you'll be able to choose References, Elaborated by etc - don't remember exact names of link types). Do the same steps vice versa as well - get local key from DB B, and add it into DB A. Since OSLC is provided via DWA, you'll need DWA configured for both databases. Hope that helps..
Best regards, |