What Motivates You to Participate Here in the PSC?
Reply posted on August 23, 2019 by fredgoldbach
You are correct that I was using the-DNodeType=Universal. I was able to change that as you suggested and restarted. The Cassandra error went away. I'm working with my networking folks regarding the firewall for port 9042.
Reply posted on August 22, 2019 by KevinZheng_GCSPega
I see, are you running only OOTB PRAsyncTopic? It is the mechanism for all background agent processes, I can see some potential impact as messages on the topic are not shared across JVMs. I would run a comparative study with both configuration, that is...
Reply posted on August 22, 2019 by MadhusudanS9253
Thanks all for your reply. I raised SR and got the fix. We need to add below configuration in BIX-prconfig.xml to stop this process to start streaming service. <env name="asyncExecutor/enable" value="false" />
Reply posted on August 22, 2019 by WaikeiKwok_GCSPega
Looking at Pega 8 code, I think we use PushbackReader API to confirm that the stream is completed written before processing. https://docs.oracle.com/javase/8/docs/api/java/io/PushbackReader.html
Reply posted on August 22, 2019 by ChrisKoylPega
Hi, For general SSO configurations you don't need to change anything within our the deployment files. For example using SAML Authentication requires no changes to the deployments. If you were to use container managed authentication with Kerberos...
Reply posted on August 22, 2019 by PaulGentile_GCSPega
You can certainly try: Owning Ruleset: Pega-Engine Purpose: prconfig/HTTP/SetSecureCookie/default Value: true
Reply posted on August 22, 2019 by Vikash KarnPega
It uses pxresolvedtimestamp property to qualify any work object for purge based on the value you have given (work object older than) in the wizard. So when you are setting the pyworkstatus with your custom value then this property(pxresolvedtimestamp)...