Establishing cross-server communication from CLM

Use the server administration interface to establish cross-server communication between Rational® Requirements Management, Change and Configuration Management, Quality Management and JIRA. Use this procedure to add the location information for the JIRA application, and send a request to the friend application.

Before you begin

After installing the Rational Adapter for JIRA and completing the set up of the adapter, you must create friend relationships between the JIRA server and the servers used by Change and Configuration Management, Quality Management and Requirements Management applications.

If you are integrating with Rational ClearQuest®, see Technote 1580379 for information about establishing friend relationships between Rational ClearQuest projects and the JIRA application.

You might also want to review the project associations that are possible between JIRA and CLM projects to get an idea about what servers to friend. For details, see Using the JIRA adapter.

About this task

Add friend relationships to JIRA to establish cross-server communication with Change and Configuration Management, Quality Management and Requirements Management applications.

Procedure

  1. Point your browser to one of the following URLs using the default context root value:
    1. https://[fully qualified hostname]:[port]/jts/admin Log in to the Rational Requirements Composer server by using an account that has administrator privileges.
    2. https://[fully qualified hostname]:[port]/ccm/admin Log in to the Rational Team Concert server by using an account that has administrator privileges.
    3. https://[fully qualified hostname]:[port]/qm/admin Log in to the Rational Quality Management server by using an account that has administrator privileges.
  2. On the Server Administration page
    • For jts/admin click the Server tab.
    • For ccm/admin click the Application tab.
    • For qm/admin click the Application tab.
  3. In the Communications section, click Friends (Outbound).
  4. At the Friends List, click Add. The Add Friend window opens.
  5. For Name, type the name that you want to use to identify the JIRA friend application, for example JIRA server.
  6. For Root Services URI, type the uniform resource identifier for the JIRA server. For example, http://YourJIRAhostname:8080/rootservices
  7. 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.
  8. Click Create Friend. A confirmation message opens. Click Next to continue.
  9. Configure the OAuth manager for OAuth authentication while creating the friend server. Click Grant access for the provisional key. If you do not have administrator permissions on the targeted application server, work with a member of that administrator group to get approval for provisional OAuth consumer keys.
    Important:
    • If JIRA uses an LDAP user registry, you must add the following JVM Arguments while starting up JIRA: Datlassian.org.osgi.framework.bootdelegation=sun.*, com.sun.*, org.springframework.ldap.core.*
    • If you are using Rational solution for Collaborative Lifecycle Management v3.0.1.0, you must configure OAuth to complete the authentication between JIRA and Jazz™ server entries, see Configuring OAuth authentication.
  10. Log in to JIRA using an account that has administrator privileges, if prompted. Specify a consumer name to remember your OAuth friendship.
  11. In the Authorize Provisional Key window, click Approve and Finish.
  12. Repeat the above steps, if you want to add another friend to the friend list for CLM applications.

Results

From the Jazz application server, you have created one or more friend requests from one or more CLM applications to the JIRA server.

What to do next

Link JIRA project areas to CLM project areas, see Linking between JIRA projects and CLM project areas.


Feedback