I am trying to make an entry for SOAPAppenderPega in the prlog4j2.xml, expecting this to write the log on the configured/specified server over SOAP WS Calls. This is not working. And when I try to check from java to see the available appender, my appender is not getting listed. Where am I going wrong, can someone please help. Is this soap appender pega class proper, I have tried to keep "com.pega.pegarules.priv.util.SOAPAppenderPega" in the configuration, but no luck. I am trying to update the "tomcat/webapps/prweb/WEB-INF/classes/prlog4j2.xml". There are no connectivity issues.
It is Pega 7.3.1. When searched for prlogging.xml in tomcat folder, I could not find any file. I think Pega is no more making use of "prlogging.xml", instead the prlog4j2.xml for logging configurations.
In Pega 731, you dont use the XML files for AES & PDC integration.
Since 717, platform has integrated "dynamic appender". Simply go to designer studio and navigate to systems / settings / PDC, enter your AES or PDC URL and press update. Do not customize logging configuration files
Thanks for clarification WERDA. One more confirmation please, so, the default/OOTB SOAPAppenderPega is no more available to be configured/used by making changes in prlog4j2.xml, and if we want to have such a feature, we need to have our own custom appender instead. Is my understanding right?
BTW - back to your original prlog4j2.xml proposal -- the "SOAP-EVENTS" appender that you defined would not receive messages as the engine explicitly writes to PEGA and ALERT appenders. The "old school" xml based configuration for AES integration called for the alert-soap appender to be chained under the ALERT appender, with a separate ASYNC appender as a buffer. Speaking of buffers, buffersize and blocking do not apply to the SOAP appender; they apply to the Async appender class