Question

3
Replies
427
Views
 Attila Donath (AttilaDonath)
Cognizant
Pega Lead System Architect
Cognizant
CH
AttilaDonath Member since 2016 10 posts
Cognizant
Posted: June 15, 2017
Last activity: July 17, 2017
Posted: 15 Jun 2017 11:07 EDT
Last activity: 17 Jul 2017 4:09 EDT
Closed
Solved

No Application is attached to a service requestor

Hi,

I am using a File Listener to process data. The processor Activity needs to read an Application specific setting (whether CMIS is enabled), but it turned out to be undefined. That's where I noticed that the service requestor doesn't have an Application under System / Operators / Requestors (see attached Requestors.png).

The service package requires authentication (see ServicePackage.png) and the Access Group is linked with a proper, existing application (see AccessGroup.png).

Could you please tell me what could be the problem, why I don't see an Application for the requestor?
How can I start debugging such errors in the future?

Thanks,
Attila

Data Integration
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.

Accepted Solution

Posted: 4 years ago
Posted: 16 Jun 2017 6:04 EDT
Attila Donath (AttilaDonath)
Cognizant
Pega Lead System Architect
Cognizant
CH

The Application field on the above image is empty because the service requestor didn't have any threads when I took the screenshot. However the Application page is still not populated by default for services which turns out to be intentional: https://pdn.pega.com/support-articles/system-page-application-not-setup-rest-service


My solution now is to populate the Application page manually in the Service File's processing prolog by an activity:

see attached screenshots.


Any other ideas or suggestions are welcome.
Posted: 3 years ago
Posted: 29 Jun 2017 4:44 EDT
Attila Donath (AttilaDonath)
Cognizant
Pega Lead System Architect
Cognizant
CH

Hi Jim,


Thank you for your answer. The access group is Application type as far as I understand this concept correctly, see: AccessGroup.png


It seems to me that it is a deliberate decision that Application data page is not populated for services as explained in that support article: https://pdn.pega.com/support-articles/system-page-application-not-setup-rest-service:


The requestor created for listeners and services is of type APP,  the system pages such as pxRequestor, Application, an so on, are kept lightweight and may not contain all the data that one would normally see when user logins to Pega through a browser.