| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
The Exception Listener component listens for exceptions from components running in a Fiorano network. It connects to the configured Enterprise Server and obtains details of all running Peer Servers whose names match the regular expression provided in the configuration. It then subscribes for messages on all topics, whose names match the regular expression in configuration, for each Peer Server identified. With the default values for regular expressions, the component listens for messages on topics whose names end with ON_EXCEPTION on all Peer Servers. It sends out messages received from configured topics on its output port. Messages sent out from the component have an additional string property ESBX_SYSTEM_SOURCE_TOPIC_NAME that contains the name of the topic to which the message was actually sent.
| Anchor | ||||
|---|---|---|---|---|
|
Figure 1: Configurations of Exception Listener
Component Configuration
Attributes
Validate input
...
Post Processing XSL Configuration
Post Processing XSL configuration can be used to transform response messages before sending it to the output port.
| Note |
|---|
If the Input validation is disabled, it does not validate the input and thereby increases the performance. However, it may cause undesired results if the input XML is not valid.Refer to the Post Processing XSL Configuration section under the Common Configurations page for details regarding Pre Processing XSL configuration and Post Processing XSL configuration (below). |
Error Handling Configuration
Please refer Error Handling section in Common Configurations.
Connect only to host peer server
This property determines whether the component should listen for messages only from topics on the Peer Server on which the component is running.
...
- no
The component listens for messages from the configured topics on configured Peer Servers. When this value is selected an Enterprise Server connection to fetch the details of Peer Servers and the regular expression for filtering Peer Servers are needed and hence, properties Pattern for peer server name, Server URL, Backup Server URL, JMS User Name, JMS Password and Server Call Timeout are shown.
Pattern for peer server name
This property determines the Peer Servers from the Fiorano network that have to be monitored. The Fiorano network from which Peer Servers are filtered is determined by the Enterprise Server details provided against properties Server URL and Backup Server URL.
...
Pattern matching condition in Figure 3 matches and selects all Peer Servers whose name has English alphabets only, but does not start with B.
FES Connection Configuration
Click the Ellipsis 
button to set the configuration.
...
The URL of Enterprise Server to which the Peer Servers that have to be monitored are connected. For more information, refer Connection to Enterprise Server section.
Back Up Server URL
The alternate URL that should be tried for connecting to the Enterprise Server if the Enterprise Server cannot be connected to using the URL mentioned against property Server URL. For more information, refer Connection to Enterprise Server section.
| Note |
|---|
In case of Enterprise Servers in HA mode, this should point to Secondary Server URL if the primary is set against Server URL property and vice-versa. |
...
The user name to connect to the Enterprise Server. For more information, refer Connection to Enterprise Server section.
JMS Password
The password to connect to the Enterprise Server. For more information, refer to Connection to Enterprise Server section.
Server Call Timeout
Sets the timeout for the calls made to the Enterprise Server.By default it is set to 180 Seconds.
This value should be increased to avoid timeout with the Enterprise server while launching Components.
For more information, refer to Connection to Enterprise Server section.
JNDI details
InitialContextFactory
InitialContextFactory implementation class name which can be used to create Initial Context that is used to lookup Peer Server's administration object. This is required to find the list of topics created on Peer Server.
| Note |
|---|
This property need not be changed. |
JNDI User Name
The user name required to create Initial Context for looking up objects on Peer Server. This user should be present on each of the Peer Servers and have permission to perform lookup for JMS objects.
JNDI password
The password for user provided against property JNDI User Name required to create Initial Context for looking up objects on Peer Server.
Admin Configuration
Click the ellipsis button to configure admin credentials.
Admin User Name
The user name required to create subscribers on topics on specified peer servers. This user should be present in admin user group.
Admin Password
The password for user provided against property Admin User Name required to subscribe to topics on specified peer servers.
Regex of Topic Name
This property determines the topics on Peer Servers from the Fiorano network that have to be monitored. Refer help for property Pattern for peer server name to specify pattern matching conditions for topic names.
Time Slice To Ping Peers
This property determines the time interval in milliseconds after which the component has to periodically poll for changes in Peer Servers and topics. At every poll interval, the component does the following:
- Fetches all Peer Servers in Fiorano network or just the Peer Server on which the component is running based on property Connect only to host peer server.
- For each Peer Server name that matches the pattern matching conditions defined, checks if the Peer Server is available in network.
- If the Peer Server is not available in the network but the component has created and cached a connection to the Peer Server during previous polls, then the connection is discarded.
- If the Peer Server is available in the network, but component has not created and cached a connection to the Peer Server during previous polls, then a new connection is made and cached.
- For each Peer Server that is available in network and connected to the component, all the topics are listed.
- If the topic matches the pattern matching conditions defined and is not in the list of topics to which the component subscribes, a subscription to the topic is made and a message listener is set.
Admin User Name
The user name required to create subscribers on topics on specified peer servers. This user should be present in admin user group.
Admin Password
The password for user provided against property Admin User Name required to subscribe to topics on specified peer servers.
Use Durable Subscriptions
Saves messages for an inactive subscriber and delivers these saved messages when the subscriber reconnects. Select the check box to create durable subscribers.
Threadpool configuration
Click the Threadpool Configuration ellipses button to configure the Threadpool Configuration properties.
| Tip |
|---|
Refer to the Threadpool Configuration section in the Common Configurations page for descriptions. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Configure the Exception Listener as described in Configuration and Testing section; configure a CBR with any schema. Use feeder to send an improper message to the CBR and display component to check the output message send by Exception Listener (which is picked from the exception port of CBR) on its output port.
...