Log out?

HTTP Get Listener

HTTP Get Listener – URL and returns the HTTP response of that query as a transaction.

Select the HTTP Get Listener from the Listener Type drop-down.

This Listener has 5 tabs: Basic, Advanced, Transaction Logging, Authentication, Proxy Configuration, and Encoding.

1. Basic – in the Basic tab you can specify:

Request path: Specifies the HTTP path to request to.
Polling interval: How often the path is polling.

2. Advanced – in the Advanced tab you can specify:

Initialize on trigger only: If enabled, the Listener doesn’t start up until a trigger initializes it.
Allow command-line invocation: If enabled, the Listener can be invoked using the CLI client application.
Restart on listening error: If enabled, the Listener will be restarted after an error occurs.

FIFO Queue Name: The FIFO stuff enables a “First In, First Out” queuing mechanism between Listeners and Transports. If a “FIFO Queue Name” is provided, that name will be used as a key for a queue Transactions & will be pushed into before reaching a transport. They’ll be ordered in this queue according to when the Listener created them.

FIFO Queue Delay: It is the interval between updates/checks against that queue. Providing a queue name guarantees that a given Transport sends transactions in the same order the Listener created them in.

Trust self-signed certs: enables a trust strategy that accepts self-signed server certificates as trusted

Validate SSL Hostnames: SSL certificates include hostnames that they are valid for, under certain circumstances, you may want to disable this hostname validation

3. On the Transaction Logging tab you can enable transaction events logging. That data can be logged by a TransactionEventListener.

The Transaction Logging Enable: This checkbox allows transaction events originating from this listener to be logged by a TransactionEventListener.

Log Transaction Data: If enabled, logs transaction data body.

Log Transaction Data Base64: If enabled, logs transaction data body as Base64.

Log Transaction Attribute: If enabled, logs transaction attributes.

Log All Attributes: If enabled, no attributes will be filtered.

Allowed Attributes: Attributes that are allowed to be logged.

4. On the Inactivity you can specify:

Enable Inactivity Monitor: Check this box to enable inactivity monitoring. This will throw a non-transaction exception if the specified number of transactions haven’t been processed in the specified time interval.

Min. Transactions to Expect: The number of transactions to expect to be completed per monitoring interval.

Monitoring Interval: How often to check the specified number of transactions have been processed.

Times to Monitor: If set, monitoring will be done during the defined times of day. To ignore, set start and end time equally.

Days to Exclude from Monitoring: Inactivity monitoring will not occur on the days specified.

Include Errors in Transaction Count: If checked, transactions that attempted to start but failed at the Listener stage will also be counted.

5. On the Throttling you can specify:

Throttling Mode: The throttling mode to use for limiting the number of transactions or messages emitted by this Listener. “Timed” will limit transactions based on time intervals, while “Concurrent” will limit based on a concurrent number of transactions. “Concurrent” mode requires a Throttling Response Processor step later in your Interface workflow to acknowledge completion.

Throttling Mechanism: The mechanism to use for throttling message. “Blocking” prevents the Listener from continuing to process and emit messages altogether, while “Queued” pushes received messages into the Interface queue (or a default, in-memory queue).

Max Concurrent Messages: How many messages can be concurrently processed, either by time-based limits (“Allow X per Second”) or synchronous (“Allow X at any Time”)

Timed Emission Interval: The interval for time-based limits (“Allow X per X Timed Emission Interval”)

Synchronous Timeout Interval: The interval to wait for a synchronous response before failing.

6. Authentication: You can specify use Basic Authentication or not. If basic authentication is selected, you should specify a Username and Password. Authentication Realm is optional.

7. Proxy: If you use proxy, you can specify Proxy Host, Proxy Port, Proxy User and Proxy Password.

 

8. On the Encoding tab you can specify:

URL Param Encoding: the encoding to use for any parameters in the URL string

Error Response Encoding: the encoding to use when serializing a response message in the event of an error with the request

    to post comments

    This is a unique website which will require a more modern browser to work! Please upgrade today!

    Thanks!

    Our editors are notified.

    Close