Message Log
Introduction
The message log is where the Websydian Express runtime reports any errors that has been registered. The message log is used to detect errors and determine their cause.
Accessing the message log
You access the message log using the administration menu Utilities→Message Log.
Content of the message log
The log shows all of the messages reported by the runtime - with the newest message shown first. The list can be positioned on messages from a particular date.
It is important to note that all messages from all sites are shown.
The information shown for each message is:
- An ID, this is mostly used to make it possible to refer to other messages
- The message text
- An icon showing the severity of the message
- The date and time of the message
- A help icon
Please note that clicking the help icon leads to a page containing an explanation for the message type.
Please note that the runtime generally can't register errors encountered in the business process functionality. For example an erroneous parameter interface on a call between a PageGenerator and the function used to fetch the data in the database will not be reported in the message log.
As the runtime must perform a database write to report errors in the message log, errors leading to a message wait or an endless loop can't be reported to the message log.
Use of the message log
The most obvious use of the message log is that you should always check it when an error is reported/encountered.
In some cases the user will not report encountered errors - in some cases the user might not even be aware that an error has occurred. This means that it can be a good idea to regularly check whether new errors has been written to the log.
Other logs
Application errors
As mentioned above, not all errors can be reported in the message log. When it comes to errors encountered when running the application, there are two other logs that can be relevant - dependent on the Websydian Express variant.
Websydian Express for ISeries
Check the job logs for the EXPRESSAS jobs submitted when running the START command.
Websydian Express for Windows
Check the ApplicationServices.log file that is placed in the Logs folder.
Websydian Express for Windows and ISeries
Check the job logs for the EXPRESSAS jobs submitted when running the START command.
Check the ApplicationServices.log file that is placed in the Logs folder.
System errors
The Websydian Express runtime uses a number of components that can also write errors to logs.
The Websydian Server that has responsibility for routing the requests to the correct application service (and controls the license system) reports errors to the file websydianserver.log. This file can be found under the Logs folder that has been created during the installation.
The web server component reports errors to the file relayservice.log. Where this file is placed depends on where the web server component is installed.