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 ^[1]. This consumer must be trusted and bound to the TRS Functional User.

A functional user is a ${local-app} user which is associated with a consumer. Every time an external application uses that consumer to access ${local-app}, the functional user's access rights are granted to it; in fact, from the perspective of ${local-app}, no external application is accessing it but the functional user only. In other words, the external application accesses ${local-app} 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 ${local-app}, 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 ^[2]. Applications mentioned above require to be in constant communication with ${local-app} (due to the TRS specification); in other words, they require an automatic access (no person behind to login) to ${local-app}. 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 ${local-app} 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 ^[3].

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

1. Follow the steps below in the Assigning Tracked Resource Set Functional User procedure to designate a ${local-app} user to be the TRS Functional User.
2. Depending on the feature/application required, follow the steps of the following sections Global Configurations and/or Reporting Services to bind the corresponding consumer with the TRS Functional User.

Assigning Tracked Resource Set Functional User

As stated above, choosing the right user is very important because bound consumer(s) will have the same credentials to consult ${local-app} information ^[2]. Make sure this user is granted with the permission required to access the OSLC-enabled projects that need to be exposed to the consuming applications before continuing.

1. Locate the TRS Functional User section and click the Assign a TRS functional user link.
2. In the displayed combo, type the first words or the complete name of the user you are looking for, this will display a panel below with matching user names.
3. Select the appropriate match from the panel and click the Assign button.

That's it, the selected user is now the TRS functional user and a warning message will invite you to bind at least one consumer to it ^[4] (following sections take care of that). If in the future you need to change the TRS functional user, you just need to click the Change button to display the combo again and repeat the steps to select another user. Be aware that doing so will require to repair the TRS feeds (if they are not empty). In this same latter scenario, after the TRS functional user is changed, repair warning messages will be displayed in the TRS feeds area until they got repaired ^[2]. To remove the functional user, you just need to click the Remove button.