Connecting to the Rational solution for Collaborative Lifecycle Management application server

Integrating : Focal Point® and the Rational solution for Collaborative Lifecycle Management : Setting up the integration for Focal Point® and Rational solution for Collaborative Lifecycle Management applications : Configuring Focal Point® as a consumer in CLM applications : Connecting to the Rational solution for Collaborative Lifecycle Management application server

If you are an global administrator, you can set up the integration with the Rational solution for Collaborative Lifecycle Management (CLM) application servers. For Focal Point^® and the CLM applications to communicate, you must establish an OAuth key for each application to access the servers. Also, you must create friend relationships to manage the list of cooperating servers.

Before you begin

▪ A CLM application administrator must create a consumer key in each CLM application for Focal Point^®. For information, see Registering Focal Point^® as an inbound consumer in a CLM application.

▪ You must have valid user credentials for the CLM application.

Remember: If you rename the Rational solution for CLM server, you must change the server name in Focal Point^® also. After renaming the Rational solution for CLM server, clear the Focal Point^® cache (click Advanced > Caches > Clear All Caches), rename the server, and clear the cache again.

Procedure

1 From a CLM application administrator, obtain the user credentials and the consumer key and consumer secret that are configured for Focal Point^®.

2 In Focal Point^®, click Application > Friends (Outbound).

3 Click the Add friend icon

The Add Friend window appears, where you add the CLM application details:

4 Specify a name for the connection. For example:

RTC1@example.com

RRC1@example.com

5 Specify the application root services URL. For example:

Connecting to	Root services URL
Change and Configuration Management application, version 2 (all releases)	https://<hostname>:<portnumber>/jazz/rootservices
Change and Configuration Management application, version 3 (all releases)	https://<hostname>:<portnumber>/ccm/rootservices
Requirements Management application, version 3	https://<hostname>:<portnumber>/rm/rootservices

Note If the hostname or port number of the Rational solution for CLM applications changes, you must update the Root Services URL. When you update the root services URL, all the links that pointed to the old URL updates to the new one.

6 In Security Type, select OAuth Consumer Key and specify the consumer key that was created for Focal Point^® in the CLM application server. The consumer key is formatted like this:

670db08a94654b559ae87545a8ac5715

Specify the consumer secret in the OAuth Secret field. For example:

FP2

7 For OSLC applications, select OSLC, and then specify the OSLC namespace URI, link namespace URI, and domain name. For example, URIs for a Requirements Management application are these:

OSLC Name Space URI:

http://open-services.net/ns/rm/1.0/

OSLC Link Name Space URI:

http://open-services.net/ns/rm#

Note Specifying the OSLC details is optional for IBM Rational Team Concert and IBM Rational Quality Manager.

8 Click Test Connection.

The first time you test the connection, you must log on to the CLM application.

The results of the test are displayed in the Add OAuth Friend window.

9 Click Save.

What to do next

Add an attribute for storing links to artifacts in the CLM application. For information, see Adding and configuring attributes for storing links to artifacts in the Rational solution for Collaborative Lifecycle Management applications.

Fetching information from CLM artifacts