Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
False
-
-
---
-
---
-
Sprint 207 AMM, AMM Sprint 208, Sprint 209 AMM
Description
There are 2 aspects to this task
1. To investigate how to retrieve data from the GraphDB using a REST API
1.1 See if we can reuse the API's that were developed for the Dynamic Reports work (started in 2017).
Findings:
The API's are incomplete, those implemented need to be refactored as there are some basic problems with them (using POST calls when GET should be used,
counter-intuitive endpoint paths, etc.)
This solution relies heavily on the using Forge add-ons to the Wildfly/EAP Server.
Which is problematic as we ultimately want MTA to be running on Quarkus, which does not support CDI portable extensions.
2. Investigate how a single GraphDB could store the MTA analysis data for all of the Applications within the Application Inventory.
Only the most recent analysis for each Application would have to be stored.
There are no constraints regarding the process via which the Graph DB is updated (either directly by MTA, or via an asynchronous process then updates the central GraphDB with data originating from each instance of a Graph DB generated by individual Executor pods).
A related (but slightly out of date) the requirements document is here.