Troubleshooting the BPM event emitter
To better follow up the activity of the BPM event emitter,
you can enable tracing. If events are not flowing to the JMS queue
or to Kafka, use the check lists to ascertain proper JMS configuration.
Enabling tracing for BPM event emitter and Machine Learning Server
To help you troubleshoot any issue that might occur with the BPM event emitter and Machine Learning Server , you can enable detailed tracing by adding a package to the trace definition in the WebSphere® Application Server administration console.
Resolving events not flowing to the JMS queue
If you observe that no events are flowing to Kafka, the cause might be with the JMS queue. Check the DEF configuration, the status of the messaging engine, and the configuration of the Java™ Message Service (JMS) resources.
Resolving events flowing to the JMS queue but not to Kafka
If you observe that events are flowing to the JMS queue but not to Kafka, check whether the BPM event emitter application is installed, whether the emitter is not paused, and whether events are retried after a JMS exception.
Troubleshooting JMS destination issues
If you observe that events are flowing to the JMS queue but not to Kafka, also the JMS destination might need examination.
Uninstalling the BPM event emitter
You can temporarily or definitively uninstall the BPM event emitter, typically to prevent cluttering Elasticsearch data with the result of tests and other quality assurance actions in the IBM Business Automation Workflow environment of your IBM Business Automation Insights deployment.