RRC Integration with DOORS

i've gone through the ibm document on customizing the interface and edited the festival.xml file using the URI and everything and have done the dbadmin lines. broker.start doesn't start. It flashes on the screen about unable to generate bean or something and errors and stops.

i've gone through the ibm document on customizing the interface and edited the festival.xml file using the URI and everything and have done the dbadmin lines. broker.start doesn't start. It flashes on the screen about unable to generate bean or something and errors and stops.

here is my error
ERROR BrokerService - Failed to start ActiveMQ JMS Message Brok
er. Reason: java.io.IOException: Transport Connector could not be registered in
JMX: Failed to bind to server socket: tcp://localhost:61616 due to: java.net.Soc
ketException: Invalid argument: listen failed
java.io.IOException: Transport Connector could not be registered in JMX: Failed
to bind to server socket: tcp://localhost:61616 due to: java.net.SocketException
: Invalid argument: listen failed
at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport
.java:27)

To serve as a notice to those participating in this thread:

As many of you know we are making significant changes and improvements to RRC as we prepare for its next release. Because of the architectural changes from a thick client to a Web client the DOORS 9.x and RRC 2.0 point integration will not immediately be taken forward and supported. RRC 3.0 will not support the point to point synchronization integration any longer.

We are working towards a new OSLC based integration which will improve the way we manage requirements between the two environments but this will not be available until a later RRC and DOORS release. We understand that there will be a functional gap between this release period and we ask for your patience as we improve the ability to generate visual requirements in RRC and linked to DOORS.

We encourage you to evaluate the next version of RRC to plan for the change in methodology for Requirements Definition and Management.

Jared Pulham
Product Manger, Requirements Management Tools

Is the ultimate goal for RRC to remove dependencies on DOORS/REQPRO interfaces for requirements management, period? If so, at what release do you anticipate this separation to occur? Will RRC be able to provide robust capabilities to generate technical specifications using RPE?

To serve as a notice to those participating in this thread:

As many of you know we are making significant changes and improvements to RRC as we prepare for its next release. Because of the architectural changes from a thick client to a Web client the DOORS 9.x and RRC 2.0 point integration will not immediately be taken forward and supported. RRC 3.0 will not support the point to point synchronization integration any longer.

We are working towards a new OSLC based integration which will improve the way we manage requirements between the two environments but this will not be available until a later RRC and DOORS release. We understand that there will be a functional gap between this release period and we ask for your patience as we improve the ability to generate visual requirements in RRC and linked to DOORS.

We encourage you to evaluate the next version of RRC to plan for the change in methodology for Requirements Definition and Management.

Jared Pulham
Product Manger, Requirements Management Tools

Is
================
what is the status of this integration? You wont know this integration wasn't there by looking at the CLM 2011 release, so people assume it's still there! When is this OSLC integration going to be there?

===================

the ultimate goal for RRC to remove dependencies on DOORS/REQPRO interfaces for requirements management, period? If so, at what release do you anticipate this separation to occur? Will RRC be able to provide robust capabilities to generate technical specifications using RPE?

To serve as a notice to those participating in this thread:

As many of you know we are making significant changes and improvements to RRC as we prepare for its next release. Because of the architectural changes from a thick client to a Web client the DOORS 9.x and RRC 2.0 point integration will not immediately be taken forward and supported. RRC 3.0 will not support the point to point synchronization integration any longer.

We are working towards a new OSLC based integration which will improve the way we manage requirements between the two environments but this will not be available until a later RRC and DOORS release. We understand that there will be a functional gap between this release period and we ask for your patience as we improve the ability to generate visual requirements in RRC and linked to DOORS.

We encourage you to evaluate the next version of RRC to plan for the change in methodology for Requirements Definition and Management.

Jared Pulham
Product Manger, Requirements Management Tools

Is
================
what is the status of this integration? You wont know this integration wasn't there by looking at the CLM 2011 release, so people assume it's still there! When is this OSLC integration going to be there?

===================

the ultimate goal for RRC to remove dependencies on DOORS/REQPRO interfaces for requirements management, period? If so, at what release do you anticipate this separation to occur? Will RRC be able to provide robust capabilities to generate technical specifications using RPE?

To serve as a notice to those participating in this thread:

As many of you know we are making significant changes and improvements to RRC as we prepare for its next release. Because of the architectural changes from a thick client to a Web client the DOORS 9.x and RRC 2.0 point integration will not immediately be taken forward and supported. RRC 3.0 will not support the point to point synchronization integration any longer.

We are working towards a new OSLC based integration which will improve the way we manage requirements between the two environments but this will not be available until a later RRC and DOORS release. We understand that there will be a functional gap between this release period and we ask for your patience as we improve the ability to generate visual requirements in RRC and linked to DOORS.

We encourage you to evaluate the next version of RRC to plan for the change in methodology for Requirements Definition and Management.

Jared Pulham
Product Manger, Requirements Management Tools

Agreed we have posted a number of statements on jazz.net for the removal of this integration but some might still assume that it is still included. We are working at the moment to close this in the CLM (RRC) 2012 release plan and when we have the plan approved then we would update our release plan on jazz.net to reflect our intention.

Today we have had two possible methods to allow customers to move forward with RRC 3.0.1:

One: Design Manager and RSA both support OSLC linking to requirements in RRC. This means that you can create models/elements and then connect them to requirements in RRC. You will be able to see these links in RSA and even use them to navigate or report to the requirements in RRC 3.0.1. RRC however does not show the link from the other end so it is so from a reporting and support point of view you would have a uni-directional solution.

Two: We have had a few customers using a work/plan item from the new planning capability (provided from RTC) to allow traceability from Requirements to plan items and then to models. Because a business analyst now has access to RTC plan items with an RRC license we can use these to our advantage to build a supported model today.