| Product | License that is consumed by LQE | Description |
|---|---|---|
| Rational solution for Collaborative Lifecycle Management | TRS Consumer-Internal | For CLM products, such as Rational Quality Manager, Rational Team Concert, and Rational DOORS Next Generation, that user is configured to be a functional user and consume a TRS Consumer-Internal license. This license is distributed with the standard Rational Engineering Lifecycle Manager licenses. |
| Rational Rhapsody® Design Manager | TRS Consumer-Internal | Same as for CLM products. |
| Rational Focal Point™ | Rational Focal Point license | Because Rational Focal Point is not based on the Jazz platform, an actual Focal Point license is consumed by LQE. When LQE sends any request to Focal Point, it must authenticate by using some user ID, and that causes the license that is associated with the user ID to be consumed. The user ID used by LQE must have full access to the data. This type of user ID is sometimes called a functional user (that is, it is not a real person - it represents LQE). The data access is configured in Focal Point by a Focal Point administrator. |
| Rational DOORS | TRS Consumer-Internal | For Rational DOORS, a FLEX TRS license is consumed, but that license is distributed as part of RELM and must be hosted by a FLEX license server so that it is available to Rational DOORS to validate the login. In addition, to provide the TRS interface for LQE, you must be running Rational DOORS Web Access (DWA). The session consumes one DOORS or DWA user license. |
These are the minimum licenses required for LQE to connect to the different TRS data sources. However, if you click through to a resource in a Rational Engineering Lifecycle Manager view or query, or access the original lifecycle tool by hovering over on an OSLC link to an artifact, then a user license is consumed, just like when you start any standard session on that tool. For non-LQE users to view data in the specific product, you must add a license by logging in to the product or by hovering over an OSLC link to an artifact in the product.