Apps 10 - UPD14
Is anybody aware of a way to setup the middleware to automatically remove ‘old logs files’ generated by the HTTP / MainServer / Integration Services?
Currently we are handling this by manually deleting the old log files but thought I would ask on the community.
+31
Hi
You can setup a log rotation policy using IFS Middleware Server Admin Console.
In the IFS Middleware Server Admin Console, navigate to Main Cluster → Managed Servers and expand the MWS Logging section at the bottom. There you can set the log rotation type to “By time” or “By size”.
If set to by size, then a new file will be created after the file size reaches the value mentioned in “Rotation file size” field.
If set to by time, then a new file will be created according to the values set in “Rotation interval” and “Begin Rotation Time” fields.
The value set for “Files to retain” would ensure only the defined number of log files will be retained, regardless of the rotation type and the older log files will be deleted. “Limit number of retained files” should also be enabled. It is recommended to retain at least 2 weeks of log files in case you need to troubleshoot any issue.
Severity levels define how verbose the logs would be. It is recommended to keep it as Warning, which is the default value, unless you are advised to increase it to troubleshoot a problem. If the log severity level is increased to a value like DEBUG or TRACE, it would show much more details in the log files which could help identify a particular issue, but the logging overhead could cause performance issues in the system.
You can set these values for all the managed servers in both Main and Integration clusters.
Hope this helps!
Hi
You can setup a log rotation policy using IFS Middleware Server Admin Console.
In the IFS Middleware Server Admin Console, navigate to Main Cluster → Managed Servers and expand the MWS Logging section at the bottom. There you can set the log rotation type to “By time” or “By size”.
If set to by size, then a new file will be created after the file size reaches the value mentioned in “Rotation file size” field.
If set to by time, then a new file will be created according to the values set in “Rotation interval” and “Begin Rotation Time”
The value set for “Files to retain” would ensure only the defined number of log files will be retained, regardless of the rotation type and the older log files will be deleted. “Limit number of retained files” should also be enabled. It is recommended to retain at least 2 weeks of log files in case you need to troubleshoot any issue.
Severity levels define how verbose the logs would be. It is recommended to keep it as Warning, which is the default value, unless you are advised to increase it to troubleshoot a problem. If the log severity level is increased to a value like DEBUG or TRACE, it would show much more details in the log files which could help identify a particular issue, but the logging overhead could cause performance issues in the system.
You can set these values for all the managed servers in both Main and Integration clusters.
Hope this helps!
Thank you!
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
