x

To configure an Internal Listener:

1. Ensure that iWay Service Manager is running.

   On Windows, you can start iWay Service Manager by clicking Start, selecting Programs, iWay 6.0 SM, and then Start Service Manager for the configuration you are currently using.

   For more information on starting and stopping iWay Service Manager, see the iWay Service Manager User Guide.

2. Open a browser window and point to the following URL:

   http://host:port/ism

   where:

   host

   Is the host machine on which iWay Service Manager is installed.

   port

   Is the port on which iWay Service Manager is listening. The default port is 9999.

   On Windows, alternatively, you can click Start, select Programs, iWay 6.0 SM, and then click Console.

   A login dialog box opens.

3. Type a user name and password for the configuration you are using, and click OK.

   The iWay Service Manager Administration Console opens.

4. Click Registry in the top pane, and then click Listeners in the left pane.

   The Listeners pane opens, as shown in the following image.

   

   The table provided lists all the previously configured listeners and a brief description each.

5. Click Add.

   The Select listener type pane opens, as shown in the following image.

   

6. Select internal from the Type drop-down list and click Next.

   The Configuration parameters for the Internal Listener pane opens, as shown in the following image.

   

   Note: The parameters prefixed with a (*) in the listener configuration pane are required.

7. Provide the appropriate values for the Internal Listener parameters.

   For more information, see Internal Listener Configuration Parameters.

8. Click Next.

   As shown in the following image, you are returned to the Select listener type pane.

   

9. Enter a name for the Internal Listener and description (optional).
10. Click Finish.

    You can now use this listener as part of your channel configuration where the business logic will be applied to the received messages.

x

The following table lists and describes parameters for the Internal Listener.

Parameter	Description
Name of internal queue	The queue name is used to identify the internal message listener destination.
Persistent	If set to True, the connection is maintained when the client requests to do so. Otherwise, the connection is closed.
Safestore location	Full path to the listener. It is the unique directory in which persistent messages are safestored.
Compress Persistence	Compression of persisted data (has size/performance impact).
Low Mark	If set, if queue length falls below this, named listener(s) are activated.
High Mark	If set, if queue length falls above this, named listener(s) are passivated.
Control list	List of masters (comma separated) to start/stop on low/high mark points.
External Mark	If set, if queue length falls above this, memory optimization is used. Otherwise, performance is optimized.
Whitespace Normalization	Specifies how the parser treats whitespace in Element content. Choose preserve to turn off all normalization as prescribed by the XML Specification. Choose condense to remove extra whitespace in pretty printed documents and for compatibility with earlier versions.
Accepts non-XML (flat) only	If set to true, listener expects flat (non-XML). Preparsers do not run.
Optimize Favoring	Selection of memory is useful for large input document.
Multithreading	Number of documents that can be processed in parallel.
Maximum threads	Parallel threads can grow to this count automatically on demand.
Execution Time Limit	Time limit for document execution(in seconds) before it is terminated (also see system property "kill interval").
Polling Interval	Interval at which to check for new input.
Default Java File Encoding	Default encoding if incoming message is not self-declaring (i.e. XML).
Agent Precedence	Changes order by which engine selects agents. Normally document overrides listener. This is used to manage iWay documents.
Always reply to listener default	If set to true, the default reply definition is used in addition to defined replies.
Error Documents treated normally	If set to true, error documents will get processed by any configured pre-emitters.
Listener is Transaction Manager	If set to true, agents run within a local transaction managed by the listener.
Record in Activity Log(s)	If set, activity on this channel will be recorded in the activity logs, else the activity will not be recorded.