Monitor Exception

Operation Name

Monitor Exception

Function overview

Monitors the target process for exception and handles exception.

Monitor Exception Structure

Icon Name Description
Monitor Exception The start of Monitor Exception.
Try Sets the component to monitor exception between [Try] and [End Monitor Exception].
Exception Handler Sets the component to use when error occurs in the monitoring target process between [Exception Handler] and [End monitor exception].
End Monitor Exception End of Monitor Exception.

Properties

For information about using variables, refer to "variables".
Basic settings
Item name Required/Optional Use of Variables Description Remarks
Name Required Not available Enter the name on the script canvas.  
Required settings
Item name Required/Optional Use of Variables Description Remarks
Check target Required Not available Select the component to monitor for exception.

If an exception occurs during processing the checked component, the [Exception Handler] is performed.
  • Component placed between [Try] and [End Monitor Exception] is shown.
  • If no component is checked, all components placed between [Try] to [End Monitor Exception] are checked.
Comment
Item name Required/Optional Use of Variables Description Remarks
Comment Optional Not available You can write a short description of this adapter.
The description will be reflected in the specifications.
 

PSP Usage

PSP is not supported.

Available component variables

Component variable name Description Remarks
component_name Returns the name of the component the exception is thrown by.
  • The value defaults to null.
component_type Returns the type of the component the exception is thrown by.
  • The value defaults to null.
message_category Returns the category of the message code corresponds to the error raised by the component being monitored.
  • The value defaults to null.
message_code Returns the message code corresponds to the error raised by the component being monitored.
  • The value defaults to null.
message_level Returns the severity of the message code corresponds to the error raised by the component being monitored.
  • The value defaults to null.
error_type Returns the type of the error raised by the component being monitored.
  • The value defaults to null.
  • Error is represented in the format depicted below.
    Example:java.io.FileNotFoundException
  • The message may vary depending on DataSpider Servista version.
error_message Returns the message of the error raised by the component being monitored.
  • The value defaults to null.
  • The message may vary depending on DataSpider Servista version.
error_trace Returns the stack trace of the error raised by the component being monitored.
  • The value defaults to null.
  • The message may vary depending on DataSpider Servista version or the client application used.

How to operate Monitor Exception

Creating Monitor Exception

Sets the component to monitor exception between [Try] and [End monitor exception].

Add Monitor Exception

Select [Add exception handler] from right-click menu of [Monitor Exception] and adds an exception.
The maximum number of [Exception Handler] icons are 98.

Change of the determination order of Exceptions

Determination order of multiple exceptions can be changed by [Move up determination order] or [Move down determination order] from right-click menu of [Exception Handler]. The number on [Exception Handler] is the determination order.

Specification Limits

Main exceptions

None.

Notes