External error pages for Self Service throttling

When the

AtHoc

Self Service application is throttled to use only 30% of CPU, it is likely that IIS will display errors with a status code of “503” or “500” when the system is under heavy load and unable to handle requests. If these errors occur, IIS displays a default error page that does not contain a lot of useful information for users.

These errors are usually not customizable at the IIS level on the same server, as documented by Microsoft.

BlackBerry AtHoc

provides friendly messages in static pages that can be used in place of the default error pages, provided that the

BlackBerry AtHoc

system is deployed behind a proxy server or load balancer that supports error message customization. You can configure these load balancers or proxy servers to trap these errors and redirect to the friendlier messages instead. The error pages are available on the application server at the following path:

AtHocENS\wwwroot\errorpages

.

You can take the

errorpages

folder and host it on any web server that is capable of serving HTML, CSS, and Javascript pages.

To host the folder, administrators copy the folder and make it publicly available from their web server. For example, if you hosted these pages directly under the root folder of the web server, the error pages can then be accessed using the following URLs, where <domainnameofserver> refers to the actual domain name of the server:

After these pages are hosted on a different server than the

AtHoc

server, you can configure the individual proxy server or load balancers to redirect to the static hosted pages based on the error that IIS returns to the client.