It's all about the answers!

Ask a question

Have you downloaded DOORS Next Generation? If so, would you share your perspective?


Daniel Moul (4.9k1318) | asked Oct 08 '12, 8:24 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
edited Oct 09 '12, 5:13 p.m.
The DOORS NG the product team is seeking feedback on DOORS NG and the degree to which you think it achieves its objectives for the first release.

I've explained more in this blog post: After four betas: requesting your feedback on DOORS Next Generation

What is transparent development at jazz.net?  It's opportunities like this to interact with developers and product managers. I hope you will take advantage of this opportunity -- and help us make DOORS NG even better.

Thanks in advance 

Daniel Moul

Rational Offering and Strategy Delivery

*** Update ... PS: the blog post I reference above points to a small number of work items.  It would help if you could leave your feeedback in the relevant work items.

4 answers



permanent link
Norman Dignard (356688169) | answered Oct 09 '12, 1:14 p.m.
We have downloaded the M4 release  and have set it up and configured a project. We are now trying to import a DOORS Reqif file exported from our DOORS 9.4 server/client.   On running the import from the DNG web side. its complaining that the export was not generated using DOORS 9.5 .

Is there a DOORS 9.5 available for download? I checked the IBM passport advantage site and its not listed.
We are trying to assess the workload/issues of migrating from DOORS to DNG.

JAZZ/DNG server installation on Red Hat Enterprise Linux Server release 5.7, using the embeded db and tomcat.
Installation done using IBM IM 1.6.

On Friday I installed a new JTS instance, started the service and activated licenses. Today, Tues Oct 9, I created 2 users, and created one CLM project using all 3 products RM, QM & RTC. RM and QM using change management.

I started looking at the various logs and noted the following errors/warning in various logs as noted below.  There appears to be issues with the install and setup that I hope you can address:
 
In /var/ibm/InstallationManager/logs/20121005_1434.xml

