This configuration section is aimed for the OSLC Remote Application administrator. It contains the tasks required for completing the configuration of ${local-app-connector}. These tasks however are not explained in detail, as it is not the scope of this guide to provide procedures of all possible products out there being compatible with this connector. Instead, it is expected that readers are familiar with configuring friends, consumers and container associations of their own managing product(s). If this is not the case, please refer to the corresponding official documentation before continuing.

Most configurations ahead require a collaborative work with the ${local-app} administrator who will ask you to:

1. Configure a consumer/friend for ${local-app} in each OSLC Remote Application they require.
2. Register associations for ${local-app} ${term-project-plural} in each OSLC Remote Application container they require.

Additional configuration might be necessary or useful for some specific OSLC Remote Applications, as detailed below.

Configuring IBM Engineering Lifecycle Management

If the OSLC Remote Application is an IBM Engineering Lifecycle Management (ELM) application and ${local-app} team require Global Configurations:

1. Make sure IBM Global Configuration Management (GCM) and ${local-app} applications become friends of each other.
2. Verify that IBM Link Index Provider (LDX) application is installed.
3. Follow the steps described in ${anchor-title-configure-ldx}.

If users require IBM Jazz Reporting Service and/or IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) services:

4. Verify that IBM Lifecycle Query Engine (LQE) application is installed.
5. Follow the steps described in ${anchor-title-configure-lqe}.