|
<< Click to Display Table of Contents >> Navigation: Appendix > Parameter Files > DBWAppH.PAR |
The presence of the file DBWAppH.par in the InstallationFolder, makes the loggin enable.
An easy procedure to enable logging is described in the Troubleshooting topic.
Here below is an example of a DBWAPPH.PAR file content:
according to the enabled options, different application behavior are logged.
TRACE_SQL 1
TRACE_FUNCTIONS 1
TRACE_API 1
TRACE_LOW_LEVEL_FUNCTIONS 1
TRACE_EXCEPTIONS 1
TRACE_PROJECTS 1
TRACE_BACKGROUND_FUNCTIONS 1
TRACE_CUSTOM_PROPERTIES 1
The tracing parameters that can be written in this file are:
This parameter enables the logging of any error that may happen while processing the file's custom properties.
It writes a special Log file named %TMP%\DBW_CustomPropertiesMonitor.LOG. We suggest to enable this tracing only when you are experiencing problems with the file custom properties.
If present and set to 1, MechworksPDM creates the .LOG file in the USERS\<user name> user specific directory. This permits the administrator to have all the log files in a shared directory.
Normally MechworksPDM creates a new log file at every session; if this option is present and set to 1, MechworksPDM appends the log to the existing one.
When set to 1, MechworksPDM doesn't flush the buffered filed information on the disk at every new line of the log file. This can be helpful when logging the activities for long periods of time.
When set to 1, all the database commands are written in the log file.
When set to 1, all the functions flow are written in the log file.
When set to 1, all the functions flow running as background processes are written in the log file.
When set to 1, all the CAD specific API calls are written in the log file.
When set to 1, any exception happened in the system are written in the log file.
When set to 1, keeps trace of current project changes and other activities related to projects.
It permits to choose to use eDrawings or not when printing through the Standalone.
When set to 0, the default application associated with the SolidWorks files (typically the SolidWorks Viewer) will be used for printing
If set to 1, the browser window is automatically closed when both the screensaver starts or the computer is locked by the user. This is in order to prevent random instabilities happening when restoring the normal state of the Windows desktop
This behavior does not apply to the StandaloneClient system
In some cases, installations with DBWServer, with the Debug LOG activated and with specific network settings, causes some warning messages like "The data area passed to a system call is too small" on functions like "FileSet/ResetReadOnly" and similar, but neverless the files are correctly managed by DBWorks (all the read-only attributes/etc. are correct) - in such environments it can be set the IGNORE_SYSTEM_ERROR parameter.
For a full list of the possible Win32 System Errors, please refer to: http://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx
to avoid the warning about the "Data area passed to a system call is too small" message, you may set:
IGNORE_SYTEM_ERROR 122
When set to 1, enables a more specific (verbose) log, useful for highlighting performance issues.
The semicolumn char ( ; ) defines as comment the rest of the line.
A sample of DBWAPPH.PAR, tracing functions and database calls is:
TRACE_FUNCTIONS 1
TRACE_SQL 1
<empty line>
A sample of DBWAPPH.PAR, tracing functions, api functions, database calls, created in the local user directory, appending to the previous logs, is:
TRACE_CREATE_LOG_IN_USER_DIR 1
TRACE_APPENDING_MODE 1
TRACE_FUNCTIONS 1
TRACE_SQL 1
<empty line>
For working over slow network, like VPN / Cloud / etc. it is now possible to declare a special parameter:
VPN_MODE_LOCAL_DRIVE C:
The intent is to make possible to connect to a remote server using a low-band-width connection ( example, an ISDN connection at 128Kb ), accepting a series of limitations in the User Interface.
Of course, the VPN MODE can also be used with a fast connection, for speeding up the overall User Interface for specific cases ( example, when working with very large set of data ).
When in VPN MODE, the Browser Title shows the label "[VPN MODE]".
Assumptions and limitations of the VPN MODE:
•Global Parameters Path must point to the shared location
•the declared VPN_MODE_LOCAL_DRIVE is the drive where an exact copy of the shared MechWorks_PDM_Server folder can be found ( Example: if the shared folder is on Z:\MechWorks_PDM_Server, then, declaring VPN_MODE_LOCAL_DRIVE C: will assume that the same folder can be found in C:\MechWorks_PDM_Server )
•The Shared DBWAPP.PAR must be read-only
•All Shared Paths, except USERS, are automatically changed to the local installation directory ( shared MechWorks_PDM_Server must be copied locally to the VPN_MODE_LOCAL_DRIVE )
•No Visual Cues
•No Tree/Grid Graphic Features depending from Database Values
•Tree Items expanded status not restored automatically when Browser opens
•No automatic refreshing of ComposedOf/UsedBy lists
•No Document Page: always open in Tree Page
•No in-Workflow documents markers: they can be accessed using the side bar queries