Business logic server (TcServer) logging levels

Administrators can use event logs to monitor system activity and troubleshoot session issues. Administrators can set startup logging levels for all business logic servers (TcServers) and can dynamically set session logging levels for a single TcServer. Startup logging level - all TcServers Administrators typically set startup logging to minimal levels for better performance. For all loggers used by TcServers, startup logging levels are specified in the logger.properties file within the TC_DATA directory. These levels apply to all business logic servers in server pools that use the TC_DATA directory. Session logging level - selected server Administrators can use the Teamcenter Management Console to dynamically change logging levels for a particular user session. Changing logging methods in this manner affects only the selected business logic server, and the changes persist only for the user session. Administrators can set the following logging levels: Logging level Description FATAL Logs only severe error events that cause the application to fail. This is the least verbose logging level. ERROR Logs error events that may allow the application to continue running. WARN Logs potentially harmful situations, such as incomplete configuration, use of deprecated APIs, poor use of APIs, and other run-time situations that are undesirable or unexpected but do not prevent the application from functioning. INFO Logs informational messages highlighting the progress of the application at a coarse-grained level. DEBUG Logs fine-grained informational events that are useful for debugging an application. TRACE Logs detailed information, tracing any significant application step. This is the most verbose logging level. DEFAULT Inherit logging level from the parent logger.