How to run multiple instances by copying standalone directory in JBoss EAP 6.x, 7.x, and 8.x?

Issue

• Is it possible to run multiple server instances by copying standalone directory in EAP 6 which is similar to EAP 5 copying profile (all, default, etc) directory?

• In EAP 5.x, it is possible to start more than one server with the same binaries. For this, we pass the -c Option to run.sh. Is this still possible with EAP 6.2? Or do we need to install the binaries for every server we want to start?

• What's best approach to create multiple instances for EAP 6.2.2 version?

• Is it possible to run the JBoss EAP server when the folder name of standalone directory is changed to abc?

• Is it recommended to run multiple server instances by copying standalone.xml file and changing the location of log files as below :

• what are the best practices on running multiple eap 6 instances in standalone mode

JBoss-EAP-6
standalone
├── configuration
│   ├── standalone-test1.xml
│   └── standalone-test2.xml
├── data
├── deployments
│   ├── test1.war
│   └── test2.war
├── log
│   ├── test1
│   │   └── server.log
│   └── test2
│       └── server.log
└── tmp

• How to install JBoss EAP so that as much of the footprint as possible is shared across instances

• Is it possible to start multiple JBoss instances from one physical jboss directory?
  - Assuming JBoss is installed under C:\tools\jboss_eap_6.4.1 and we need 6 different instances/configurations named 'node1' ...'node6'. Can we copy the $JBOSS_HOME/standalone folder to $JBOSS_HOME/node1, $JBOSS_HOME/node2 and so on?
  - Are the following jboss artifacts in $JBOSS_HOME shareable? i.e. appclient, bin, bundles, docs, module, welcome-content, jboss-modules.jar, version.txt etc

• How to create multiple standalone Servers in a Single Jboss installation ?

• What's best approach to create multiple instances for EAP 7 version?