Enabling Client Logging in AutoVue Client/Server Deployment
(Doc ID 752589.1)
Last updated on JUNE 20, 2023
Applies to:
Oracle AutoVue 3D Professional Advanced - Version 20.0.0 and laterOracle AutoVue Electro-Mechanical Professional - Version 20.0.0 and later
Oracle AutoVue Office - Version 20.0.0 and later
Oracle AutoVue 2D Professional - Version 20.0.0 and later
Oracle AutoVue EDA Professional - Version 20.0.0 and later
Information in this document applies to any platform.
Goal
In an AutoVue Client/Server Deployment where the client is deployed as an applet, the primary means of client logging is through the Java Console. Client logging may be required when troubleshooting certain types of AutoVue issues such as printing-related issues or markup-related issues.
This document outlines the two stages to enable client logging when using AutoVue Client/Server Deployment, as well as advanced options for debugging rare and complex issues on the client.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Modify the 'VERBOSE' applet parameter |
| Enable the Java Console |
| Advanced Options - Tracing and Logging (not required unless specified by support) |
| Advanced Options - Generate Java thread dump |
| References |