Hi Ashok,
I agree to your point in opening up an idea and support case. But this might be required by most of the organizations, especially if its banking and insurance sector.
Reason:
If the Admin UI is upgraded or re-installed, the tasks which is captured and stored in the derby DB is lost and hence there is no record of who did what and a fresh Derby DB store is created.
Risk:
Losing track of tasks performed, unable to identify the risk involved.
Workaround and obstacles:
Yes, as a work around we could connect this to some SIEM tool to capture the tasks from the store, but that would again be customized, as we need to share credentials and other details with a different team. However, if we could do this on our own, either by exporting to external DB or LDAP or copy and move it to different directory manually.
===========================================================================================
As you suggested, if i have to export to an external DB( RDBMS SQL client in this case) what are the things, I should be considering to create an external DB, what would be the structure of the schema that should be created.