PRPC 7.1.8 , JMS MDB Listener
We have a jms listener that takes some information and then is expected to augment that information.
Some of the info that we need to get is only available in the pxRequestor page, however all attempts to access data in the pxRequestor come back blank.
Things like; pxRequestor.pxReqServer , pxRequestor.pxReqServerPort , pxRequestor.pxAlertSessionCount
They all come back empty when the activity is called via a JMS MDB Listener rule.
Accepted Solution
Pegasystems Inc.
CA
Pegasystems Inc.
US
Make sure your MDB runs in the requestor context that has the access to system pages. For example, you can configure MDB to run authenticated and make sure the user used for authentication has the access to those system pages.
Pegasystems Inc.
CA
This is expected. The requestor created for listeners and services is of type APP. For this requestor type, the system pages such as pxRequestor, Application, etc. are kept lightweight and may not contain all the data that you would normally see when you login to Pega through a browser.
Rulesware LLC
CA
Hmm, any idea how I could get that information?
Pegasystems Inc.
CA
Could you explain your use-case a bit. What do you intend to do with the server host name and port?
Rulesware LLC
CA
We are calling a java libary / codeset . The code set needs to know the host and port, because it needs to perform a naming lookup from the web application container, in order to use a service provided by the container.
Accepted Solution
Pegasystems Inc.
CA
Joseph, the properties pxReqServer and pxReqServerPort only get populated when HTTP-based requests are made into Pega. This means all requests made to Pega via the browser or through calls made to Pega SOAP/HTTP/REST services. That's why you don't find them populated in case of JMS services. I can't think of any workarounds at this point. Let's see if anyone here has any ideas.
Joseph, the properties pxReqServer and pxReqServerPort only get populated when HTTP-based requests are made into Pega. This means all requests made to Pega via the browser or through calls made to Pega SOAP/HTTP/REST services. That's why you don't find them populated in case of JMS services. I can't think of any workarounds at this point. Let's see if anyone here has any ideas.