Configuring Additional Fatal Error Codes

Remedy Adapter recognizes a set of AR System API call error codes as fatal. These error codes indicate that the AR System has become unavailable. In response to a fatal error code, Remedy Adapter throws an AdapterConnectionException, drops the connection from the connection pool, and tries to create a new connection.

You can configure Remedy Adapter to add to the list of error codes that it considers fatal. As a result, when Remedy Adapter receives one of the fatal error codes you configure, it behaves in the same manner; that is, throws an AdapterConnectionException, drops the connection from the connection pool, and tries to create a new connection.

To identify additional fatal error codes, use the Integration Server Administrator to configure the watt.adapter.Remedy.fatalErrors server configuration parameter in the Extended Settings. You use this configuration parameter to list the AR System API call error codes that should be considered fatal.

When an AR System API call results in an error and an ARException is thrown, Remedy Adapter catches the exception. Remedy Adapter examines the error code and if it matches a code listed on the watt.adapter.Remedy.fatalErrors configuration parameter, an AdapterConnectionException is thrown rather than a AdapterException.

1. Start your Integration Server and the Integration Server Administrator if they are not already running.

2. From the Integration Server Administrator, from the Settings menu in the navigation panel, select Extended.

4. In the Extended Settings box, add a line for the watt.adapter.Remedy.fatalErrors server configuration parameter.

For example, if you want Remedy Adapter to consider error codes 91, 95, and 99, as fatal, you would use the following:

Note:
By default error code number 90 is treated as a fatal error. You can append a new error code to the existing list.

For more information about setting server configuration parameters, see the webMethods Audit Logging Guide for your release.