Browse Prior Art Database

Polling Optimization in Email Adapter by Pruning Filtering Criteria Disclosure Number: IPCOM000179581D
Original Publication Date: 2009-Feb-18
Included in the Prior Art Database: 2009-Feb-18
Document File: 6 page(s) / 36K

Publishing Venue



In a typical business integration scenario which uses e-mail adapters, e-mail filter rules are written to take only certain types of e-mails for processing, i.e., converting only specific e-mail messages that meet filtering criteria into business objects. There may be cases where there are many rules which check for similar patterns repeatedly. To enable an efficient processing of these rules, the number of rules processed should be reduced. This article discusses a method to compress the given set of filter rules so that the number of conditions checked per e-mail is low and hence will improve the overall polling efficiency of an e-mail adapter. This method can be applied to all implementations using a method similar to the Java Mail API for searching a mail server for e-mails with specific patterns.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 29% of the total text.

Page 1 of 6

Polling Optimization in Email Adapter by Pruning Filtering Criteria


    An email adapter (also known as an e-mail connector) is a software system that converts an incoming e-mail message into a business object that can be processed by business integration software. The process of waiting for an e-mail message on an e-mail server and converting an incoming e-mail in to a business object (hereafter referred to as BO) and pushing it into the integration software system is known as 'polling' or an e-mail adapter's 'inbound scenario'. The incoming e-mail message is referred to as an 'event'. Similarly, the adapter can also convert a business object into an email message that can be transmitted via an email server, and this process is referred to as the 'outbound scenario'.

    While configuring the e-mail adapter for polling, the user may adjust the configuration settings in such a way that the adapter processes only certain types of incoming e-mail messages, i.e., messages with specific content or header values. The search terms are specified as name=value or name!=value separated by commas. The 'name' refers to a valid e-mail header value /content, and value is a valid string. The commonly used e-mail header values are From(sender), To, Subject, Attachment size, etc. An example of an inbound filter is: process only those messages that are sent with a subject "Insurance Claim Form" or from an e-amil id . There can be multiple such conditions on different header values which can be "And"ed / "Or"ed creating logical expressions.

Example: From= AND subject contains "Insurance Claim Form" . They can be of the form




Page 2 of 6

    Some adapters for email use MatchAll and MatchSome filtering criteria for filtering events in inbound scenario. These use the AndTerm and OrTerm like SearchTerm Java mail APIs to search Mail folders.

Property Name Description Default Value

MatchSomeCriteria This field will contain conditions which are used as filtering criteria to selectively poll the Poll Folder. The conditions specified under this property will be ORed for the search. Options for NOTing will also be provided.

( No filtering )

( No filtering )


MatchAllCriteria =, MatchSomeCriteria = subject=test, from!

When both MatchAllCriteria and MatchSomeCriteria are mentioned, the final criteria evaluated is :

(( AND ((subject=test)OR(from!

Search Inbox using Filtering Criteria

In using Java Mail API searching on mail box, the SearchTerm classes in the API provide extensible search coverage on Mail Box. There are actually 22 different classes under packages which can be used for searching. Below is the list of basic fiel...