Configuring ClearQuest Web
server for Collaborative Lifecycle Management integrations
You must perform several configuration tasks on the ClearQuest® Web server and
the Jazz™ server to enable the
Collaborative Lifecycle Management (CLM) integrations with Rational Team Concert™, Rational® Quality Manager, and Rational DOORS Next Generation.
You must perform the same configuration tasks on two ClearQuest Web servers to allow users
to link records between the two servers.
Overview of OAuth access
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.
Configuring project relationships
After configuring the ClearQuest Web
server for cross-server communication, configure project relationship
links.
Configuring the target server for cross-server communication
You must configure the target OSLC service provider for
cross-server communication back to the ClearQuest Web server to complete configuring ClearQuest Web for a Collaborative
Lifecycle Management integration.
Approving an OAuth consumer key
If an administrator on the Jazz server
is configuring cross-server communication with the ClearQuest Web server and the administrator
does not have Super User privileges on the ClearQuest Web server, the ClearQuest Web administrator can use the
OAuth Consumer Management window to approve the provisional consumer
key.
Registering an OAuth 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 ClearQuest Web, for example, non-Jazz-based
clients (consumers) that want to access OSLC links by using the OAuth
protocol.
Remapping URIs after renaming a CLM server
You must remap Jazz Team Server public URI artifact links
for the Rational solution for Collaborative Lifecycle Management (CLM)
resources after a server rename operation. Specifically, these are
links that are stored in IBM Rational ClearQuest Web server configuration
files and in OSLCLinks records in the ClearQuest user database.