11. Error and trace log files
No logs are generated on the client side. All errors are displayed using popup windows or via the HTML browser. An option enables to control the display of errors to end users (GUI). For advanced diagnostic, a verbose mode can be enabled to generate more detailed logfiles.
Different files can be created on server side. There are 2 mains default locations for the logs:
• C:\ProgramData\MEGA\Hopex Application Server\logs
For the logs of the HAS Instance Manager.
• C:\ProgramData\MEGA\Hopex Application Server\5000\Logs
For the logs of the HAS Instance: HAS server and all the modules.
Where “5000” is the port number of the instance
 
General naming convention of log files:
“cluster name”-[“Module name”-“Module version”]-YYYYMMDD.txt
Where:
• Cluster name: is the name of the cluster or the port number
• Module name: is the name of the module defined in the manifest
• Module version: the full build version of the module as defined in the manifest
• YYYYMMDD: represents the year, month and day
Example:
5000-[HAS.CONSOLE-1.0.301]-20201104.txt
5000-[HAS.UAS-1.0.301]-20201104.txt
 
Log name
Content
5000-[HAS-X.X.X]-YYYYMMDD.txt
Main HAS Server log
megaerrYYYYMMDD.txt
Main logs of HOPEX
5000-[HAS.CONSOLE-X.X.X]-YYYY.txt
For logs on the HAS console
5000-[HAS.PORTAL-X.X.X]-YYYYMMDD.txt
For logs on the portal that expose all web modules
5000-[HAS.UAS-X.X.X]-YYYYMMDD.txt
For logs about identity manager
5000-[HOPEX WEB DESKTOP-X.X.X]-YYYYDDMM.txt
For logs of the web part of HOPEX
sspsprvsYYYYMMDD.txt
Supervision error logs
ssperrYYYYMMDD.txt
Errors generated by the SSP when assigning a user to an environment
redis_server_log.txt
Redis logs in case of cache issues.
HopexHealthDigestReportYYYY-MM-DD_XX-XX-XX.html
 
Report to diagnose HOPEX usages and performance
HopexHealthFullReportYYYY-MM-DD_XX-XX-XX.html
Report to diagnose HOPEX usages and performance
RepositoryHealth-YYYY-MM-DD- MyEnvironment_MyRepository
Report to diagnose HOPEX usages and performance