Copyright © Cloud Software Group, Inc. All Rights Reserved

OnError

Activity

This activity provides error handling mechanism for all the errors that happen outside the job boundaries of all processes associated with the service resource.

You are recommended to create only one process definition with this event source for the whole project. If you create multiple processes, then all of them will be triggered and may not be in sequence.

Whenever an error occurs for messages triggered through Service Resource outside of Job boundaries, the Error handler process gets triggered with the appropriate data.

This error handler process can be used only for Logging purposes. The actual Service MEP will not be affected.

The Error handler handles the failure in Pre-process, Post-process (failure while sending the response), and Fault Sending scenarios. It does not catch the error during the execution process.

Configuration

The Configuration tab has the following fields.

Field	Description
Name	The name to appear as the label for the activity in the process definition.
Description	Short description of the activity.

Misc

The Misc tab has the following fields.

Field	Description
Sequencing Key	This field can contain an XPath expression that specifies which processes should run in order. Process instances with sequencing keys that evaluate to the same value will be executed sequentially in the order the process instance was created. See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information about controlling the execution order of process instances and about XPath expressions.
Custom ID	This field can contain an XPath expression that specifies a custom ID for the process instance. This ID is displayed in the View Service dialog of TIBCO Administrator, and it is also available in the $_processContext process variable.

 

Output

The Output-tab of the onError event source contains the following schema:

•	errorCode - Contains the error code useful for filtering the errors.

•	errorDesc - Contains description of errors.

•	errorStack (optional) - Contains stack of error logs.

•	msgData - Contains the Soap-Envelope of the message.

•	MessageHeaders (optional) - Contains either JMS or HTTP transport headers.

This depends on the transport for which the error is captured.

•	mimeEnvelopeElement (optional) - Contains mime data.

Copyright © Cloud Software Group, Inc. All Rights Reserved