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.

Application

Rootservices Location

Approval Location

Notes

DOORS Next

{DNG_HOST}/rm/rootservices

{JTS_HOST}/jts/admin

Create to RM but approve in JTS

ETM

{ETM_HOST}/qm/rootservices

{ETM_HOST}/qm/admin

 

EWM

{EWM_HOST}/ccm/rootservices

{EWM_HOST}/ccm/admin

 

GCM

{GCM_HOST}/gc/rootservices

{JTS_HOST}/jts/admin

Create to GC but approve in JTS

Polarion

{Polarion_HOST}/polarion/oslc/rootservices

{Polarion_HOST}/polarion/oslc/services/oauth/approveKey

Jira

{Jira_HOST}/rest/oslc/1.0/rootservices

{Jira_HOST}/plugins/servlet/oslc/consumer

Confluence

{Confluence_HOST}/rest/oslc-connect/1.0/rootservices

{Confluence_HOST}/plugins/oslc-connect/consumers.action

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

Application’s URI

Tool admin

Notes

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.