Editing trace or expiration data in a failed event

The Failed Event Details page enables you to set or modify values for the trace control and expiration date associated with a failed event.

Why and when to perform this task

Important: Any edits you make to the trace or expiration data are only saved locally until you resubmit the event. If you perform any other action before resubmitting the event, all edits are lost.

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.

Steps for this task

  1. Ensure that the failed event manager is open and that you have retrieved a list of the failed events on your system.
  2. From the failed event manager’s Search Results page, click the ID (found in the Message ID column) of the failed event whose data you want to edit.

    The Failed Event Details page opens.

  3. If the event has an expiration date that causes it to expire before it is resubmitted, edit the expiration in the Resubmit expiration time field.

    The expiration time shown is local to the server. The value for this field must be formatted according to your specified locale. An example of the correct format for your locale is provided above the field.

  4. If you want to enable tracing for the failed event, specify a new value in the Trace Control field. For detailed information about trace values, see the Monitoring topics in the WebSphere Process Server Information Center.
  5. Do one of the following:
    • If the edited data is correct and you want to resubmit the event, click Resubmit to make the changes at a server level.
    • If you want to remove the changes you made, click Undo local changes.

    The edited failed event is resubmitted for processing and is removed from the failed event manager.

Related tasks
Finding failed events

Terms of use |

Last updated: Thu Apr 27 14:23:51 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)