How to configure Rational ClearQuest web with the Rational Lifecycle Integration Adapters for HP ALM and JIRA

Before you begin
You must establish cross-server communication between the HP ALM server and the Rational ClearQuest web server before performing this procedure.

3. View the Provisional Keys section for new requests.

4. Locate the consumer key requested by the HP ALM server and select Approve.

Before you begin
After approving an access request from the Rational Adapter for HP ALM, you create friend relationships between the Rational Adapter for HP ALM, the HP ALM server, and the ClearQuest web server.

a. For Title, type the name that you want to use to identify the HP ALM friend application, for example HP ALM server.

b. For Root Services URI, type the uniform resource identifier for the HP ALM server. To find the URI, click the Help icon in the Rational Adapter for HP ALM title bar.

c. In the OAuth Secret and Re-type Secret fields, enter an OAuth secret code phrase to associate with the new OAuth consumer key. This string can contain one or more words and special characters, and cannot exceed 50 characters. This string is never displayed in the user interface, and you do not enter this string again. This string, also called an OAuth consumer secret, acts as a password to access the friend server.

d. Select the Trusted check box. Trusted consumers can share authorization with other trusted consumers and do not require user approval to access data.

e. Click Request Access. A provisional key is requested on the target server and the access information is added to the Server Friends List section of the page. A new entry is added to the Authorize Provisional Key section.

f. Authorize the provisional OAuth consumer key by clicking Grant access for the provisional key.

g. Record the provisional key value. If you have administrator privileges on the target server, you can log on and approve the request. Otherwise, work with a member of that administrator group to get approval for the provisional OAuth consumer key. You might need to provide the provisional key value to the target server administrator.

Before you begin
You must establish cross-server communication and approve OAuth access requests before performing this procedure. Ensure that your web browser preferences are not set to block pop-ups.

Before you begin
After installing the Rational Adapter for JIRA and completing the adapter set up, you must establish links between the Rational ClearQuest web server and the JIRA server.

1. Point your browser to the Rational ClearQuest web server. Typically, the URL is https://<fully qualified hostname>/cqweb. Log in to the Rational ClearQuest web server by using a ClearQuest account that has administrator privileges.

2. Click Site Administration > Cross-Server Communication on the ClearQuest web toolbar. The Cross-Server Communication window opens.

3. Specify the requested information about the target JIRA server with which you want to establish communication:

a. In the Title field, enter a title to identify a target server. For example, JIRA Adapter Server to identify a Rational JIRA Adapter server.

b. In the Root Services URI field, enter the URI for the JIRA server root services. Typically, the URI is https://<fully qualified hostname>:<port>/jira/rest/oslc/latest/rootservices.

c. In the OAuth Secret and Re-type Secret fields, enter an OAuth secret code phrase to associate with the new OAuth consumer key. This string can contain one or more words and special characters, and cannot exceed 50 characters. This string is never displayed in the user interface, and you do not enter this string again. This string, also called an OAuth consumer secret, acts as a password to access the friend server.

d. Optional: Select the Trusted check box. Trusted consumers can share authorization with other trusted consumers and do not require user approval to access data.


Attention: For external products or web sites, it is a best practice to clear the Trusted check box.

e. Click Request Access. A provisional key is requested on the JIRA server. Log in with your JIRA credentials, if prompted. Specify a consumer name to remember your OAuth friendship.

f. In the Authorize Provisional Key window, click Approve and Finish. The access information is added to the Server Friends List section of the page. A new entry is added to the Authorize Provisional Key section.

Results

From the ClearQuest web server, you have added a friend to the JIRA server.