Listener keywords for Windows

The following keywords can be used to configure message handlers created with the dblsn -l option. For more information about using Listener keywords, see -l option.

Filter keywords

Use the following keywords to filter messages in a push notification:

Keyword syntax Description
subject=subject-string

Filters a message if the subject is textually equivalent to subject-string.

content=content-string

Filters a message if the content is textually equivalent to content-string.

message=message-string

Filters a message if the entire message is textually equivalent to message-string.

message_start=message-string

Filters a message if it begins with message-string.

sender=sender-string

Filters a message if it is send by sender-string.

Action keywords

Use the following keywords to initiate an action when a filter condition is met:

Keyword syntax Description
action=command

Specifies an action command. See Listener action commands for Windows.

altaction=command

Specifies an alternative action command that is initiated when the action command fails. See Listener action commands for Windows.

Polling options

Use the following options to configure a light weight poller:

Keyword syntax Description
poll_connect={ http | https | tcpip } [ (protocol-option=value;...) ]

Specifies the light weight network protocol options required to connect to the server. The default value is inherited from the dblsn -x option. See -x option.

poll_notifier=Notifier-string

Specifies the name of the Notifier that handles push requests. Required.
poll_key=key-string

Specifies the name of the Listener to identify itself to the Notifier. This value must be unique. Required.
poll_every=seconds-number

Specifies how often the Listener should poll the server. The interval is measured in seconds. The default value is auto-retrieved from the MobiLink server.

Options

The following can be used to configure message handler behavior:

Keyword syntax Description
continue=[ yes | no ]

Specifies whether the Listener should continue listening after finding the first match. The default value is no. A yes value is useful when specifying multiple filters, where one message initiates multiple actions.

confirm_action=[ yes | no ]

Specifies whether the filter should confirm the action. The default value is yes.

confirm_delivery=[ yes | no ]

Specifies whether the filter should confirm qualified message delivery. The default value is yes, so delivery confirmation is sent after the first filter accepts the message.

Delivery can only be confirmed if the message requires confirmation, and if the filter accepts the message. A message requires confirmation if the specified gateway has its confirm_delivery keyword value set to yes. A no value can be used when multiple filters accept the same message to give you finer control over which filter should confirm the delivery. For information about handling delivery confirmation on the server, see confirmation_handler event.

maydial=[ yes | no ]

Specifies whether the action has permission to dial the modem. The default value is yes. A no value causes the Listener to release the modem before the action.

See also
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1