RRC Integration with DOORS

Has anyone configured the RRC - DOORS integration yet? I have installed DOORS 9.2.0.2 and RRC 2.0 but can not get the integration to work. I run into issues when RRC can not find the DOORS database.

Any help ?

I think the issue here is that you do not have the Interface Services Server setup correctly for DOORS. After installation of the DOORS 9.2.0.2 fixpack, you must follow the installation guide in order to setup and configure the interface services which will allow RRC to communicate with DOORS.

Installation guide:
http://publib.boulder.ibm.com/infocenter/rsdp/v1r0m0/topic/com.ibm.help.download.doors.doc/pdf92/doors_install_guide.pdf

Take a look at Chapter 8 (page 51) for setting this up on Windows and follow the steps listed. After following these steps, you can then attempt to run the RRC/DOORS integration. Note that the Interface Services server port number defaults to 8080, which is what you would use when specifying the port number for the integration

This does appear to work fine after configuring and starting the Interface Services Server. Just to clarify, this is the service that you install by selecting "Custom Setup" during the DOORS Database installation, and then extracting the file it lays down (festival-win32.zip), configuring it (changing the port, adding the DOORS DB UID), and starting the service (server.startup.bat).

After everything is configured:

1) Start the message broker (broker.start.bat)
2) Start the interop server (doors.exe -interop -data 36677@<hostname> -brokerHost <hostname> -brokerPort 61616
3) Start the Interface Services Server (server.start.bat, from C:\program files\ibm\rational\doors\9.2\interfaces\festival-win32).

Hope it helps,

Hi all,

I also have a problem when I try to connect to the Doors database.
I get the message no Doors database were found.

I followed the installation guide but it still doesn't work.
I installed:
- RRC Version: 2.0.0.1
- Doors Client version: 9.2.0.2
all tools are on the same virtual machine and running on Windows Server 2003.

Rational Database Server 9.2 is started as a Windows Service.
Broker is started:
D:\Rational\DOORS\9.2\interfaceservice>broker.start.bat
ACTIVEMQ_HOME: D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..
ACTIVEMQ_BASE: D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..
Loading message broker from: xbean:activemq.xml
INFO PrimaryRouteBuilder - Configuring Festival Router 1.0
INFO PrimaryRouteBuilder - Finished configuring Festival Router
INFO AdminRouteBuilder - Configuring Festival Router 1.0
INFO AdminRouteBuilder - Finished configuring Festival Router
INFO TiredRouteBuilder - Configuring Festival Router 1.0
INFO TiredRouteBuilder - Finished configuring Festival Router
INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..\data)
INFO BrokerService - ActiveMQ 5.2-SNAPSHOT JMS Message Broker (localhost) is starting
INFO BrokerService - For help or more information please see: http://activemq.apache.org/
INFO AMQPersistenceAdapter - AMQStore starting using directory: D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..\data
INFO KahaStore - Kaha Store using data directory D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..\data\kr-store\state
INFO AMQPersistenceAdapter - Active data files: []
INFO KahaStore - Kaha Store using data directory D:\Rational\DOORS\9.2\interfaceservice\broker\bin\..\data\kr-store\data
INFO TransportServerThreadSupport - Listening for connections at: tcp://vm16adt01:61616
INFO TransportConnector - Connector openwire Started
INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:vm16adt01-3003-1274262198626-1:0) started
INFO TransportConnector - Connector vm://localhost Started

The Doors Client is started via:
doors.exe interop data 36677@vm16adt01 brokerHost vm16adt01 61616


The Interface Services Server is also started:
<19> INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'FestivalServlet': initialization completed in 156 ms
<19> INFO org.apache.coyote.http11.Http11BaseProtocol - Starting Coyote HTTP/1.1 on http-8080
<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8009 java.net.BindException: Address already in use: NET_Bind
<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8010 java.net.BindException: Address already in use: NET_Bind
<19> INFO org.apache.jk.common.ChannelSocket - JK: ajp13 listening on /0.0.0.0:8011
<19> INFO org.apache.jk.server.JkMain - Jk running ID=2 time=0/15 config=null
<19> INFO org.apache.catalina.storeconfig.StoreLoader - Find registry server-registry.xml at classpath resource
<19> INFO org.apache.catalina.startup.Catalina - Server startup in 6782 ms

