Configuring DOORS web access to communicate with other components

After you have installed Rational® DOORS® Web Access, you must configure the components to communicate with one another, and to provide OSLC services.

Setting Rational DOORS database server parameters

You must configure the Rational DOORS database server to communicate with the Rational DOORS Web Access broker and the Rational DOORS Web Access server by adding parameters to the command line. The instructions for completing these tasks are here: Configuring the Rational DOORS database server to communicate

Setting up the Rational DOORS Web Access server

Once you have installed DOORS web access, you must set up the DOORS Web Access server to communicate with the broker, the license server, and the Rational DOORS database server. The instructions for completing these tasks are here: Setting up the Rational DOORS Web Access server

Configuring Rational DOORS Web Access to use SSL

The Rational DOORS Web Access server can be configured to use SSL, which is the default used by the Rational solution for systems and software engineering. To enable Rational DOORS Web Access to use SSL, follow the instructions here: Configuring Rational DOORS Web Access to use SSL or TLS
Tip: Because several web browsers such as Mozilla Firefox now block mixed SSL content (that is, having SSL and non-SSL content on the same page), we recommend enabling all applications in the Rational solution for systems and software engineering to use SSL.

Increase the OAuth timeout

Increase the OAuth timeout allowances to match the Jazz™ applications (24 hours).
Note: For DOORS Web Access version 9.5 or later this step is optional.
  1. Open [DWA_path]/server/conf/web.xml.
  2. Search for session-timeout. Change the value to 1440 (minutes). Save the file.
  3. Open [DWA_path]/server/festival/config/festival.xml.
  4. Search for OauthAccessTokenTimeout. Change the value to 1440 (minutes). Save the file.

Feedback