HTTP Form/Post Listener – Listens for HTTP POST form requests.
When data is accepted through an HTTP Form/POST Listener, it is expected to arrive through a Web Form. The name-value pairs accepted through this Listener will be automatically converted into an XML format.
There are 4 tabs for this Listener: Basic, Advanced, Transaction Logging and WSDL
1. Basic: This tab allows you to specify a Request Path. The Request Path will be the path appended to the standard eiPlatform URL that will be used as an entry point to this interface. The “Wait for response” checkbox will let you determine whether or not to wait for a response (fire and forget or synchronous response).
Timeout (Seconds): Specifies how long (in seconds) the listener should wait for a response before timing out the connection.
2. Advanced: In 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, 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.
Servlet path: Specifies the HTTP servlet to listen at.
Process Multipart Body: Specifies whether or not to parse a multipart body request.
Respond with Multipart Body: Specifies whether or not the response should use a multipart body.
Keep Massage Body: Specifies whether or not the output of the process should be the original multipart body.
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 this tab, you can specify:
WSDL file: WSDL file that would be returned on request 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.