Enterprise Manager Log settings: EM.log - log4j.xml
Originally Published: 2012-10-08
Article Number
Issue
-Maximum Number of Logs to save
-Maximum Log File Size
-Logging Level (Set DEBUG, ERROR, etc)
Resolution
1) Stop Enterprise Manager Service
2) Rename the current EM.log to EM-old.log or other suitable name.
Later, when the EM is restarted a new EM log will be created.
3) Save a back up copy of the Log4j.xml file.
4) Open the Log4j.xml file with Notepad.
Please use Notepad, since other file editors may add formatting data that will corrupt xml files.
5) Edit and save the file.
6) Start the Enterprise Manager Service.
Notes
File is located at ~Enterprise Manager\webapps\root\WEB-INF\classes\log4j.xml
Property values that you may want to change:
?MaxIndex
?Number of rollover files to keep
?MaxFileSize
?File size to reach before rolling over
?Level for logger ?com.tablus?
?Log level (WARN, DEBUG, INFO (default), ERROR, and FATAL)
Related Articles
FIM - Log4j memory leak Number of Views The audit.log is not logging to the proper location defined in the log4j.xml Number of Views How to turn off log4j errors at Thor Xellerate server startup Number of Views Old connector Log4j files not removed in RSA Governance & Lifecycle Number of Views RSA Customer Advisory: Apache Vulnerability Log4j2 CVE-2021-44228 Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide Troubleshooting RSA MFA Agent for Microsoft Windows How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
