About Me

About Me
Working with SOA technologies , implementing solution using IBM BPM , IBM Integration Designer,IBM WODM and IBM DataPower

About me

View Mahesh Dondeti's profile on LinkedIn

upcoming posts on IBM Bluemix,Devops,Worklight,Node js.

Monday, 6 May 2013

Creating Custom Selectors with IBM Integration Designer(BPMv7.5)

Selector Component Overview:-

A selector is a dispatch pattern you use to dynamically determine which implementation of a component to invoke at runtime. Like a rule group, a selector has date range entries, selection criteria, and a default destination. That is, when a selector is invoked, it selects a destination using the selection criteria and date range entries. A destination could be any service-oriented component.


Process Server selectors let you determine dynamically which implementation to invoke at runtime based on a specified set of criteria, which is currently limited to dates. Although the standard selector implementation has the date limitation, with a little knowledge (and a little programming experience) you can create a custom selector that can use more varied selection criteria.

Scenario:-(Sample Solution)

How is this useful? You often need non-date selection criteria in real world Business Processes. For example, the company XYZ has a Web site from which it must calculate sales taxes differently based on the state from which the order is placed. XYZ company would like its online invoice process to select the correct tax calculation process, based on the state code entered on the order form by the customer.
A selector can use any Process Server Components as its outcome choices, including those defined in other modules. With a custom selector, you can write code that makes selections based on the values of some interface parameter passed into the selector. Other components can then use selectors that need to select behavior based on the criteria expressed in the selector.