Customising
Error Pages
See
also:
Ebase contains a number of error
pages which are presented to the end user when runtime errors occur. These
pages are designed to be customised to meet the requirements of different
customers. The pages are located within the top level directory of the Ebase
web application.
|
File name |
Displayed
when... |
Comments |
|
ufs_authentication_error_page.htm |
Authentication error occurs: HTTP 401 error. |
Applies only if security is enabled and authentication has not been
done prior to accessing the Ebase form. |
|
ufs_authorisation_error_page.htm |
Authorisation error occurs: HTTP 403 error. |
Applies only if security is enabled. This page appears when the end
user does not have access to the requested resource. |
|
ufs_error_message.htm |
A form failure is detected by the Ebase system e.g. form design error,
external system not available etc., and a form on error event is not specified. |
The html in this file will be included in an html page generated by Ebase. The file should not include <html>, <body> and <head> tags, or corresponding closing tags.
If startup parameter
Ufs.systemMode is set to 'Test', detail error messages will additionally be displayed.
If Ufs.systemMode is set to 'Prod', detail error messages will not be
displayed. |
|
ufs_error_page.htm |
A catastrophic error has occurred e.g. Ebase or application software
failure. |
|
|
ufs_timeout_page.htm |
A timeout occurs part way through a form. |
The timeout period (maximum time between receiving data from a client
browser) is set in the Ebase web deploment descriptor file web.xml. This is
located in the WEB-INF directory of the Ebase web application. This is
supplied with the timeout value set to 30 minutes. |