Adapter Development Kit 6.5 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Run Time Activities | Retry and Recovery Architecture
 
Retry and Recovery Architecture
 
Detection
Removal/Regeneration
Retry Mechanisms
Putting It All Together…
A highly available and reliable system has the ability to recover from temporary errors. If, during execution, a transient error is encountered, the system should do the following:
1. Detect the error
2. Remove or regenerate the component causing the error
3. Retry the operation.
The first phase in recovery is defining a transient error. For a webMethods adapter, a transient error is one that will go away in time, without requiring human intervention on webMethods Integration Server. If an adapter service is called and tries to perform an insert and the backend resource rejects the insert because the data format is incorrect, then this is not transient. Someone will need to reformat the data for the insert to complete correctly.
Suppose you try the insert and your backend system is offline for scheduled maintenance. The insert will fail, but when the system comes back on line, the insert would work. Retrying the operation in this scenario is useful.
The role of detecting the transient error is the responsibility of the adapter. The removal, regeneration, and retry functions are provided by Integration Server.