@harish_malavade Are your process applications are Spring based applications?
If yes, you can try camunda-spring-event-bridge like below:
@Slf4j
@Component
public class CamundaEventListeners {
@EventListener
public void onTaskEvent(DelegateTask taskDelegate) {
log.info("Handling mutable DelegateTask:{}", taskDelegate.getTaskDefinitionKey());
}
@EventListener
public void onTaskEvent(TaskEvent taskEvent) {
log.info("Handling immutable TaskEvent:{}", taskEvent.getTaskDefinitionKey());
}
@EventListener
public void onExecutionEvent(DelegateExecution executionDelegate) {
log.info("Handling mutable DelegateExecution:{}", executionDelegate.getCurrentActivityName());
}
@EventListener
public void onExecutionEvent(ExecutionEvent executionEvent) {
log.info("Handling immutable ExecutionEvent:{}", executionEvent.getProcessDefinitionId());
}
@EventListener
public void onHistoryEvent(HistoryEvent historyEvent) {
log.info("Handling mutable HistoryEvent:{}", historyEvent.getEventType());
}
}
The process engine can be hooked-up to the Spring event bus. We call this the “Spring Eventing Bridge”.
camunda.bpm.eventing.execution=true
camunda.bpm.eventing.history=true
camunda.bpm.eventing.task=true
By default, the Spring eventing is enabled by a engine plugin.