Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Building Services | About Service Auditing | Service Auditing Use Cases | Auditing for Recovery
 
Auditing for Recovery
Auditing for recovery involves using the service log to track executed services and service input data so that you can re-invoke the services. You might want to audit for recovery in the event that a resource experiences a fatal failure, and you want to restore the resource to its pre-failure state by resubmitting service invocations.
When auditing for recovery, you want to be able to resubmit failed and successful services. The service log needs to contain an entry for each service invoked by a client request or a trigger. The service log also needs to contain a copy of each service’s input pipeline.
To use the service log to audit for recovery, select the following Audit properties.
For this property...
Select this option...
Enable auditing
When top-level service only
Log on
Error and success
Include pipeline
Always
To use the service log to audit for recovery, use a database for the service log.