Description of problem: When dashbuilder is deployed on EWS 2 (tomcat 7), the role names in select are: Administrator, End User, Anonymous. But they should be (as they are when dashbuilder is deployed on EAP 6.1): Administrator, Analyst, Anonymous Version-Release number of selected component (if applicable): BPMS 6.0.0 ER4 deployed on EWS 2 (tomcat 7). How reproducible: Always Steps to Reproduce: 1. When dashbuilder deployed on tomcat, navigate to General options > General permissions (or to any other permission management page like Workspace permissions, Page permissins, Panel permissions) Actual results: In Permission assignation section, in the select for choosing role there is 'End User' -> should be 'Analyst' Expected results: The roles in select should be named the same both on EAP 6.1 and on EWS containers. Additional info: Please also take into consideration existing bug, that manifested itself when deployed on EAP6 (https://bugzilla.redhat.com/show_bug.cgi?id=1019317)
The dashbuilder generic repo is located at https://github.com/droolsjbpm/dashboard-builder. The generic dashbuilder artifacts are generated from there. Generic dashbuilder uses "Administrator" and "End User" as default roles and it contains only the Showcase workspace. On the other hand, we have the dashbuilder distribution for jBPM. The repo is located at https://github.com/droolsjbpm/jbpm-dashboard. This is the repo that must be used to generate the artifacts for the BPMS distribution. The ER4 distribution for EAP 6.1 http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER4/jboss-bpms-6.0.0-redhat-4-deployable-eap6.x.zip it's OK as it contains the dashbuilder distribution for jBPM: * The roles are well defined. "Administrator" and "Analyst" (see jboss-eap-6.1/standalone/deployments/dashbuilder.war/WEB-INF/web.xml) * It also contains the jBPM dashboard stuff (existing files jboss-eap-6.1/standalone/deployments/dashbuilder.war/WEB-INF/etc/appdata/initialData/jbpm*.xml) The ER4's Tomcat 7 distribution http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER4/jboss-bpms-6.0.0-redhat-4-deployable-generic.zip IS NOT OK. I've looked into the contents of that file and it NOT contains the dashbuilder distribution for jBPM. It contains the generic one. * It contains the roles of the generic distribution "Admnistrator" and "End user" (see /dashbuilder.war/WEB-INF/web.xml) * The jBPM dashboard files are missing /dashbuilder.war/WEB-INF/etc/appdata/initialData/jbpm*.xml I think ER4 distribution for tomcat should be reviewed to ensure the dashbuilder for jBPM artifacts are included instead of the dashbuilder generic ones.
*** Bug 1026345 has been marked as a duplicate of this bug. ***
The problem is still present in ER5 (only EWS binaries are concerned - binaries for EAP are ok in this regard) - the jBPM Dashboard workspace is not present and the roles are named as described in problem Description.
Can you confirm the binaries for EWS are using the right dashbuilder war. There should be no difference, unless the dashbuilder.war is being packaged instead of jbpm-dashbuilder.war. There's also the requirement for it to be named dashbuilder.war to provide the context /dashbuilder DAvid, can you verify this?
I've downloaded the ER5 from here: http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER5/jboss-bpms-6.0.0-redhat-5-deployable-generic.zip ... and the same issues encountered in ER4 remain: * It contains the roles of the generic distribution "Admnistrator" and "End user" (see /dashbuilder.war/WEB-INF/web.xml) * The jBPM dashboard files are missing /dashbuilder.war/WEB-INF/etc/appdata/initialData/jbpm*.xml ER5 distribution for tomcat should be reviewed to ensure the dashbuilder for jBPM artifacts are included instead of the dashbuilder generic ones.
Yes, this is a bug in BPMS assembly code. Could we target this for ER6?
Fixed in http://git.app.eng.bos.redhat.com/ip.git/commit/?id=9b04771f9d9a5e78a25c4b7d02cdfa81e2927c7f
Ok, verified with BPMS ER6 - currently there are 6 roles available for permission configuration in dashbuilder: 5 business-central ones (admin, analyst, developer, manager, user) + anonymous
*** Bug 1040143 has been marked as a duplicate of this bug. ***