<entry num='990' time='1349462378449' elapsed='05:19.38' level='ERROR' thread='main'>

 <logger>com.ibm.cic.common.logging.LogManager</logger>

 <class>org.eclipse.core.runtime.SafeRunner</class>

 <method>handleException</method>

 <message>Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.IllegalArgumentException: Argument not valid The element type "exec" must be terminated by the matching end-tag "&lt;/exec&gt;".</message>

 <exception>

  java.lang.IllegalArgumentException: Argument not valid The element type "exec" must be terminated by the matching end-tag "&lt;/exec&gt;".

  <stack>org.eclipse.swt.SWT.error(SWT.java:4064)</stack>

  <stack>org.eclipse.ui.internal.forms.widgets.FormTextModel.parseInputStream(FormTextModel.java:133)</stack>

  <stack>org.eclipse.ui.internal.forms.widgets.FormTextModel.parseTaggedText(FormTextModel.java:111)</stack>

  <stack>org.eclipse.ui.forms.widgets.FormText.setText(FormText.java:673)</stack>

  <stack>com.ibm.cic.agent.internal.ui.views.LogDetailsPage.selectionChanged(LogDetailsPage.java:212)</stack>

  <stack>org.eclipse.ui.forms.DetailsPart$1.run(DetailsPart.java:274)</stack>

  <stack>org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)</stack>

  <stack>org.eclipse.ui.forms.DetailsPart.showPage(DetailsPart.java:261)</stack>

  <stack>org.eclipse.ui.forms.DetailsPart.update(DetailsPart.java:234)</stack>

  <stack>org.eclipse.ui.forms.DetailsPart.selectionChanged(DetailsPart.java:219)</stack>

  <stack>org.eclipse.ui.forms.ManagedForm.fireSelectionChanged(ManagedForm.java:148)</stack>

  <stack>com.ibm.cic.common.ui.parts.TreeSection$PartAdapter.selectionChanged(TreeSection.java:42)</stack>

  <stack>com.ibm.cic.common.ui.parts.TreePart$1.selectionChanged(TreePart.java:56)</stack>

  <stack>org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)</stack>

  <stack>org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)</stack>

  <stack>org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)</stack>

  <stack>org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)</stack>

  <stack>org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)</stack>

  <stack>org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2162)</stack>

  <stack>org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1699)</stack>

  <stack>org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139)</stack>

  <stack>org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:392)</stack>

  <stack>com.ibm.cic.agent.internal.ui.views.LogSection.primeSelection(LogSection.java:425)</stack>

  <stack>com.ibm.cic.agent.internal.ui.parts.TreeMasterDetailsBlock.createContent(TreeMasterDetailsBlock.java:48)</stack>

  <stack>com.ibm.cic.agent.internal.ui.dialogs.ViewLogDialog.createLogView(ViewLogDialog.java:266)</stack>

  <stack>com.ibm.cic.agent.internal.ui.dialogs.ViewLogDialog.createDialogArea(ViewLogDialog.java:249)</stack>

  <stack>org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:760)</stack>

  <stack>org.eclipse.jface.window.Window.create(Window.java:431)</stack>

  <stack>org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)</stack>

  <stack>com.ibm.cic.agent.internal.ui.dialogs.ViewLogDialog.create(ViewLogDialog.java:117)</stack>

  <stack>org.eclipse.jface.window.Window.open(Window.java:790)</stack>

  <stack>com.ibm.cic.agent.internal.ui.wizards.CompletionPage$1.linkActivated(CompletionPage.java:203)</stack>

  <stack>org.eclipse.ui.forms.widgets.FormText.activateLink(FormText.java:1552)</stack>

  <stack>org.eclipse.ui.forms.widgets.FormText.handleMouseClick(FormText.java:1355)</stack>

  <stack>org.eclipse.ui.forms.widgets.FormText.access$16(FormText.java:1326)</stack>

  <stack>org.eclipse.ui.forms.widgets.FormText$6.mouseUp(FormText.java:448)</stack>

  <stack>org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213)</stack>

  <stack>org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)</stack>

  <stack>org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)</stack>

  <stack>org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552)</stack>

  <stack>org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171)</stack>

  <stack>org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)</stack>

  <stack>org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)</stack>

  <stack>org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)</stack>

  <stack>org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)</stack>

  <stack>org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)</stack>

  <stack>org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)</stack>

  <stack>org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)</stack>

  <stack>com.ibm.cic.agent.internal.ui.AgentUIApplication.launch(AgentUIApplication.java:251)</stack>

  <stack>com.ibm.cic.agent.internal.ui.AgentUIApplication.start(AgentUIApplication.java:62)</stack>

  <stack>org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)</stack>

  <stack>org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)</stack>

  <stack>org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)</stack>

  <stack>org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)</stack>

  <stack>org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)</stack>

  <stack>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</stack>

  <stack>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)</stack>

  <stack>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)</stack>

  <stack>java.lang.reflect.Method.invoke(Method.java:611)</stack>

  <stack>org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)</stack>

  <stack>org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)</stack>

  <stack>org.eclipse.equinox.launcher.Main.run(Main.java:1408)</stack>

  <stack>org.eclipse.equinox.launcher.Main.main(Main.java:1384)</stack>

 </exception>

 In the JTS/server/logs/admin.log

 2012-10-05 14:45:22,937 [         http-bio-9443-exec-15]  INFO com.ibm.team.lpa.config                             - CRJCA0037I Lifecycle Project Administration Build RJF-I20120927-1932

2012-10-05 14:45:22,977 [         http-bio-9443-exec-15]  INFO com.ibm.team.lpa.config                             - com.ibm.team.lpa.app.jtsTargetHost=LpaInit.Default

2012-10-05 14:45:22,977 [         http-bio-9443-exec-15]  INFO com.ibm.team.lpa.config                             - com.ibm.team.lpa.app.jtsVirtualHost=LpaInit.Default

2012-10-05 14:45:22,979 [         http-bio-9443-exec-15]  INFO com.ibm.team.lpa.config                             - CRJCA0028I Initialization of the Lifecycle Project Administration Application failed.  Please register the Lifecycle Project Administration application with the Jazz Team Server.

 In ccm.log – getting a number of

Caused by: ERROR 40XL1: A lock could not be obtained within the time requested

 Also getting the above in the jts.log

SQL: SELECT UUID FROM REPOSITORY.CONTENT_STORAGE WHERE CLAIMED = ? AND MODIFIED  < ?

SQL Exception #1

SQL Message: A lock could not be obtained within the time requested

SQL State: 40XL1

Error Code: 30000

 

