Using Hints in Filters
Hints are used to further define a filter. You add hints to the end of a subscription in the Filter field.
Hints use the following syntax:
{hint: HintName=Value}
The table below identifies the HintNames that you can use with a document subscription.
Hint | Description |
IncludeDeliver | When set to true, the filter applies to documents that are delivered to the client and documents that are delivered to the subscription queue. By default, filters are only applied to documents that are delivered to the subscription queue. |
LocalOnly | When set to true, the filter is applied only to documents that originate from the webMethods Broker to which the Integration Server is connected. Documents originating from a different webMethods Broker are discarded. |
DeadLetterOnly | When set to true, a deadletter subscription is created for the document type specified in the webMethods messaging trigger. The webMethods messaging trigger that subscribes to this hint receives messages that do not have subscribers. To learn more about detecting deadletters, see the webMethods Broker Java Client API Reference. |
Keep the following points in mind when you add hints to filters:
Hints must be added at the end of the filter string in the
Filter field.
Hints must be in the following format:
{hint: HintName=Value}
For example, the following filter will match only those documents that originate from the webMethods Broker to which the Integration Server is connected and the value of city is equal to Fairfax.
%city% L_EQUALS "Fairfax" {hint:LocalOnly=true}
A filter can also contain a combination of subscription hints. For example, the following filter will match only those documents that do not have a subscriber and that originate from the
webMethods Broker to which the
Integration Server is connected.
{hint:DeadLetterOnly=true} {hint:LocalOnly=true}