Tracing the method Queue-For-Agent
Hello,
I would like to know if we can trace the activity called by the agent.
For more information about my requirement:
I have a service rest that saves information in Pega. Upon failure, I call the method Queue-For-Agent (in order to queue all the requests that failed and then relanch the save later on).
For the Agent, I have linked it to an activity testOHLS:
When I run the activity of the service REST and simulate a failure, I can see in the tracer that the method Queue-For-Agent is called but I do not see the activity related to the agent (testOHLS) being called in the tracer. Is there a way to make sure that the Agent is calling the required activity ?
Thank you in advance for your help,
Mariane
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Incessant Technologies
GB
Hi mariane,
Please find my attachment for steps to follow while tracing the agent.
ThankYou,
Srijith.
Incessant Technologies
GB
To trace the agent activity,you need to open System Management Application(SMA) and then need to select your agent and delay it.when the agent is delayed ,you need to select your requestor session from the requestor menu and then click on trace button within SMA.This will trace the agent activity.
Murex
LB
Thank you Srijith :)
I have opened the SMA, I can see my Agent runnable but the activity linke dto it is generating the below exception:
Please note that my activity is pretty straightforward (obj-open - given a hard coded value - propety set then save and commit)
Any idea what is causing the below error ?
Thank you Srijith :)
I have opened the SMA, I can see my Agent runnable but the activity linke dto it is generating the below exception:
Please note that my activity is pretty straightforward (obj-open - given a hard coded value - propety set then save and commit)
Any idea what is causing the below error ?
Agent CSFW #0: MX-FW-CSFW-Work-Case.testOHLS encountered an execution error. Restarting after delay. Exception at 20161005T163938.275 GMT: com.pega.pegarules.pub.clipboard.ReadOnlyException: ReadOnlyPageOrProperty Param PageDirectoryImpl.getPage reserved page named 'Param' does not exist and cannot be created at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.getPage(AbstractPageDirectory.java:1107) at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.getDirectPage(AbstractPageDirectory.java:731) at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.getDirectPage(ThreadPageDir.java:471) at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.getPage(ThreadPageDir.java:429) at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.getPage(ThreadPageDir.java:421) at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.getPage(PRThreadImpl.java:539) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.getTopPage(PropertyReferenceImpl.java:2169) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.getTopPage(PropertyReferenceImpl.java:2113) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.resolveEmbeddedPages(PropertyReferenceImpl.java:1789) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.resolveEmbeddedPages(PropertyReferenceImpl.java:1722) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.doGetString(PropertyReferenceImpl.java:1476) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.getStringIfPresent(PropertyReferenceImpl.java:1258) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.getStringIfPresent(PropertyReferenceImpl.java:1243) at com.pega.pegarules.data.internal.clipboard.PropertyReferenceImpl.getStringIfPresent(PropertyReferenceImpl.java:1232) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.setupParameters(QueueProcessor.java:706) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:327) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:967) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1266) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:908) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:684) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) at java.lang.Thread.run(Unknown Source)
Thank you :)
Accepted Solution
Incessant Technologies
GB
Hi mariane,
Please find my attachment for steps to follow while tracing the agent.
ThankYou,
Srijith.
Murex
LB
Hello Srijith,
I am trying to trace the activity called by the agent as specifed by your steps.
When clicikng on the 'Tracer' under the Requestor Management, the tracer is not launched, instead a Fail status popup appears as you can see in the below screenshot.
Altough a message 'TracerURL opeartion has been executed successfully' is displayed in the Requestor Management screen
Any ideas if there are some missing configurations that I need to set ?
Thank you,
Mariane
Incessant Technologies
GB
Hello Mariane,
Can you try remote trace option from designer studio tracer with that requestor ID and share the result?
Accenture Services
NL
Hello Mariane,
As you are queueing the Agent using the "Queue-For-Agent" method, you can Keep the mode of the Agent as Advanced. Also,does your requirement need AQM? Probably not, as it will get executed, based on a precondition.
Try this configuration. Hope it works. Please let me know your feedback after trying this.
Thanks,
Jyotirmoy
Murex
LB
Hello Jyotirmoy and Harsha,
Thank you for your replies.
I noticed that the tracer only works on IE and not on Chrome. So I have been using IE to trace the agents sucessfully.
Thank you,
Mariane
