Handling loss of connection to an application
A good design practice is to code the connector application-specific code
so that it shuts down whenever the connection to the application
is lost. To respond to a lost connection, the connector's
application-specific component should take the following steps:
- Log a fatal error message so that email notification is triggered
if the LogAtInterchangeEnd connector configuration property is set to True.
- Return the outcome status inform the connector controller that the application
is not responding. When this occurs, the process in which the connector
runs is stopped. A system administrator must fix the problem with
the application and restart the connector to continue processing
events and business object requests.
The following user-implemented methods
should check for a loss of connection to the application:
- For event notification, the pollForEvents() method should verify the connection before it accesses the
event store. For more information, see
- For request processing, the doVerbFor() method should verify the connection before it begins verb
processing. For more information, see
