Log out?

HTTP Form File Post Listener

HTTP Form File Post Listener – Monitors a specified local HTTP path for POST requests with ‘File’ attachments. Attachment is used as input data.

Select the HTTP Form File Post Listener from the Listener Type drop-down.

This Listener has 6 tabs: Basic, Advanced, Transaction Logging, WSDL, Authentication and Resources.

1. Basic: At the Basic tab you can specify:

Request path: Specifies the HTTP path to listen at, modified by application server.

Timeout: Specifies how long the listener should wait for messages which are interrupted before timing out the connection.

2. Advanced: At the Advanced tab you can specify:

Initialize on trigger only: If enabled, Listener doesn’t start up until a trigger initializes it.
Allow command-line invocation: If enabled, Listener can be invoked using the CLI client application.
Restart on listening error: If enabled, 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.

Synchronous: Specifies whether or not a response is expected.

Require SSL: If selected, plain text requests will be rejected.

HTTP Headers: Allows specification of HTTP header name-value pairs to use in synchronous response.

3. Transaction Logging – This tab allows us to enable transaction events logging. That data can be logged by a TransactionEventListener.

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

Log Transaction Attribute – if enabled, logs transaction attributes.

Log Transaction Data – if enabled, logs transaction data body.

Log Transaction Data Base64 – if enabled, logs transaction data body as Base64.

4. WSDL: In the WSDL tab you can specify:

WSDL file: WSDL file that would be returned on request that ends with “?wsdl”. If you want to create new or edit existing files, you can click Edit/New to open the WSDL editor.

WSDL Content Type: specifies the content-type to send with the WSDL file.

Validate At The Listener Level: If selected, the Listener will validate incoming message against XML schema in defined WSDL.

5. Authentication: In the this tab you can specify usage of Basic Authentication.

Authentication File: A properties file  containing usernames and passwords for basic authentication.

Authentication Realm: The realm for basic authentication.

6. Resources – In the this tab you can specify:

Additional Resources: Specifies any additional content to be served up and the URL fragment at which they are served up.

    to post comments

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


    Our editors are notified.