Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

InitialContextFactory

...

Similarly, regular expressions can be used to match the peers on which the exception listener has to subscribe to.

Example

For example, consider four event processes EP1, EP2, EP3, and EP4.

Scenario 1.1

To fetch exceptions for EP2 and EP3 (ignore exceptions for EP1 and EP4), recommended TopicRegex is:

Code Block
(EP2[A-Za-z0-9_]*ON_EXCEPTION|EP3[A-Za-z0-9_]*ON_EXCEPTION) = true
Tip

logical operation '|' is used in regex.

Scenario 1.2

Scenario 1.1 can be performed in a different way as given below. This method is helpful when there are more number of EPs.

Ignore exceptions for EP1 and EP4 (fetch exceptions for EP2 and EP3) with TopicRegex as below:

Code Block
[A-Za-z0-9_]*ON_EXCEPTION=true
EP1[A-Za-z0-9_]*ON_EXCEPTION=false
EP4[A-Za-z0-9_]*ON_EXCEPTION=false
Info
  • First one in the above listens to all exceptions across EPs, while the second and third ones are to ignore listening.
  • logical operation '|' can be used in regex, however, expressions are separated by lines at this instance. It is better to have separate lines when there are more number of expressions.
Scenario 1.2

To fetch exceptions for EP4 (ignore exceptions for EP1, EP2 and EP3), recommended TopicRegex is:

Code Block
EP4[A-Za-z0-9_]*ON_EXCEPTION=true
Scenario 1.3

To fetch exceptions for EP1, EP2, EP3 ( ignore exceptions for EP4), recommended TopicRegex is

(EP1[A-Za-z0-9_]*ON_EXCEPTION|EP2[A-Za-z0-9_]*ON_EXCEPTION|EP3[A-Za-z0-9_]*ON_EXCEPTION) = true

Tip

logical operation '|' is used in regex.

Scenario 2

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.

...

Adaptavist ThemeBuilder EngineAtlassian Confluence