As a general rule, the Logidex application log(s), "logiclibrary_*.log", should always be included in a Customer Issue report. Retrieve logs through the Logidex Site Administration page {servername}/logiclibrary/admin/listLogs.do. In addition, if the logging level from the time of a problem was not at FINER or FINEST, increase the logging level and attach the more verbose log to the CI asset. Application server or Web server logs may be included with a CI, if available, or may be requested by LogicLibrary Support. J2EE data upgrade actions are logged to "ll_startup_*.log," and .NET data upgrade actions are logged to "trace.log," located in the Logidex logging directory.
1. Access the Logidex site administration console (mainMenu.do)
2. Click Execute A Command
3. Classname: GetLoggingConfig
4. Invoke
5. Copy the output into a text editor such as Notepad
6. Edit, as appropriate:
7. Save the changes in a file name of your choice
8. Back in the browser, click Back to the Execute A Command page
9. Classname: UpdateLoggingConfig
10. Browse to the file you saved in step 7
11. Enter "save" (without the quotes) in Parameter 1 to save the change across application restarts
12. Invoke
1. Open the LogicLibrary web.xml located in the deployed EAR directory: logidex.ear/logidex.war/WEB-INF/web.xml file
(If websphere 6.1: birt.ear/birt.war/WEB-INF/web.xml)
2. Modify the existing BIRT_VIEWER_LOG_DIR entry, and specify somewhere to write the BIRT logs. Make sure it exists and is writable:
Example:
<context-param\>
<param-name>BIRT_VIEWER_LOG_DIR>/param-name>
<param-value>/tmp</param-value>
</context-param>
3. Modify the existing BIRT_VIEWER_LOG_LEVEL and set it to FINEST
Example:
<context-param>
<param-name>BIRT_VIEWER_LOG_LEVEL</param-name>
<param-value>FINEST</param-value>
</context-param>
4. Restart the application server