Idea

1
Replies
249
Views
Felipe Kohn (KOHNF)
PEGA
Director, Technical Solutions
Pegasystems Inc.
US
KOHNF Member since 2009 1 post
PEGA
Posted: March 20, 2017
Last activity: March 21, 2017
Posted: 20 Mar 2017 14:55 EDT
Last activity: 21 Mar 2017 8:23 EDT

Triaging issues related to SystemName- >Requestor- >AccessGroup- >Application failures

Today when one of the following conditions occur (with respect to unauthenticated browser requestors), very little, if any, information is written to the logs.

  • The SystemName defined via DSS or prconfig.xml does not exist – impacts startup of PRPC
  • The Browser Requestor for SystemName does not exist – impacts unauthenticated browser sessions (i.e., signon)
  • The AccessGroup pointed to by the SystemName:Browser instance does not exist – impacts unauthenticated browser sessions (i.e., signon)
  • The Application pointed to by the AccessGroup referenced on SystemName:Browser does not exist – impacts unauthenticated browser sessions (i.e., signon)
  • A similar set of errors occur with the other requestors of APP, BATCH and PORTAL

Can we prioritize a product enhancement to generate an error message in the PegaRULES.log which details which of the above is missing or invalid?

***Updated by moderator: Lochan to add enhancement request ID and SR Exists group tag***

Support Case Exists