Open zhangs-ibm opened 6 years ago
The BPM Analytics do not support the event type generated by the service flow, please update the subscriptions at the ${BPM_ROOT}/BPM/Lombardi/tools/def/SampleConfigureJSONEventsToJMS.py to filter out the service flow event. Change the subscription to:
subscriptions = [
'*/*/BPD/*/*/*/*'
]
Then run:
wsadmin.sh -lang jython -f EnableBPMAnalytics.py --update=subscriptions
Since the service flow events are emitted at the Elasticsearch, the data need to be cleared before move forward.
Hello:
I've tried the sugested solution and executed the script for the subscriptions update. It failed. Then I tried to recreate the configuration using the modified SampleConfigureJSONEventsToJMS.py file. The same exception was thrown.
I'm using ES version 5.5.3 and BPM 8.6.0 with the last commulative fixpack.
Would you please help us resolving the issue? I'm very interested in making this work for the most recent version of BPM.
Hi, The same exception was thrown. is the exception as at the EventSummaryAgent or the exception when run the EnableBPMAnalytics.py --update?
Would you paste the content of the defconfig.xml at the cell level(BPM_ROOT\profiles\DMGR_NAME\config\cells\CELL_NAME) at here?
Just before submit the information you asked (btw thanks for the answer) I reviewed the defconfig.xml file. I noticed that there was a dupplicate ProducerFor_jmsListenerForJSON entry one with the wrong configuration and another one with the correct one.
Once I deleted that file, fully resync the node and recreated the configuration using the modified SampleConfigureJSONEventsToJMS.py file everthing works fine.
Thanks for the hint with the defconfig.xml file.
The one thing I couldn't make to work is the wsadmin.sh -lang jython -f EnableBPMAnalytics.py --update=subscriptions
command. I had to recreate that configuration from the very beggining, deleting the different resources I had created the first time and use for a second time the Enable IBM BPM Analytics instrucctions in the pdf file you supplied.
Glad to hear the issue is solved, when run the EnableBPMAnalytics at second time, there is an redundance entry created, this issue will be fixed at the V860.201803.
If you run the --update with exception, this ifix can help you: https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Express&fixids=8.6.0.201712-WS-BPM-IFJR58916&source=SAR&function=fixId&parent=ibm/WebSphere
Hi,
I have the same exceptions but seems that my defconfig.xml does not contains duplicate.
Also I'm using ES version 5.5.3 and BPM 8.6.0 with the last commulative fixpack.
Please help me for the solutions.
Thanks
Best Regards.
this is my defconfig.xml
<?xml version="1.0" encoding="UTF-8"?>
@gabrigam , if you got the same exception as the description of this issue, it cased by the EventSummaryAgent can not process the new ServiceFlow type event. You need filter out this type of events at the DEF configuration:
Please update the subscriptions at the ${BPM_ROOT}/BPM/Lombardi/tools/def/SampleConfigureJSONEventsToJMS.py to filter out the service flow event. Change the subscription to:
subscriptions = [
'*/*/BPD/*/*/*/*'
]
Then run:
wsadmin.sh -lang jython -f EnableBPMAnalytics.py --update=subscriptions
BTW, you need this ifix applied before run the EnableBPMAnalytics.py --update: If you run the --update with exception, this ifix can help you: https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Express&fixids=8.6.0.201712-WS-BPM-IFJR58916&source=SAR&function=fixId&parent=ibm/WebSphere
Hi zhangs,
Thanks for your Help.
Now all works fine.
Gabriele
HI zhangs,
Please I need your help again.
I receive some errors during the dashboard installation on Kibana.
In attachements some images related to the installation steps.
Thanks in Advance.
Best Regards
Gabriele images.zip
Hi zhangs
Resolved.
[Kibana 5.5.x and later version] Enter bpm-summary*
I remove * and works fine.
Thanks
Gabriele
If your process include service flow, the EventSummaryAgent will fail with the following exception: