Arnab Chakraborty (ArnabC0883)

ArnabC0883 Member since 2019 1 post
Posted: October 9, 2019
Last activity: December 9, 2019
Posted: 9 Oct 2019 3:08 EDT
Last activity: 9 Dec 2019 7:15 EST

AsyncProcessor requestor type issue

We have multiple pega applications running in the same instance where each of the applications are handled by different teams. We have created a Job Scheduler and a Queue Processor in one of our application to perform some daily work. The issue we faced was we could not find the JS and QP in the admin studio and they were also not running. While debugging the issue, we found that the PRPC:AsyncProcesssor accessgroup referred in the AsyncProcessor requestor type, was not finding the job scheduler and queue processir created in our application. After checking some previous posts in pega community, we created an umbrella access group that includes all the applications which use any JS or QP to perform tasks. We added this access group in the AsyncProcessor requestor type and made it the default one. Though this change fixed our issue but we may face possible performance related issues in future since we always have to maintain and update new applications running JS or QP. We also need to update the umbrella access group in case there are any new rulesets added or deleted. Along with this, security might be a concern as we are adding all available applications, which are entirely different from one another and managed by different teams. So, we wanted to know if there is any viable solution present which will reduce or nullify these risks but also perform the intended task by running all available job schedulers and queue processors.

Enterprise Application Development Dev/Designer Studio
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.