Search allows searching for specific messages based on position in the queue, put time, header property testing and message content searching. In addition it allows search for specific complex types of messages such as XML and JSON.

Open

Open

As shown below, additional search options are available that allow:

• All Messages checkbox - Deselect to choose a range of messages to return

• Put Date Filter - Deselect the checkbox and set a range of the Put Time for selection. Note that the order of precedence as described in Order than x days applies to this range as well.

• Older than 30, 60, or n days - The order of precedence with this comparison is Orig Put Time if available otherwise Put Time. Only rows which are older than will be returned.

• Properties - Key:Value comparison of Header Property values, the pre-defined header values are provided but you can also enter any other property name as well. NOTE: For Andi_Original_Put_Time, don't include the trailing 0's. For example instead of 2024-12-21 05:14:45.471000000, use 2024-12-21 05:14:45.471.

Open

• Message Selector - A JMS search expression that allows for more natural way to search Header Properties. An example would be: Andi_NumberTimesRequeued > 10. You can use more than one expression at a time using parens to group expressions, for example: (Andi_NumberTimesRequeued > 10) AND (Andi_NumberTimesRequeued < 1000)

Open

• Text Search - Search the message content for a value, choose the operator which controls the comparison that will take place

Open

• After the first expression is added, another listbox will be enabled that allows choosing how the expressions will be joined. You will be able to select and|or which will allow you to create a more complex expression such as:

  contains <DesignatedArea>National Guard</DesignatedArea> or <DesignatedArea>National Guard</DesignatedArea>

Open

NOTE: Use JMS Message Selectors where possible and performance allows. This allows Artemis to only transfer messages which match the expression(s). Header Properties Expressions are verified after the message has been transferred to the client which can be slower. Be sure to try both to see which performs better.

Add from file allows adding 1-n terms in an or expression. The file must have each term on it's own line and they will be used as if you placed or between each value.

Open

In this example you can see the additional @Or() placed around the selected terms to allow Andi to check if the messages "contains Army or contains Navy or contains Marines or contains Air Force".

Open

The operators determine how the text will be compared.

• Contains - Anywhere in the message contains the value

  • Not Contains - The value does not exist in the message

  • = - The message contents equals the value

  • != - The message contents do not equal the value

• Message Type - Selecting XML or JSON will ensure that only those type of messages are returned. NOTE: XML or JSON MUST be selected to use the Xpath or JSON formatted display options.

Open

Open