if I try to connect via Browser to the local machine on port 8080 I get an empty page, but no error. Is this ok ?

In RRC I create a new Doors connection like this:

Server: vm16adt01:8080
username: Administrator
password: database password

the username and password should be the Database username and password. Is that right ?

So did I forget something ?
What about this info message:

<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8009 java.net.BindException: Address already in use: NET_Bind
<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8010 java.net.BindException: Address already in use: NET_Bind

I'm not sure the interface services server should be reporting success when it also reports that ports are in use:

<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8009 java.net.BindException: Address already in use: NET_Bind
<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8010 java.net.BindException: Address already in use: NET_Bind

You will want to free up these ports before attempting to use the server. You can run a netstat -aon while the interface services server is shut down to see what is running on 8009 and 8010. Match the PIDs from netstat to the PIDs in Windows Task Manager (just make sure you enable the PID column through View -> Select Columns -> PID).

If it's not something you need, you can kill the process. Otherwise, you will want to re-configure the interface services server to use different ports. Hope it helps,

I'm not sure the interface services server should be reporting success when it also reports that ports are in use:

<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8009 java.net.BindException: Address already in use: NET_Bind
<19> INFO org.apache.jk.common.ChannelSocket - Port busy 8010 java.net.BindException: Address already in use: NET_Bind

You will want to free up these ports before attempting to use the server. You can run a netstat -aon while the interface services server is shut down to see what is running on 8009 and 8010. Match the PIDs from netstat to the PIDs in Windows Task Manager (just make sure you enable the PID column through View -> Select Columns -> PID).

If it's not something you need, you can kill the process. Otherwise, you will want to re-configure the interface services server to use different ports. Hope it helps,

I changed the port from 8009 in the server.xml to 8014

Connector port="8014"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /

now the server starts without java.net.BindException, but the database could still not be found in RRC.

Any other solutions ?

There are a few things you need to do before the integration will work. Hopefully this helps,

1) Configure the re-director:

from \program files\ibm\rational\doors\9.2\bin:

dbadmin -data 36677@servername -urlPrefix http://servername:8080/doors/redirector

2) Enable dcn:

dbadmin -data 36677@servername -dcnEnable -dcnBrokerUri
tcp://servername:61616 -dcnChannelName "dcn"

3) Start the broker (broker.start.bat)

4) Start the interop:

doors.exe -interop -data 36677@servername -brokerHost servername -brokerPort 61616

5) Start the interface services (server.start.bat)

Make sure you're using an administrator login when you attempt to connect to the DOORS DB from RRC.

We have installed Doors again on an other machine and now the doors database appears in RRC. What we want to do is to import the requirements from Doors to RRC and not from RRC to Doors. Is this also possible ?

What we want to do is to import the requirements from Doors to RRC and not from RRC to Doors. Is this also possible ?

Right now the integration is one way (RRC -> DOORS), but I think you could do this manually:
1. In DOORS export to MS Word
2. In RRC upload Word doc
3. For each object that should be separate in RRC highlight it, right-click and "mark as requirement"

Hi, I am having similar problems with the DOORS-RRC integ. I am using DOORS 9.2.0.3 and Composer 2.0.0.2.

I have been through the user guide a couple of times and checked my settings and have started all the components in order.

When I go into Composer to Create a Connection, I add in the FQDN and then enter the DOORS user name Administrator and password abc123.

It takes a long time (hour glass appearing) and then reports the error:
CRRC2100E Either the UserName or is not valid. Yet I use this UN and PW to enter the DOORS client freely.

Any suggestions and how to trouble shoot this?

I have seen this before when attempting to access the server with a user that does not have the appropriate permissions to the DOORS database. Try accessing with the administrator user to see if this makes a difference. Hope it helps,