Installing

Prerequisites

Before starting, make sure you have all of this:

• The OSLC Connect for Jira app component ^[1].
• An instance of the Jira Software Data Center with a supported topology, remarkably:
  • The Jira instance uses the same transfer protocol (HTTPS) as the OSLC Remote Application ^{[2], [3], [4]}.
  • The Fully Qualified Domain Name (FQDN) of the server hosting Jira must be different from the server hosting the OSLC Remote Application or they must use a different port ^[5].

Procedure

Follow the steps described in the official Jira documentation. If everything went ok, you will see the Installed and ready to go! dialog with following data:

OSLC Connect for Jira <version>

by SodiusWillert

This app has been installed. If you need help getting started, click the link to the app documentation from the Manage apps screen.

At this point, you should see the OSLC Connect for Jira app listed on the User-installed apps section in the Manage apps page. Another way to validate you completed this process successfully is to refresh the current page (Manage apps page) and a new OSLC Connect section should appear on the left panel below the ATLASSIAN MARKETPLACE section.

^[1] The com.sodius.oslc.app.jira.server-<version>.jar file. ^[2] This is required to eventually create Collaboration Links between both applications. ^[3] If you are installing the connector on a Jira Data Center instance, this rule applies only for the load balancer/reverse proxy; not for individual nodes. ^[4] If Global Configurations will be used with either IBM Engineering Requirements Management DOORS Next or IBM Engineering Test Management, Jira server must support the SSL version TLSv1. ^[5] This is a known limitation of Jira, check Known Limitations section for details.