This Listener allows the user to specify a Generic Socket based protocol over which data will be received into the eiConsole environment.
You will see four different tabs: Basic, Advanced, Transaction Logging and Scenario.
1. Basic: The Port specifies the inbound port to which the external system will connect. The Char Set configuration option specifies the character set that the source system will use to write data through into the eiConsole.
2. Advanced: This tab has the options to initialize the Listener on trigger only.
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.
Keep Socket Open for Response: If true, this will leave socket open and store socket in a transaction attribute ‘com.pilotfish.eip.socket.CurrentSocket’.
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. Scenario: This tab allows you to configure the protocol that the Listener uses to accept data.