Network Topology

When it comes to OSLC, not all nowadays complex architectures may allow communication between two different applications/servers. There are some mandatory configurations (plus some recommended ones) that must be followed to enable OSLC discovery and linking. Please refer to the OSLC Architecture Recommendations page to know the minimal requirements and supported architectures, by OSLC, before continuing with some Jira-specific considerations.

Jira Considerations

Once OSLC requirements are met, make sure of the following for the Jira instance and the OSLC Remote Application:

• They both use the same transfer protocol (HTTPS).
• They do NOT share the same Fully Qualified Domain Name (FQDN) or they have a different port^[1].

Also consider that the Jira server must support the SSL version TLSv1 if Global Configurations will be used with either IBM Engineering Requirements Management DOORS Next or IBM Engineering Test Management.

Last but not least, consider the following for clustered Jira Software Data Center instances:

• Sessions affinity, or sticky sessions, are mandatory. ^[2]
• Traffic distribution or traffic shaping is not support. ^[1]

^[1] This is a known limitation, check Known Limitations section for details. ^[2] This is a known requirement of Jira clustered instances.