BAM deployed on EAP6 is accessible on URL http://host:port/bam-app
I do not consider this name - "bam-app" - appropriate for the product, what about some better naming? Maybe "dashboards" or "bam" ?
Moreover, when using deployable binaries (for example on tomcat7) BAM is accessible on URL http://host:port/dashbuilder.
At least I would expect consistent naming in URL across all supported containers.
Second inconsistence in naming is between business-central (BPMS) and jboss-brms (BRMS). In fact, it is the same application (with more or less features), so the naming should be identical in both BRMS and BPMS product => no "jboss-brms", only "business-central" or whatever.
>> BAM deployed on EAP6 is accessible on URL http://host:port/bam-app
The preset context is /dashbuilder and where is deployed. The issue is that the links in the home screen are wrong, and the jBPM Uberfire panel has not yet been integrated. We are fixing both issues during this week.
So the right path will be: http://host:port/dashbuilder
The dashbuilder war url is recovered to http://host:port/dashbuilder in the latest DR5.
qe_test_coverage: see the summary