This documentation is in progress and includes all updates released after Data Analytics Server 3.1.0. For documentation specific to a version, see About this Release.
WSO2 Data Analytics Server is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

All docs This doc
||
Skip to end of metadata
Go to start of metadata

WSO2 DAS has many inbuilt event receivers to receive events via different transports. In addition, you can receive events via SQS by implementing an SQS event receiver as explained below.

Before you begin:

  • Download the aws-java-sdk-bundle-1.11.261.jar from here and place it in the <DAS_HOME>/repository/components/lib directory.
  • Download the org.wso2.carbon.event.input.adapter.sqs-5.1.3.jar and place it in the <DAS_HOME>/repository/components/dropins directory.

To configure an SQS event receiver, follow the steps given below:

  1. Start the WSO2 DAS server by issuing one of the following commands.
  2. Create an SQS event receiver. For detailed instructions to create an event receiver, see Configuring Event Receivers.

    The following are adapter properties configured for the SQS event receiver

    Adapter PropertyDescriptionConfiguration File PropertyOptionalDefault Value
    queueURLThe URL of the queue from which the event receiver consumes eventsqueueURLNoN/A
    AccessKeyThe AWS access key.accessKeyNoN/A
    SecretKeyThe AWS secret key.secretKeyNoN/A
    RegionThe AWS service region.regionNoN/A
    Polling intervalThe number of milliseconds between two message retrieval operations.pollingIntervalYes500
    Wait TimeThe maximum amount of time (in seconds) that a polling call should wait for a message to become available in the queue.waitTimeYesThe default value set in the configurations of the queue.
    Max number of messagesThe maximum number of messages to be retrieved per polling call.maxNumberOfMessagesYes1
    Visibility TimeoutThe time period after which a message received by a consumer should no longer be visible for other consumers.visibilityTimeoutYesThe default value set in the configurations of the queue.
    Delete message after consumingIf this parameter is set to true, each message is deleted once it is consumed.deleteAfterConsumingYestrue
    Max number of retry attemptsThe maximum number of times the system must attempt to delete a consumes message if a delete operation fails.deleteAfterConsumingYestrue
  • No labels