This page lists the steps involved in Reproducing ED Issues.
Release | Yes/No |
---|---|
8.3.x |
RDBMS | Yes/No |
---|---|
CSS |
- To perform the below steps you will need the following Relevant input
- Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.
- Deploy the Engineering Dashboard war for the version being used on a Tomcat server: Standalone Engineering Dashboard deployment
- Import the Central Database
Update the name of the central database in the tables of central base by running the following queries on the Central Base:
select * from dss_sites
Query Result123456;1;"sample_central";"";"N/A";"host";"operator";"GKGMIMMIDOCSFNKL";1;5;"2016-04-18 17:56:00.255";"first_central";1;"PostgreSQL";"//localhost:2280/postgres"
In the above query the original name of the users central database is sample_central
update dss_sites set site_name='<new_CB_name>' where site_id= <site_id>
ExampleReplace <new_CB_name> with the restored central database name (following the naming convention) and <site_id> with the siteID returned in the above query. update dss_sites set site_name='c810_1234_asd' where site_id= 123456
Modify the META-INF\context.xml in your deployed tomcat area for the database server and the central database name
- Add a user to access the ED dashboard with the role ROLE_ADMIN (unless the issue is related to specific roles, then you may need to do further configuration as per the issue that is being investigated): User authentication
Activate SQL traces on ED logs using the steps in the page Health Dashboard - Information - How to activate SQL traces on AAD and RestAPI logs
Reload the application from Tomcat.
Navigate to the page where the issue exists.
- From the SQL traces get the query responsible for the value displayed on the AAD