Question
Externalization of prconfig/prlogging xml files is no longer working after upgrade to v7.3.x
Hello,
We recently upgraded from v7.1.8 to v7.3.1, and have found that the JVM arguments/JAVA_OPTS that have worked in the past to utilize external config files, are no longer working as expected. PEGA logs are no longer being written to the specified locations within prlogging.xml file, and the 'pegatmp' directory defined in prconfig.xml remains empty. How do we get these args/JAVA_OPTS working again, as we had before with v7.1.8?
Example of -D JAVA_OPTS that worked as expected in lower version (v7.1.8):
JAVA_OPTS="$JAVA_OPTS -Dpegarules.logging.configuration=/opt/projects/pega/prlogging.xml"
JAVA_OPTS="$JAVA_OPTS -Dpegarules.config=/opt/projects/pega/prconfig.xml"
***Edited by Moderator Marissa to update categories; add SR Details***
Prlogging.xml is probably not working because it's no longer used as of 7.3. The new file is prlog4j2.xml and you will need to customize and externalize this instead (do not just copy the contents from your existing prlogging.xml file, this will not work).
As for prconfig.xml, it sounds like you believe it's not being used because that is where you have defined the pega temp directory and nothing is being written there. What application server is in use? There should be another area to specify where the Pega temp directory is. (For example, in context.xml for Tomcat)