Problem:

Which logging level of EL Server is enough for support to investigate problems that are not reproduceable?

Resolution:

EnterpriseLink Server uses Logging Level configuration settings to determine how much information is placed in the Server.log file. The configuration setting is under EnterpriseLink Administrator's Site --> Configuration --> Messages and Logs tab. The Server.log file is placed in the EnterpriseLink installation directory's logs directory. The Logging Level can be selected with one of the following settings:

0 - no messaging Although Server.log is created and contains the version number of the EnterpriseLink Server, no other messages are recorded.

1 - warnings and errors Error messages sent to the browser (e.g., EL0005 can't connect to host) are recorded here along with warnings such as pages not found. When Performance Monitoring has been enabled through the Configuration --> Session Info administrator setting or using the Windows Performance Monitor, performance statistics are also generated at this logging level.

2 - session, screen matching, and repository loading status Indications as to the operation of each session are recorded in the Server.log file. Messages are grouped by context. The Manage Session grouping includes when sessions begin, end and connect to the host application. The Process Session grouping logs the URL processing. The Page Retrieval grouping indicates when page definitions are retrieved from the repository.

3 - warnings, errors and trace This setting includes detailed tracing information that allow Micro Focus personnel to diagnose issues and answer questions about the transformation process that EnterpriseLink Server goes through.

4 - full log and datastream Further detailed information regarding the internal operation of EnterpriseLink Server is produced as well as a host trace file, Server.rep.

The log file settings include the ability to split the log at certain intervals. Check the Split log file every [1] days checkbox. Log files are then timestamped with the time they were created, such as Server-2004-04-21_15-47-32.log. At log level 4 all host communications are logged to a single Server.rep file. Log splitting occurs around midnight. To break each session's trace file up you may check the One Per User Session checkbox. Files are stamped with the session ID and are of the form Server-20uMM2ADOQZM2HRe.rep.

Generally, customers can run EnterpriseLink with log level 1, warnings and errors. SupportLine personnel may ask for detailed tracing information to be sent to Micro Focus. If so, turn on log level 4. SupportLine will ask for both the Server.log and the accompanying host application trace file Server.rep to diagnose problems.

It is not recommended that log level 3 or higher be used in a production system as performance is degraded and large log files are produced.