Where to access and verify Async Loaded Data Page?
We have configured an agent activity to do Load-DataPage (node level) at off hours as the source service has a heavy response.
I can verify from logs and DB that agent activity ran and performed the processing but I have a few questions below.
Firstly, I am not able to trace the agent through SMA as after 10 seconds or so tracer says 'no session found for requestor'. Is ADP load D_Page not traceable?
Secondly, D_Page doesn't show up immediately under Node level pages unless I run a test activity later with D_Page as a step page. Is it possible to access or view the original background thread to check for D_Page creation without the need of running a test activity?
Thanks
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
Pegasystems Inc.
US
The data page is loaded asynchronously in the background using a new requestor thread and will not be visible in the clipboard until you refer it from your workflow.
You should be able to trace ADP events via tracer. And you should be able to delay and trace the agent requestor. Depending on the Pega version you are on, you can trace and manage agents directly from Designer Studio here :- System > Operations > Agent Management
As shared above you can enable loggers. Please find few of the loggers for Data Page related issues below:
- ADP Life cycle
- com.pega.TRACE.adp_lifecycle
- Data Page life cycle
- com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory
- com.pega.pegarules.session.internal.mgmt.base.handler.AbstractPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler. EditableDataPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandlerForNode
Note: These loggers have to be used with caution because they could turn out to be highly verbose in the logs. It is advised that you revert the logging levels after debugging.
Pegasystems Inc.
IN
Hi,
You can enable these Debug loggers to check the Data page loading in logs.
com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl
com.pega.TRACE.adp_lifecycle
com.pega.TRACE.datapage_lifecycle
Accepted Solution
Pegasystems Inc.
US
The data page is loaded asynchronously in the background using a new requestor thread and will not be visible in the clipboard until you refer it from your workflow.
You should be able to trace ADP events via tracer. And you should be able to delay and trace the agent requestor. Depending on the Pega version you are on, you can trace and manage agents directly from Designer Studio here :- System > Operations > Agent Management
As shared above you can enable loggers. Please find few of the loggers for Data Page related issues below:
- ADP Life cycle
- com.pega.TRACE.adp_lifecycle
- Data Page life cycle
- com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory
- com.pega.pegarules.session.internal.mgmt.base.handler.AbstractPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler. EditableDataPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandler
- com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandlerForNode
Note: These loggers have to be used with caution because they could turn out to be highly verbose in the logs. It is advised that you revert the logging levels after debugging.