Establishing cross-server communication

Use the server administration interface to establish cross-server communication with other Jazz™ Team Servers that can participate as friends in the Collaborative Application Lifecycle Management (C/ALM ) integration. Use this procedure to add the location information of another Jazz Team Server, create a provisional OAuth consumer key, and send a request to the friend server.

Before you begin

You must set the public URI on each Jazz server that is participating in the C/ALM integrations before performing this procedure.

About this task

To establish cross-server communication:

Procedure

  1. Open the server administration interface as a member of the JazzAdmins group:
    • For IBM® Rational® Team Concert and IBM Rational Requirements Composer, log in to the Admin Web UI and click the Server tab.
    • In IBM Rational Quality Manager, click Admin > Jazz Server Administration.
  2. In the Configuration pane, click Cross-Server Communication.
  3. In the Title field, enter a title to identify a target Jazz Team Server. For example:
    • My Test Server to identify a Rational Quality Manager server.
    • My Requirements Server to identify a Rational Requirements Composer server.
    • My RTC server to identify a Rational Team Concert server.
  4. At the Root Services URI field, enter the URI for the Jazz root services of the server you want to add as a friend.
    • To identify the Jazz root services of a Rational Team Concert or Rational Quality Manager server, use the form https://friend-server:9443/jazz/rootservices. For example, https://rqm-host:9443/jazz/rootservices.
    • Because Rational Requirements Composer uses a fronting server application, the root services path is slightly different. To identify the root services of a Rational Requirements Composer fronting server application, use the form https://rrc-server:9443/rdm/rootservices. For example, https://rrc-host:9443/rdm/rootservices. The fronting server application is layered on the Jazz Team Server and provides additional support for requirements management services. The requirements management services help to implement the Open Services for Lifecycle Collaboration (OSLC ) standard.
  5. In the OAuth Secret and Re-type Secret fields, enter an OAuth secret code phrase to associate with the new OAuth consumer key.
    Note: In this step, you do not enter the key itself; you enter a shorter phrase that will be associated with the key.
  6. Select the Trusted check box. Otherwise, you are asked for authorization when communicating with the other server.
  7. Click Request Access. A provisional OAuth consumer key is added to the list on this page and a request for access approval is sent to the other server. A new entry is added to the Server Friends List.

What to do next

If you have administrator permissions on the target server, follow the Grant access for the provisional key link that is provided at the bottom of the Cross-Server Communication page to navigate to OAuth Consumer Management on the target server and approve the access request; otherwise, work with a member of the administrator group on the target server to get approval for provisional OAuth consumer keys. See Approving access requests.

After you approve the access request, repeat this procedure for the other Jazz Team Servers so that they can access this Jazz Team Server.

The Server Friends List at the bottom of the Cross-Server Communication page lists the servers with which you have established cross-server communication. The Cross-Server Communication page for the Rational Requirements Composer server includes an additional section, Internal Friends List. Rational Requirements Composer uses a fronting server application, and that application has an internal friend relationship with the Rational Requirements Composer Jazz Team Server.


Feedback