java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested

                at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)

                at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

                at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)

                at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)

                at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)

                at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)

                at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)

                at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)

                at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeQuery(Unknown Source)

                at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.executeQuery(PreparedStatementStatWrapper.java:60)

                at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.executeQuery(PreparedStatementErrLogWrapper.java:78)

                at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.executeQuery(PreparedStatementLeakWrapper.java:57)

                at com.ibm.team.repository.service.internal.dataaccess.delete.AbstractBackgroundDeleter.selectKeys(AbstractBackgroundDeleter.java:261)

                at com.ibm.team.repository.service.internal.dataaccess.delete.AbstractBackgroundDeleter.doIt(AbstractBackgroundDeleter.java:133)

                at com.ibm.team.repository.service.internal.dataaccess.delete.AbstractBackgroundDeleter.run(AbstractBackgroundDeleter.java:84)

                at com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.cleanupUnclaimedContent(RdbRepositoryDataMediator.java:1246)

                at com.ibm.team.repository.service.internal.dataaccess.delete.ItemCleanup.doAllPendingItemCleanup(ItemCleanup.java:201)

                at com.ibm.team.repository.service.internal.dataaccess.delete.ItemCleanupService$1.run(ItemCleanupService.java:136)

                at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:500)

                at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:324)

                at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)

                at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

                at java.lang.reflect.Method.invoke(Method.java:611)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

                at $Proxy1429.withCurrentConnection(Unknown Source)

                at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:320)

                at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runInTransaction(RepositoryDatabase.java:275)

                at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runInTransaction(PrimitiveTransactionService.java:110)

                at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

                at java.lang.reflect.Method.invoke(Method.java:611)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

                at $Proxy1442.runInTransaction(Unknown Source)

                at com.ibm.team.repository.service.internal.dataaccess.delete.ItemCleanupService.completePartialItemDeletions(ItemCleanupService.java:141)

                at sun.reflect.GeneratedMethodAccessor1080.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

                at java.lang.reflect.Method.invoke(Method.java:611)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

                at $Proxy1463.completePartialItemDeletions(Unknown Source)

                at com.ibm.team.repository.service.internal.ItemCleanupTask.runTask(ItemCleanupTask.java:22)

                at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:89)

                at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

                at java.lang.reflect.Method.invoke(Method.java:611)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

                at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

                at $Proxy1514.executeTask(Unknown Source)

                at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:136)

                at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:99)

                at java.lang.Thread.run(Thread.java:738)

 

And in the qm.log

2012-10-05 14:45:09,321 [          http-bio-9443-exec-5]  INFO .repository.service.internal.rdb.ConnectionFactory  - CRJAZ1364I The connection to the following database was successful:

 Db Product Name: Apache Derby

  Db Product Version: 10.8.2.3 - (1212722)

  Db URL: jdbc:derby:conf/qm/derby/repositoryDB;create=true

  Jdbc Driver Name: Apache Derby Embedded JDBC Driver

  Jdbc Driver Version: 10.8.2.3 - (1212722)

…..

….

  Jazz Team Server location: "https://jazz1.deveng.local:9443/jts/"

2012-10-05 14:48:11,463 [         http-bio-9443-exec-19]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at VariableMapEntry#value is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.

2012-10-05 14:48:11,469 [         http-bio-9443-exec-19]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Item reference at ManualExecutionScript#elements is marked as a containment reference but it should not be. All Item references should be marked as non-containment. Please update your model so that the containment is correct.

2012-10-05 14:48:11,812 [         http-bio-9443-exec-19]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at VariableMapEntry#value is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.

2012-10-05 14:48:12,154 [         http-bio-9443-exec-19]  WARN ice.internal.verticalRegistry.ComponentORMProvider  - The Helper reference at DatapoolVariable#suggestedType is marked not as a containment reference but it should be. All Helper references should be marked as containment. Please update your model so that the containment is correct.

2012-10-05 14:48:13,293 [         http-bio-9443-exec-19] ERROR com.ibm.rqm.buildintegration.service                - com.ibm.rqm.integrationprovider.service.rest.internal.ConnectionRestService:scheduleRTCBuildInfoCollectorTask AQXIN5019E Failed to reschedule the task: componentId "com.ibm.rqm.buildintegration", taskId "rtcBuildInformationCollector"

