Title: Installing the EAP6 package

Describe the issue:

• Sometimes customers do not interpret these lines in the documentation correctly and attempt to install the BPMS/BRMS deployable installer on an existing EAP6.1.1 installation where they have already installed an earlier release of BPMS/BRMS (e.g. version 6.0.0/6.0.1/6.0.3) .
  ~~~
  To install the deployable package for an EAP that has yet to be configured,...
  ...
  To install the deployable package for a previously configured EAP,...
  ...
  Ensure the target EAP does not include a deployment with a colliding name. Copy the folder jboss-eap-6.1/standalone/deployments into the EAP_HOME directory from the BPMS distribution. ...
  ~~~

As of BPMS/BRMS 6.0.x releases we do not have any smart update tool for this product , hence it is a natural tendency amongst customer community to simply apply the latest versions of these products on an already installed BPMS)/BRMS set-up for a quick set-up. Which leads to many issues.

Suggestions for improvement:

• My suggestion to the documentation team is to enhance this topic and put a WARNING message (like a dialogue box appearing in this section of documentation) to warn customers not to attempt to install this deployable version of BPMS/BRMS on top of an existing BPMS/BRMS set-up. This should prevent customers from facing further complications due to wrong installation.

Additional information:

• DOC URL:

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Installation_Guide/index.html#Installing_standalone_package