Delete Message

Operation Name

Delete Message

Function Overview

Delete messages in Amazon SQS.

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
Destination Required Not available Select a global resource.
  • [Add]:
    Add a new global resource.
  • [Edit list]:
    Global resource settings can be edited in “Edit resource list” screen.
  
Queue name Required Available Specify a queue to delete messages of.
  • Enter directly or select from the list.
  
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

<?xml version="1.0"?>
<message_results>
  <message_result receipt_handle="" >
  </message_result>
</message_results>
Element name Attribute name Description Remarks
message_results -    
message_result - Appears for each sent message. One DeleteMessage request is sent per element.
receipt_handle Specify the identifier (Receipt Handle) got when receiving a message from Amazon SQS.  
The output schema of Receive Message operation can be specified as the input schema of this operation.

Output schema

<?xml version="1.0"?>
<message_results>
  <message_result receipt_handle="" status="" >
  </message_result>
</message_results>
Element name Attribute name Description Remarks
message_results -    
message_result - Appears for each sent message. One DeleteMessage request is sent per element.
receipt_handle The same value as the one specified in receipt_handle element is stored.  
status The result of message deletion.
  • SUCCESS: Success
  • INVALID_RECEIPT_HANDLE: Failure (Invalid Receipt Handle)
  

Loading schema in Mapper

Schema is loaded automatically.
Refer to “Edit Schema” for more details.

Mass Data Processing

Mass data processing is not supported.

Transaction

Transaction is not supported.

PSP Usage

PSP is not supported.

Available Component Variables

Component variable name Description Remarks
count The number of messages sent successfully is stored.
  • Default value is null.
error_count The number of messages failed to send is stored.
  • Default value is null.
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
ResourceNotFoundException
Resource definition is not found. Name: []		 [Destination] is not specified. Specify [Destination].
ResourceNotFoundException
Resource definition is not found. Name: [<global resource name>]		 The resource definition selected in [Destination] is not found. Check the global resource specified in [Destination].
The specified queue does not exist for this wsdl version. (Service: AmazonSQS; Status Code: 400; Error Code: AWS.SimpleQueueService.NonExistentQueue; Request ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) A queue which does not exist is specified in [Queue name]. Check [Queue name], or [Region] setting of the global resource specified in [Destination].
The security token included in the request is invalid. (Service: AmazonSQS; Status Code: 403; Error Code: InvalidClientTokenId; Request ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) There is something wrong with [Access Key ID] of the global resource specified in [Destination]. Check the settings of the global resource specified in [Destination].
The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. There is something wrong with [Secret Access Key] of the specified global resource in [Destination]. Check the settings of the global resource specified in [Destination].

Notes