Regulation of message flows in WebSphere Process Server – Part 2
Phani_Madgula 060000NHGT Visits (3227)
In my Part 1 posting on this topic, I had put forward the following questions.
The Figure 1 below helps to recap the scenario that was discussed.
Figure 1. Integration scenario
I answered question (1) in my previous posting and now I will try to answer question (2).
I referred to this article for the solution. The answer to the question can be provided as illustrated in the below Figure 2.
Figure 2. Regulating message flow using Scheduler
Here, two new components are introduced between Integration module and the target end point (WebService). These are Scheduler component and the end point stub. The flow of messages is as follows.
The Scheduler component does all the work of regulating the message flow. It acts as the valve which opens the message flow of certain quantity at certain intervals. These Scheduler interval and quantity of messages can be made configurable. For more information about Schedulers, visit the information center.
Currently, the store-and-forward does not provide fine grain control over changing the status of the control points to either store or forward. For example, it does not provide an API to programmatically change the status. This improvement is something that can be desirable to be expected in the future versions of WebSphere Process Server. Until that time, I proceed with the solution explained above.