Configuring DWA as a TRS provider
You can configure IBM®
Engineering Requirements Management DOORS® - Web
Access
(DWA) as
a provider for tracked resource sets (TRS) by editing configuration files and running Derby batch
files.
About this task
- LQE Functional User
- This standard IBM Engineering Requirements Management DOORS (DOORS) user handles Lifecycle Query Engine (LQE) requests from an integrated TRS consumer application to DWA. If this user has a user name and password other than the default values, those values must match entries in the festival.xml file, as described in the following procedure.
- trs.db.user
- This Derby database user can access the TRS database data, and is used by DWA to retrieve data from the database. If you want to use values other than the default user name and password, you must make entries in the festival.xml file. If you change the password, you must enter the new password in the Derby properties file.
- derby.user.admin
- This Derby database administrator currently does not provide functions for DWA. You can set a password for this user in the Derby properties file.
Important: Administrators must take action to maintain the integrity of the Derby
database and prevent it from becoming corrupted. For more information, see "Maintaining database
integrity" in the Derby Server and
Administration Guide.
Procedure
What to do next
After the integration with a TRS consumer application is configured with OSLC friend relationships, you must register DOORS as a TRS provider in the consumer application. For an example of that procedure, in the documentation for Rational® Engineering Lifecycle Manager, see "Register applications as TRS providers for the Lifecycle Query Engines".
LQE, which is used by a TRS consumer application such as IBM
Rational Engineering Lifecycle Manager, builds
a master index, or database, of data from multiple lifecycle tools. Each TRS provider tool publishes
its data through a TRS. LQE can collect or index the data from each tool. Teams can write queries,
which are like reports, for indexed data in the SPARQL language. When you add a data source for
DOORS in
the LQE Administration application, set these values:
- Number of threads for initial indexing: 1
- Number of threads for incremental indexing: 1
- Refresh rate: 60
On the Administration tab, click and set the following HTTP timeout values. The default is 60 seconds. Increase
both values:
- Connection timeout (minimum): 5 minutes (300 seconds)
- Socket timeout (minimum): 15 minutes (900 seconds)