eStudio allows you to define Selectors for the data flow through an event route. The Selectors can be defined based on any one of the following:

  • Sender of the message
  • Value of a JMS property in the message
  • Using an XPath defined on the incoming XML message
  • Using an XPath defined on the Application Context (in case Application Context is defined).

Below-mentioned are ways to configure the Selector:

  • Sender selector: Filters the messages based on the source/traversed components. Allows messages sent or forwarded by the components specified in the condition. Condition can be specified by selecting single or multiple components.
  • JMS selector: Filters the messages based on the JMS headers. Allows messages that contain the headers matching the specified the condition. Conditions should be specified using SQL-92 syntax.
  • Message Body XPath selector: Filters the messages based on the message body. Allows messages whose message body content matches the specified XPath condition. Conditions should be specified using valid XPath expression. If the source port of the route is associated with the schema then user can use the XPath Editor to specify the condition else need to specify the condition manually.
  • Application Context XPath selector: Filters the messages based on the application context.It allows messages whose application context content matches the specified XPath condition. Conditions should be specified using valid XPath expression. If the source port of the route is associated with the schema then user can use the XPath Editor to specify the condition else need to specify the condition manually.
Icon

In case of multiple selectors defined on a route, only those messages which match (while filtering) the criteria set on selectors will be allowed to pass through the route.

Icon

When a selector is defined on a route, a filter icon appears on the route, next to the Route Name as a visual indication.

Adaptavist ThemeBuilder EngineAtlassian Confluence