Romain_Barth 2700076HKB Visits (8375)
You have multiple DOORS databases to organize you DOORS projects.
There is no documentation or feature to do that task.
This can do done via DXL
AcdntlPoet 2700019V2G Visits (9396)
Romain_Barth 2700076HKB Visits (9527)
When DOORS 9 is integrated with Rational Quality Manager, Rational Design Manager or Rational DOORS Next Generation, it uses Discovery Links to link DOORS requirement to other Artifacts.
This means that DOORS does not store any of those links but it queries the other tools to know if there are links to DOORS requirements. Here is more details about discovery links : http
Baseline is one of the main feature in DOORS. As those OSLC links are not stored in DOORS, what about those links in baselines ?
Unfortunately those OSLC links are not displayed in DOORS baseline:
Baselined objects have different URIs than the original object URIs. When creating a baseline in a module, DOORS does not create new links from the baselined objects to the OSLC provider. Even if DOORS created the links, there is no way to make these links immu
To summarize, OSLC integration doesn't support baselines.
Romain_Barth 2700076HKB Visits (6247)
Is there a way to delete multiple linksets from a link module including all the contained links?
The DOORS UI does not provide that feature but it is possible by using DXL.
Here is a sample that will delete all the linksets and links contained in a specific project:
First, open your link module in Exclusive Edit mode, then run the script above.
Romain_Barth 2700076HKB Visits (9427)
By using DXL, however, you can do this task quickly. Here is a sample of code to help you perform it:
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (11087)
Are you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)?
Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki
Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati
There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details:
Sizing Guidelines for Rational DOORS Next Generation 6.x
Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration
Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations?
The guidance is clearly aimed for the general use cases and is very much our strongest recommendation.
It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.
AcdntlPoet 2700019V2G Visits (11083)
Migrating data from IBM Rational DOORS to IBM Rational DOORS Next Generation- With the release of IBM Rational DOORS 184.108.40.206 and IBM Rational DOORS Next Generation V6.0.1 the migration has been optimized, now automatically creating a global type system and artifact types in IBM Rational DOORS Next Generation, considering the commonalities of the type system defined in modules within DOORS, as well as links relationships. In addition, you can now incrementally migrate a project, and the two applications will automatically maintain and update link relationships with every incremental migration.
Migration is not interchange of data where data can go from one tool to another and possibly back again. Migration is a one-way move from Rational DOORS to Rational DOORS Next generation, with traceability back to the source.
Using a migration package, migration can include one or more modules and can be incremental, migrating a little at a time, and only what you need. The current version of modules is migrated along with internal external and OSLC links, OLE objects, pictures and so forth.
The history of the migrated data is not migrated however, the migration creates links in Rational DOORS Next Generation that link back to the corresponding records in Rational DOORS.
AcdntlPoet 2700019V2G Visits (10541)
Migrate data from Rational DOORS to Rational DOORS Next Generation- Kim Letkeman, Senior Technical Staff Member, IBM and Martin Henderson, Development Manager, IBM, lead you through planning and implementing a DOORS migration project.
Plan and execute a migration project from IBM® Rational® DOORS® to IBM Rational DOORS Next Generation. This article provides a list of migration terms and definitions (as opposed to interchange) and describes the phases and tasks involved when moving active data into a Collaborative Lifecycle Management environment.
AcdntlPoet 2700019V2G Visits (10163)
How to index DOORS 9.6 artifacts in Lifecycle Query Engine - John Carolan demonstrates the steps required to enable DOORS 9.6 as a Tracked Resource Set (TRS) provider and how to add that feed to Lifecycle Query Engine (LQE) as a new Data Source.