The support team may ask for troubleshooting purposes to send the PDE Log.
This log is available from the Semarchy Workbench.
To Export the PDE Log:
...
PDE Log provides lots of details (ERRORs, WARNings, INFOrmation) about what's going on in Semarchy xDM. It's configurable to provide more or less detail, and it's an invaluable troubleshooting tool.
Open the PDE Log:
- In xDM 4.4 and earlier:
- Open the Workbench
- Menu: Windows -> Show View... -> Error Log
- In xDM 5.0 and later:
- Open the Application Builder
- Menu: <Username> -> Error Log
To Export the PDE Log:
- Click the button Export Log in this view and download the log export.
- Alternative: see below for details about the location of this file on the server.
| Info |
|---|
You may want to Please delete the content contents of the PDE Log then first. Then reproduce the issue that you are facing prior to exporting and sending it . Then export and send the log to the support team. |
Advanced
For users with access to the application server you can find the same PDE log in a location like this one (the exact path may differ based on your configuration, and files are usually hidden, make sure to use the ls command with the -a flag: ls -a command):
- <tomcat-home>/work/Catalina/localhost/semarchy/eclipse/workspace/.metadata/.log
- <tomcat-home>/work/Catalina/localhost/semarchy/eclipse/workspace/.metadata/.bak_0.log
Trivia: PDE stands for Plug-in Development Environment and is used because the Semarchy xDM workbench is based on Eclipse RAP.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...