This Listener allows you to take a data stream in through a WSDL defined Web Service, which includes one method that accepts all of the inbound data as a single string parameter. This is the simplest way to implement a WSDL defined Web Service.
1. Basic – First, specify the Service Name. This will be used to differentiate this Web Service against others in the system. Next, add the Axis URL. Web Services are deployed using the Apache Axis platform. In cases where the Axis URL cannot be discovered automatically by the eiPlatform, you can enter the URL directly. This is typically not required. The Allowed Methods line will list the allowed platforms. To edit this, choose the icon to the right of the line.
2. Advanced – The advanced dialogue lets you specify the port on which the admin service is running, as well as if this Listener should be initialized only when it is triggered from an external source.
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 that the Listener created them in.
Port: Specifies the port to listen at: 8080 by default.
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. Called By – this tab allows you to check if the current route is called by a RouteToRoute transport and if so, by which one exactly.
Called By: the Routes called into this listener (if there are any).