Configuring Consumers for TRS

To reach the TRS configuration page, log in as an administrator and navigate to the administration interface at https://<secollab_host_name>:<port>/secollab/web/clm/admin. Then, locate and select the Tracked Resource Set section.

When either Global Configurations or IBM Jazz Reporting Service/IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) are required, a special type of consumer needs to be configured to enable Tracked Resource Sets (TRS) consumption. This consumer must be trusted and bound to the TRS Functional User.

A functional user is a SECollab user which is associated with a consumer. Every time an external application uses that consumer to access SECollab, the functional user's access rights are granted to it; in fact, from the perspective of SECollab, no external application is accessing it but the functional user only. In other words, the external application accesses SECollab on behalf of the consumer functional user. This contrasts with regular consumers where no functional user is associated: when their remote applications try to access a resource, a pop-up window is opened in the external application to let the person login into SECollab, so the access rights of the logged-in user are the ones granted to the remote application during that session.

Now, the TRS Functional User is called that way because it is the one used to build and access the TRS Feeds this application provides. Applications mentioned above require to be in constant communication with SECollab (due to the TRS specification); in other words, they require an automatic access (no person behind to login) to SECollab. This is where the functional user comes to play: by associating the Tracked Resource Set functional user to the consumer these applications use, they can access SECollab without requiring a person to login in the middle of the process, the consumer will just use the same credentials as the functional user and this is why choosing it is very important.

Summarizing, when either Global Configurations or IBM Jazz Reporting Service/ENI are required, these are the things to do:

Available TRS Feeds

SECollab exposes the following TRS 2.0 feeds:

Global Configurations

If Global Configurations are needed, you need to:

  1. Make sure SECollab and IBM Global Configuration Management applications become friends of each other.
  2. Confirm with IBM Engineering Lifecycle Management administrators that IBM Link Index Provider (LDX) application is installed in their instance.
  3. Register a consumer bound to the TRS functional user for LDX application. This is done by following the Registering a Consumer procedure with following data:
    FieldValue
    NameA name of your choice, e.g. LDX
    KeyLeave it empty, system will create a key for you.
    SecretWhatever you want that you don't forget.
    ConfirmationThe same as Secret field.
    Functional UserThe User selected for TRS interactions.
    Trustedchecked
  4. Ask IBM Engineering Lifecycle Management administrator to register a new data source for each required SECollab feed using the above LDX consumer credentials.

The IBM Link Index Provider administrator can follow the IBM Link Index Provider (LDX) Integration topic to register the required feeds.

Reporting Services

If IBM Jazz Reporting Service and/or IBM Engineering Lifecycle Optimization - Engineering Insights are required, you need to:

  1. Confirm with IBM Engineering Lifecycle Management administrators that IBM Lifecycle Query Engine (LQE) application is installed in their instance.
  2. Register a consumer bound to the TRS functional user for LQE application. This is done by following the Registering a Consumer procedure with following data:
    FieldValue
    NameA name of your choice, e.g. LQE
    KeyLeave it empty, system will create a key for you.
    SecretWhatever you want that you don't forget.
    ConfirmationThe same as Secret field.
    Functional UserThe User selected for TRS interactions.
    Trustedchecked
  3. Ask IBM Lifecycle Query Engine administrator to register a new data source for each required SECollab feed using the above LQE consumer credentials.

The IBM Lifecycle Query Engine administrator can follow the IBM Lifecycle Query Engine (LQE) Integration topic to register the required feeds.

After configuring LQE, you may also need to perform LQE Access Control Configuration to control which ELM users can access SECollab content through LQE.