IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > (Deprecated) Routing with Selectors
(Deprecated) Choosing components without using a selector
When used with time-based routing, the selector is, in essence, a scheduling tool. You use it to route an operation to a component for a specific period of time. To achieve the same results on a daily, or a periodic basis, you can use a combination of a business process and a rule set as described here.
In a typical selector, the routing algorithm uses the date and time settings to determine which component to route an operation for implementation.
For example, suppose you have an operation called getDiscount. By default, the selector may route this operation to a component called NoDiscount, but during the Christmas season the routing may go to a ChristmasDiscount component.
What if you want to invoke a different operation at a different period of time each day? Perhaps you might want to route an operation to one component during business hours, and another component during off hours. The selector does not support such periodicity, so to achieve the required ends, you will have to take advantage of the close relationship of the IBM Integration Designer family of tools, and use a combination of a BPEL process and a rule set. The procedure is outlined below.
- Create a rule group component which captures your routing policy. Keep in mind, that you will be able to modify the behavior of the rule set in the runtime environment using the web client.
- Create a BPEL process that invokes the rule set.
- Drop a switch activity into the process that takes the result from the rule set, and invokes the appropriate component.
This image represents what the completed process will look like.
