In order to simplify your deployment of your environment, planning it ahead is key.

In this article, we will focus on preparing a few simple data on the different servers offering OSLC services that you will want to connect to each other.

Mapping your Applications

As seen in the introductory article, Enabling Lifecycle Collaboration with OSLC, applications need to request authorization to use a Friend application’s data and get it granted. This will be the next step of this journey.

Typical Friends created from Jira with their rootservice location, and approval location.


Rootservices Location

Approval Location





Create to RM but approve in JTS












Create to GC but approve in JTS










You should only connect the applications you intend to collaborate with.

Start planning your deployment

Prepare a table similar to the below with the applications you wish to connect (applications may differ, lines have been added as an example).

This will help you make sure you have access to the right people with the right permissions to get the next steps of this journey done in a timely manner.


Application’s URI

Tool admin


ie. DOORS Next

ie. xxx

ie. xxx

Remember to approve in JTS

ie. ETM


ie. EWM


ie. GCM

Remember to approve in JTS

ie. Polarion

ie. Jira

This URL is visible in the Consumer’s administration panel

ie. Confluence

Once done, you are ready and can proceed with configuring Friends.