Stéphan VERDIER
Director of the Data Management Division at KWANZEO - Paris / FR
Asked a question last year
How to see the queries generated in the searches and the queries that display in the collections when the user is using the application ?
Stephanie FourrierSEMARCHY TEAMHead of support at SemarchyHi Stéphan,
from the xDM Configuration menu, you can
- set to TRACE the following Logging Configuration:
log4j.logger.org.springframework.jdbc.core.JdbcTemplate=TRACE
- then make sure that the PDE appender is set for the root logger (default):
log4j.rootLogger=INFO, PDE
- and set the PDE appender Threshold to TRACE, so that it can catch TRACE logs:
log4j.appender.PDE.Threshold=TRACE
- save this Logging Configuration:
Sample Logging Configuration - get ready from the UI screen so that you just have to refresh the page you want to analyze
- make appear the Error Log (PDE log) and flush its content:
Flush Error Log content - refresh the UI screen you want to analyze (browser refresh is enough)
- export the Error Log right away
Export Error Log - restore the Logging Configuration:
Restore Logging Configuration - find the appropriate query from the exported Error Log
I hope this helps!
Best regards,
Stéphanie.
Stéphan VERDIER last yearThis works for searches but not for the query used in the collection.Stephanie Fourrier SEMARCHY TEAMlast yearI'm surprised because I tested before writing this answer. The collection queries look like an embedded query with "from GD_xxx" if the collection is displayed on a golden Business View. Don't hesitate to open a support issue with an export of your model as well as the collection you want to test and the exported PDE log if you don't want to share details on community.
How to see the queries generated in the searches and the queries that display in the collections when the user is using the application ?
Stephanie FourrierSEMARCHY TEAM
Head of support at Semarchy
Hi Stéphan,
from the xDM Configuration menu, you can
- set to TRACE the following Logging Configuration:
log4j.logger.org.springframework.jdbc.core.JdbcTemplate=TRACE- then make sure that the PDE appender is set for the root logger (default):
log4j.rootLogger=INFO, PDE- and set the PDE appender Threshold to TRACE, so that it can catch TRACE logs:
log4j.appender.PDE.Threshold=TRACE- save this Logging Configuration:
- get ready from the UI screen so that you just have to refresh the page you want to analyze
- make appear the Error Log (PDE log) and flush its content:
- refresh the UI screen you want to analyze (browser refresh is enough)
- export the Error Log right away
- restore the Logging Configuration:
- find the appropriate query from the exported Error Log
I hope this helps!
Best regards,
Stéphanie.
Stéphan VERDIER
last year
This works for searches but not for the query used in the collection.
Stephanie Fourrier SEMARCHY TEAM
last year
I'm surprised because I tested before writing this answer. The collection queries look like an embedded query with "from GD_xxx" if the collection is displayed on a golden Business View. Don't hesitate to open a support issue with an export of your model as well as the collection you want to test and the exported PDE log if you don't want to share details on community.