If your web.xml file does not look like this then it is the old web.xml file: Older web.xml files vary in style and content but the new one is standard, so rather then specify all the old web.xml file variations it is much simpler to outline the new one. viewone.properties or the older *.properties, is defined in the web.xml file. Each file is outlined in its default and modified format below. In these files we specify the log name, location and the traces that are being enabled, but they all use the same format regardless of whether they are old or new. Newer systems use the viewone.properties file for all viewer server components. Older systems may be using the streamer.properties file for the streamer and burner.properties or redactlocal.properties files for redaction. There are two server components to the viewer for which you may need to gather the logging (streamer or redaction).ĭepending on the age of your system these can be configured using different properties files. So any annotation load viewer startup or document load issue may well have occurred prior to you being able to enable them here.Įnabling the server side traces and log file location It is generally recommended that you add the tracing via the viewer source page rather then via this window, as ticking the boxes on this page only enables the traces for this viewer session and using this method they cannot be enabled prior to start up. Once these have been added correctly you can verify this by opening the viewer and accessing the shift+t window.Īs you can see the three traces are listed as HTML parameters on the left and as debug settings on the right. You may have integrated the viewer using JSP files, or many other methods, but the above information should be able to be applied by your internal team. The three most common trace parameters have been added in the example above but this does vary depending on the issue you are trying to resolve. Using the simplest example of this page (in an HTML format) it would look like: This is done by adding additional parameters to the HTML page that runs the viewer. If asked for "full Java logging" this would indicate that you should enable "tracing", "logging" and "Show applet lifecycle exceptions" as part of your log gathering procedure. You may be asked to enable any of the three top options in this control panel so please take a note of these for your reference. Please make sure this is set to "Show console" during your testing. Under the Advanced tab you should see the Java console hidden by default. The client logging appears in the client side Java control panel rather then in a log file so you will need to set your Java console on the client machine to be shown prior to the issue being reproduced.įor the Java console to be shown please access the Java control panel. With a stand-alone installation of the viewer, logging is enabled in several different areas depending on the logs required and the version installed.