Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to identify which files are modified during runtime operations

Suggest edit Updated on September 13, 2021

Summary

A system administrator asks:

We have a very restricted production environment where most files are locked down against change.

Can you identify what files are created or changed at runtime, so we can determine if these are audit exceptions to our standard environment?



 

Suggested Approach

The pegarules.xml file can contain a setting named WebRootReadOnly; if not mentioned, it defaults to "false." 

Update the pegarules.xml file to change this setting to "true" to cause Process Commander to write to directories (except for those in of the EAR file, for deployment) within the work directory provided by the servlet container.  This container holds the Java, exploded help file, source export directory, upload files, etc. 

In addition, examine the contents of the PRWebTmp and PRTemp directories. 

Review these directories to see what files and directories are created.  This will give you a sense of what is being created as your applications run   It is difficult to supply a complete answer or list of files, because the actual files vary depending on what the application does.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us