Whether Bonita has the capability to act as a Listener or not?
1 answer
Hello, it would be good to precise your use case(s) a little bit. But, as a general answer - yes, Bonita could do that. There are exposed APIs (REST or Java) that allow to start a process, execute a task etc, from an external system. This means that you could have a process that is listening for an external call. Let me know if this answers your needs, Haris
Comments
Requirement is : whenever a new message will be pushed to the MQ, based on message content different bonita process will be instantiated. Current implementation: whenever a new message will be pushed to the MQ, an external Listener will receive the message and based on message content different bonita process will be instantiated.
Question : Instead of using external Listener whether we can use Bonita OOTB capability to listen the message and instantiate different Bonita process.
Your current implementation is a good choice, there is no OOTB feature that would help you to cover this use case in a better way. Note that you might create a timer-based process with an MQ connector, that would periodically check for MQ messages and instantiate processes (if applicable for your case, with regards to the required frequence, number of instances etc.).
Thanks haris for reply. So in that case we have to write create a bonita process with an intermediate timer event and after the timer in a service task we have to create a custom MQ connector wich will read the MQ message and then again go to the same intermediate timer event. Is it the approach you are talking about?
I was rather thinking about a process with a start timer event, that will make start your process regularly. And then the process would have a service task with an MQ connector and you would do anything you need.
In that case if the timer frequency is high a huge number of process instancees will be created. I think this will have impact on performance. Is there any specific reason for selecting start timer event?