The objective of page is to provide an overview of the ETM TRS Validation including troubleshooting techniques.
ETM provides two TRS Feeds, namely:
ETM Process Resource TRS 2.0 (https://
Jazz Foundation provides the process feeds for the foundation-based applications and contains the project area level information.
If a report doesn’t show the project areas, team areas, timelines and iterations, validating the Process Resources feed would help in determining and/or addressing the problem.
ETM Artifact Resources TRS 2.0 (https://
As the name indicates, ETM provides the artifact resources feed the include the artifacts such as Test Plans, Test Cases, Attributes etc.
If a report doesn’t show the artifacts or attributes, validating the Artifact Resources feed would help in determining and/or addressing the problem
*Note:*
Running a TRS Validation may take a long time to complete and will put additional load on the server.
• We recommend running a validation when server usage is low, such as during a scheduled maintenance window.
• There is no way to stop a validation once it starts except by shutting down the ETM server. After the server is stopped there is no way to resume the validation manually or automatically. Validation must be restarted again by including “Clear cached validation data” option since it will be in an unknown state.
• Validation results are based on the data from when it is started. So, if there are changes performed by the end users after the validation is started, they will be be picked up and validated. Therefore, the validation results may contain false positives
Open the Engineering Test Management Administration page: https://
On the toolbar, click TRS Feed Diagnostics.
In the TRS Feed Diagnostics details page, click on Validate artifacts and configurations
This option is used to verify that resources in the ETM TRS Feed match the resources present in the ETM Repository. Use this option if there are discrepancies reported in the JRS Reports or in cases where there are skipped resources reported in LQE.
This option is used to automatically address the issues, if any, are identified during the validation process. The option is selected by default.
Where there are unresolved issues, you may notice a list of
• Missing or extra artifacts.
• Unknown resource for Selections patch.
• Wrong patch eTag.
• Unexpected artifact added by a patch, etc.
The validation results are appended to the existing validation summary include the duration of the validation execution.
You can view the number of repaired, missing, and extra artifacts in the feed. These artifacts are listed in separate sections.
• If all issues are resolved, then the validation result shows a green check mark.
• If there are discrepancies found that were fixed, then the validation result shows a Yellow Triangle.
• If there are discrepancies to fix, then the validation result shows a red cross.
Note: There are some discrepancies identified in the validation report status that is being worked upon currently. Wiki would be update with more details after a conclusion is reached.
If you see discrepancies in the report after the validation is performed, consider running the validation choosing the option “Clear cached validation data”
Choosing this option when executing the validation would erase the cache data that is recorded during the previous validation which is used during the current validation process.
Cached data is used to improve the TRS Validation performance.
This option is useful in the following scenario:
a) If the application is restarted during the validation which results in unknown validation status.
b) The last validation is executed over 28 days depending on the configuration of ETM Advanced Property “Validation results expire after (days after start)”
c) Validation with “Validate artifacts” and “Resolve problems” reports the error “The validation was cancelled because of an error. For details, check the server log file.” In such cases, it is recommended to execute the validation along with “Clear cached validation data” option. If the issue persists, contact the IBM Support.