We are migrating from WAS to Tomcat in a cost savings move. In WAS, we have prconfig.xml and prlogging.xml externalized from the ear file in a separate directory. The location is defined in the WAS configuration. In the install manual for PRPC Tomcat/Oracle I don't see any information on how to externalize these files.
Can this be done in Tomcat? If so, what config file needs to be updated and how? (Tomcat neophyte...)
***Edited by moderator, Maryrita: moved to Product Support from Applications***
***Edited by Moderator Marissa to update categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
MarkH960. To protect against future upgrades of Pega, you can also externalize access to prconfig.xml and prlogging.xml like you did within WAS. My assumption is you are using 7.1.x (I believe it will also work in 7.x but I have not tested it). Of course, with an upgrade of Pega you would still want to validate the differences in XML files to make sure you are safe that way. But like PaulGentile_GCS states, it is, by default auto expanded (usually) by Tomcat and accessible within the webapps directory of tomcat installation
With those caveats out of the way, and if you still want to externalize, I believe the configuration explanation (from System Administrator Specialist online course 7.1) is as follows,
prlogging.xml can be externalized by placing this file in the directory that is defined by the JVM System property "user.home"
prconfig.xml can be externalized by placing this file in a directory that is defined by the JVM System property, "pegarules.config"
As per the installation guide, you are advised (by Apache Tomcat) to create a custom script setEnv.sh where you can append the abovementioned JVM system properties to the JAVA_OPTS environment variable. Also ensure that the user under which Tomcat server runs has read/write/execute permission to the server filesystem <path> above.
Thanks all for the replies. As our Middleware team wants to do a repackage/redeploy rather than let us update the file in the war folder directly, the information on externalizing is very helpful. Thanks again.