/
Configuring the OSLC Connector for Confluence to work with Smartfacts

Configuring the OSLC Connector for Confluence to work with Smartfacts

You have to configure the network connection, the root services, the link types and optionally the association of spaces to OSLC sources.

Install OSLC Connector for Confluence

 

 

1. Network Configuration

There are two options on the network configuration page:

 

image-20250124-080635.png
  1. No SSL
    You chose not to encrypt the communication between Jira and IBM Jazz.

  2. Default Settings
    Just import a self-signed certificate into the system trust store.

    1. Make sure you have imported the public certificate of the IBM Jazz instance into the TrustStore on the Jira machine.

    2. (2) allows you to test if the Jira server can connect to the IBM Jazz instance. The result is shown in (3).

    3. (4) shows the current setting of the path to the TrustStore on the Jira machine. You can change the path and apply the changes by clicking the Apply button.

    4. (5) allows you to have Confluence return an answer under an alternative URL. This is useful when you have a http (no SSL) connection from IBM Jazz to Confluence and want to make sure that the answer from Confluence is provided via an alternative url.

2. Add a Consumer in Smartfacts

  1. Open the Model Warehouse profile from the main menu

  2. Select the "Consumer (Inbound)" tab

  3. Click the "+" button to add a new consumer

  4. Provide a name and a secret. You will need the secret later in Confluence. The consumer key is generated by Smartfacts. Copy it and switch to the Confluence admin area.

3. Add the Smartfacts OSLC rootservices URL in Confluence

  1. In Confluence, navigate to OSLC CONNECTOR FOR CONFLUENCE > Friends Management

  2. Click "Add Root Service Configuration"

    1. Enter a name

    2. Add the Smartfacts root services URL https://[genoslc-base-url]/rootservices.
      If you are not sure what the url is, you can look it up in the Model Warehouse profile of your Smartfacts instance on the Smartfacts tab.

    3. Select "AM" - Architecture Management - as OSLC domain for Smartfacts

    4. Use the consumer key you have copied on the Smartfacts side in step 2.4

    5. Use the same secret as on the Smartfacts side

  3. Having added an OSLC source via (1), you can test via the "Test" button (2) if the source can be reached from the Confluence server. By clicking (2), the addon tries to download the rootservices file and shows a protocol in the Test - log space.

 

image-20250124-080725.png

 

4. Link Type Management

 

image-20250124-080811.png

 

  1. You can add manual Link types, but there is also a Set of default OSLC Link types with which you can start out of the box.

5. Confluence Project Association

 

image-20250124-080957.png

 

  1. A project association between a Confluence project and an OSLC artifact container will simplify the selection of a OSLC target artifact. If you activate associations via (1) the selection of a target artifact will only be possible between your Confluence project and the associated OSLC artifact containers. Ideally you associate only one OSLC artifact container with a Confluence project.

  2. (2) allows to add an association between a Confluence project and an OSLC artifact container, such as a DOORS Next project or a Smartfacts project.

 

Related content