Licenses are acquired for each user session, but are managed on the server side rather than in the client process. The server acquires licenses from the license server when users connect. When users log off, the server releases the licenses. Users do not need direct access to the license server through any firewalls that might exist.
The Rational License Key Server must be installed on your system. For information about the Rational License Key Server, see Rational Common Licensing information.
The licensing models differ between Rational DOORS and Rational DOORS Web Access. Rational DOORS licensing is client-based and uses hostname, while Rational DOORS Web Access is server-based and uses username. Because the products use different licensing models, you cannot share Rational DOORS licenses even if they are running on the same computer. For information about license usage and when it is required, see the following table.
Action | License requirement |
---|---|
Start and run the Rational DOORS Web Access server | No license is required |
Log in to Rational DOORS Web Access through the client | A license is required |
Another tool implements code directly against the OSLC RM domain to use it as a server API | A license is required |
Show Rational DOORS data from an integrated product by using a delegated UI for selecting requirements or UI previews, such as compact rendering and rich hovers | A license is not required |
Use node-locked licenses on the Rational DOORS Web Access server | Not supported |
The following products integrate with Rational DOORS and use back links. When a user creates a link that requires an update to Rational DOORS to add a back link, a license is required. The OSLC GET and PUT commands are used.
The following products integrate with Rational DOORS and use link discovery. To determine traceability, you must authenticate to the user database of another tool, so a license is required. However, if a user creates a link, no Rational DOORS data needs to change, so no license is required.