You can integrate HCL Compass with other software by adding packages to existing schema.
Collaborative Lifecycle Management integrations provide a common approach to artifact linking, dashboards, security, and user interface frameworks. Cross-product links support traceability, web-like navigation, commenting, and status tracking across project repositories.
This section discusses how to configure HCL Compass Web to use the Collaborative Lifecycle Management integrations.
The OAuth protocol enables web sites or applications (consumers) to access protected resources from a web service (service provider) through an API without requiring users to disclose their service provider credentials to the consumers.
After configuring the HCL Compass Web server for cross-server communication, configure project relationship links.
You must configure the target OSLC service provider for cross-server communication back to the HCL Compass Web server to complete configuring Compass Web for a Collaborative Lifecycle Management integration.
If an administrator is configuring cross-server communication with the HCL Compass Web server and the administrator does not have Super User privileges on the Compass Web server, the Compass Web administrator can use the OAuth Consumer Management window to approve the provisional consumer key.
You can register an OAuth consumer's secret to create a new consumer key. Use this function when the OAuth consumer does not have an interface to request access to HCL Compass Web.
This section discusses how to use the Collaborative Lifecycle Management (CLM) integrations with the HCL Compass Web client in HCL Compass. These instructions apply only to HCL Compass environments where the Compass OSLCLinks package is applied to your database schema.