java.lang.NullPointerException

 

2012-10-05 14:48:50,986 [         http-bio-9443-exec-24]  WARN com.ibm.team.datawarehouse                          - com.ibm.team.repository.common.TeamRepositoryException: The new user could not be created because a user with the user id "etl_user" already exists.

 

2012-10-05 14:56:54,706 [ qm: AsynchronousTaskRunner-11]  WARN com.ibm.rqm.defects.service                         - com.ibm.rqm.defects.service.internal.ChangeRequestCollector:hadInitialized AQXIN2503W Automatic synchronization of blocking defects with the Change Management provider has not been configured properly and will be disabled.

 

2012-10-05 15:48:14,602 [ qm: AsynchronousTaskRunner-14]  INFO sqlExceptionLogger                                  - Invalid transaction state

SQL Exception #1

SQL Message: Cannot close a connection while a transaction is still active.

SQL State: 25001

Error Code: 20000

 java.sql.SQLException: Cannot close a connection while a transaction is still active.

 

In rm.log  numerous error msgs:

2012-10-09 09:48:36,991 [        RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - java.lang.RuntimeException: Parse error org.xml.sax.SAXParseException: Content is not allowed in prolog.

  Line number: 1

Column number: 1

 Public ID: null

 System ID: null

2012-10-09 09:48:37,347 [        RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - java.lang.RuntimeException: Parse error org.xml.sax.SAXParseException: Content is not allowed in prolog.

  Line number: 1

Column number: 1

 Public ID: null

 System ID: null

 

2012-10-09 09:48:38,166 [        RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - Error validating XHTML for artifact _10576_19af2546-013d-4437-ab89-3341f2bca4ec: org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.

2012-10-09 09:48:38,171 [        RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - java.lang.RuntimeException: Parse error org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.

 2012-10-09 10:15:43,643 [        RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - com.ibm.rdm.fronting.server.exception.ForbiddenException: CRRRS8657E  Invalid value specified for attribute attrDefURL: https://jazz1.deveng.local:9443/rm/resources/_6fd0a07e-f405-49f8-abac-f5ac8567ed4f

 

Also in the tomcat catalina.out:

[Fatal Error] :1:1: Content is not allowed in prolog.

2012-10-09 09:48:36,991 RRC [RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - java.lang.RuntimeException: Parse error org.xml.sax.SAXParseException: Content is not allowed in prolog.

  Line number: 1

Column number: 1

 Public ID: null

 System ID: null

2012-10-09 09:48:38,171 RRC [RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - java.lang.RuntimeException: Parse error org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.

  Line number: 1

Column number: 69

 Public ID: null

 System ID: null

 

2012-10-09 10:15:43,643 RRC [RRS-Command-Executor-2] ERROR bm.rdm.fronting.server.services.reqif.ReqIFService  - com.ibm.rdm.fronting.server.exception.ForbiddenException: CRRRS8657E  Invalid value specified for attribute attrDefURL: https://jazz1.deveng.local:9443/rm/resources/_6fd0a07e-f405-49f8-abac-f5ac8567ed4f

 

Regards
Norm Dignard

Comments
Daniel Moul commented Oct 09 '12, 5:11 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

@normd I have asked someone on the product team to respond to your questions directly.  Let me make a larger point right now:  ReqIF can be used to move a copy of the current requirements in a DOORS 9 repository to seed a project in DOORS NG repository, but this is not migration in the proper sense of that word.  ReqIF files do not contain all of the information in a DOORS repository (e.g. doesn't include the change history of objects). Also a ReqIF transfer does not address traceability links that start in another system (e.g, a Quality Management system) and link into a DOORS repository.

I mention this so you can have (and set) good expectations for what "migration" would accomplish.

Also you can review the release objectives for this years DOORS NG release by looking at the blog post I referenced above and follow the link to the first work item.  (I will also modify this question to make it clearer that I'm hoping for feedback in the work items).


permanent link
Norman Dignard (356688169) | answered Oct 10 '12, 9:17 a.m.
Thanks for your insight however we are aware of some of the limitations in data migration using  ReqiF. As it is we are not expecting history or external links to be migrated.  As this point we are testing migration from DOORS to DNG to get a feeling of the efforts required in migrating. As yet we have been unable to migrate a moderate amount of data from DOORS 9.4 to DOOR NG beta4 and M4. The import stalls at 5% and never completes (for a modest file size of 121M). I've asked Edmund Mayer at IBM some questions about the issues we've had in testing the reqif export/import but have yet to get an answer. Aside from an import of  small module, all out import attempts have fails on larger files. The import appears to just hang during the "upload" stage of the import. 

 Here is what we are expecting:
-          current versions only (not history or baselines)
-          a small number of modules only
-          object heading, text, and all other attributes to be transferred
-          internal links between modules to be transferred
-          modules may contain OLE objects

Would you not expect the above to be reasonable for data migration efforts to review the look and feel of our current data in NG, especially traceability?

Comments
Daniel Moul commented Oct 10 '12, 9:34 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Yes I would expect the items you note to work by the time we release DOORS NG and DOORS 9.5 [footnotes: (1) DOORS 9.5 is not available yet; and (2) DOORS NG handles OLE objects differently than DOORS 9. I don't have the details at hand at the moment].

The developers working on this scenario have been improving ReqIF support in DOORS NG and in DOORS 9.x, and I'm not close enough to this work to offer guidance on what should work with DOORS 9.4.0.1 (which had improvements in this area over 9.4.0.0). And the warning in M4 that the ReqIF file was not generated by DOORS 9.5 is a reflection of fixes post-9.4.0.1 that are important.... thus my comment that I've asked someone else to answer more specifically.


Daniel Moul commented Nov 29 '12, 11:37 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

permanent link
Shiv Singh (1156) | answered Nov 21 '12, 6:18 p.m.
JAZZ DEVELOPER
Dan,
I had DOORS NG  M4 and DOORS v9.5 earlier. ReqIF exported file [without any links] couldn't be imported in DOORS NG.
So upgraded to RC3 of DOORS NG, still couldn't successfully import the ReqIF.
However my colleague confirmed that he could import similar ReqIF using RC2.
The difference was  RC2 instance [on his machine] had DB2 as database whereas RC3 instance had Derby as database.
OS in both cases were Windows 7 - 64 bit and Web Server was Tomcat.
Hope this helps you debug the issue.
Shiv

Comments
Daniel Moul commented Nov 27 '12, 10:25 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

@majorshiv thanks for mentioning this.

I double-checked with the DOORS dev & test teams. They tested this successfully on recent RCs where DOORS NG used Tomcat and Derby as well as Tomcat and DB2.

I suggest using the GA code of both DOORS 9.5 and DOORS NG 4.0.1 (both available as of today!)


permanent link
david groff (122) | answered Aug 23 '13, 1:56 p.m.
Better Handling of OLE Objects from DOORS to DNG via ReqIF import (this likely has several requirements within)

When importing a ReqIF package from DOORS 9.5.x, OLE Objects are created differently in DNG depending on whether the DOORS Object also contained Text.An OLE Object that contained additional Text is created as Artifact in DNG of type 'Text'  with a link to the Embedded Artifact.

In order to display the image in-line with the text similar to DOORS, the user has to navigate to the embedded artifact, open it with the appropriate application, copy the image/table/etc and save the image as a bmp or png etc that can then be inserted into the Artifact. If however the OLE was standalone (contained no additional text) the resulting Artifact in DNG is created as type 'File'.   This Artifact is NOT editable.

IF the user wishes to display the Graphic in-line, they have to go through the same steps of opening, copying, and saving the file as a bmp/png/etc BUT.....they also have to CREATE a NEW ARTIFACT in order to
insert the graphic. The Graphic CANNOT be inserted into the original artifact because it is of type 'File'
This then also requires the user to set all the Attributes correctly as per the original artifact.

Three Requests:
1) Minimum requirement:  Create ALL OLE Artifacts as type Text....not File.  This would at least eliminate the need for the user to have to create a new artifact each time.

2) Preferred:  Create the Artifact of type Text, with the 'Embedded artifact' link BUT also create the necessary Graphic Image and insert it into the same Artifact.
.
Business impact ( BusImpact )
Some data modules have many (+650)  OLEs and/or Pictures forcing manual conversion each one to a graphic and
then insert it into the Artifact for display.  (and possibly creating NEW artifacts when the original is not editable).

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.