The Failed Event Details page enables you to set or modify values for the trace control and expiration date associated with a failed event.
Failed events can be resubmitted with trace to help you monitor the event processing. Tracing can be set for a service or a component, and it can be sent to a log or to the Common Event Infrastructure (CEI) server. When you view the failed event data on the Failed Event Details page, the default trace value SCA.LOG.INFO;COMP.LOG.INFO is shown for the event. If you resubmit the event with this default setting, no trace occurs when the session calls an SCA service or executes a component.
Some failed events also have an expiration. If a user has specified an expiration with the asynchronous call that sends the event, that data persists even if the event fails, and the expiration time appears in the Resubmit Expiration Time field on the Failed Event Details page. Expired failed events cannot be resubmitted successfully. To prevent a second failure, you can edit the expiration date for the event to ensure that it is not expired when it is resubmitted.
Security role required: You must be logged in as administrator or operator to perform this task.
Last updated: Thu Apr 27 15:07:56 2006
(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)