Output XML Data Log

Operation Name

Output XML Data Log

Function Overview

Write XML type input data to execution log at arbitrary log level.

Data Model

XML type.
For more details on input/output schema, refer to “Schema”.

Properties

For details on use of variables, refer to “Variables”.
Basic settings
Item name Required/Optional Use of variables Description Remarks
Name Required Not available Enter the name to show on the script canvas.  
Input data Required Not available Select a component on the script canvas.  
Required settings
Item name Required/Optional Use of variables Description Remarks
Output log level Required Not available Select a log level to output in.
  • [NOTICE]:
  • [INFO]: (default)
  • [FINFO]:
  • [FINEST]:
  • [DEBUG]:
  • Log will be output in the specified log level.
  • Refer to “Log Level” for more details.
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.
 

Schema

Input schema

Same as the schema of input component.

Output schema

Same as the schema of input component.
Refer to “Schema of XML type” for more details.

Loading schema in Mapper

Schema should be loaded manually.
Specify the schema of the data to be read.
Refer to “Edit Schema” for more details.

Mass Data Processing

Mass Data Processing is supported.

When the setting of input source component is to perform Mass Data Processing, then it will be performed automatically.

PSP Usage

PSP is not supported.

Available Component Variables

Component variable name Description Remarks
message_category When an error occurs, the corresponding message code's category is stored.
  • Default value is null.
message_code When an error occurs, the corresponding message code is stored.
  • Default value is null.
message_level When an error occurs, the corresponding message code's severity is stored.
  • Default value is null.
error_type When an error occurs, the error type is stored.
  • Default value is null.
  • The error type will be in the following format.
    Example: “java.io.FileNotFoundException”
  • The contents that will be stored may vary depending on DataSpider Servista versions.
error_message When an error occurs, the error message is stored.
  • Default value is null.
  • The contents that will be stored may vary depending on DataSpider Servista versions.
error_trace When an error occurs, the error's trace information is stored.
  • Default value is null.
  • The contents that will be stored may vary depending on DataSpider Servista versions and client applications.

Specification Limits

None.

Major Exceptions

Exception name Cause Solution
InputDataNotFoundException [Input data] is not specified. Specify [Input data] or draw a data flow.