Title: Setup JMS resources
Describe the issue:
The example pattern JMS destations in the documentation is incorrect: `jms/queue/KIE.AUDIT`. The deployment artifacts in the WAS8 business-central.war file expect the following JNDI names for the JMS queues since they are referenced specifically by configuration files. There is flexibily in the naming of connection factories or activation specifications:
jms/KIE.AUDIT ./WEB-INF/ejb-jar.xml & ./WEB-INF/classes/jbpm.audit.jms.properties
Instead, the documentation for installing BPMS on WAS8 states the following for how to configure the JMS resources.
> Enter the name (example: KIE.AUDIT) and the JNDI name
> (jms/activation/KIE.AUDIT) and then making sure that
> Queue is selected as the Destination type, enter the
> corresponding queue you created in the previous step
> (example: jms/queue/KIE.AUDIT).
Suggestions for improvement:
Call out specifically that the queue names must match the `jms/QUEUENAME` pattern, and why.
Thanks. Changes made to section Setup JMS Resources with a note added to explain the correct choices.
When the docs are built next, I will update with a link to verify.
Moving this to MODIFIED.
The Setup JMS Resources section can now be reviewed on the documentation stage  to confirm the changes made to reflect the correct queue names.
Moving this to ON_QA.
In case all examples should show the default naming, in chapter 3.5. Add custom JVM properties, a property defining a response queue must be changed too:
Excellent point Radovan. I have made the change and it can be verified here for BPMS  and here for BRMS .
"Generic JVM arguments field" in BPM Suite guide contains as example -Dkie.services.jms.queues.response=KIE.RESPONSE.ALL, which is in my opinion misleading. JNDI name must be provided as a value for this property, which is - by default - jms/KIE.RESPONSE.ALL. KIE.RESPONSE.ALL without the jms/ prefix could be understood as a logical name used to register the queue in WebSphere.
Agreed. :) Have made the change and it can be checked here  (in about 15 minutes time).
Moving back to ON_QA.
This is now live on access.redhat.com .
Closing this bug.