Avoid restarting the server for configuration change to take effect

[kmcnulty1]

Is there a way to make a change to a configuration file and THEN AVOID restarting the server for the change to take effect. I seem to be able to make the change I want by changing the configuration file and then restarting the server but I am hoping to avoid restarting the server in production because, well... It becomes a huge production to do that. It is for SASPrincipalServices-log4j. I'm just redirecting the log it creates to a different location.

[Kalind_Patel · Accepted solution]

Unfortunately, 

Changing a log file location requires SAS Services to be restarted, 

Only following changes can be done in logging configuration via SAS Web Admin Console (by using Dynamic Logging Changes), without restarting Services:

1. Change the logging levels (Increase or decrease log details)
2. Logging categories addition

For any changes in Log4j configuration file, you must restart the services to make the change in effect, and your requirement can only be fulfilled by modifying Log4j file:

Task	Log4j Configuration File	Dynamic Logging Changes
Change the logging levels.
Add a logging category.
Changes persist after web application server restarts.
Add or change an appender to log to console, file, socket, or ARM.
Change a log filename or location.
Change the layout pattern for the log message.
Track user logons. You can monitor usage patterns by logging activity for SAS web application logons.

Refer this document for more information: 
https://documentation.sas.com/?docsetId=bimtag&docsetTarget=p0qy7oulxf2ot7n1bcavt6difgu3.htm&docsetV...

[kmcnulty1]

Also SAS support recommended using Symbolic Links instead to move my log files to another location to avoid changing the configuration file altogether.