JBoss Administration and Configuration Guide note

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/6.4/html/administration_and_configuration_guide/sect-start_and_stop_jboss_eap_6
1.  Start JBoss as a Standalone Server
EAP_HOME\bin\standalone.bat
    To list all available parameters for the start-up scripts, use the -h parameter:
EAP-6.4.0\bin>standalone.bat -h
    Run multiple instances of JBoss EAP standalone servers on a single machine:
Create a copy of the EAP_HOME/standalone/ directory directly under EAP_HOME
Start each JBoss EAP standalone instance by specifying node name, IP, port offset...
If you would like to manage two nodes at once or two nodes that have the same configuration,
you are recommended to run them in a managed domain instead of running a standalone server.
Using an Alternate Configuration file for a Standalone Server in Microsoft Windows Server
C:\EAP_HOME\bin> standalone.bat --server-config=standalone-alternate.xml
2.  Stop JBoss
Stop an instance which was started interactively from a command prompt.
Press Ctrl-C in the terminal where JBoss EAP 6 is running.
3.  Configuration files
EAP_HOME/bin/standalone.sh -c standalone-full-ha.xml
Backup:
EAP_HOME/standalone/configuration/
Descriptor-based Property Replacement:
Java EE descriptor replacement is disabled by default. When enabled, descriptors can be replaced
in the following configuration files: ejb-jar.xml and persistence.xml.
<subsystem xmlns="urn:jboss:domain:ee:1.2">
  <spec-descriptor-property-replacement>
true
  </spec-descriptor-property-replacement>
  <jboss-descriptor-property-replacement>
true
  </jboss-descriptor-property-replacement>
</subsystem>



4. JBoss auto keeps the configuration file change history under the below folder,

EAP_HOME/bin/standalone.sh --server-config=standalone_xml_history/current/standalone.v1.xml

EAP_HOME/standalone/configuration/standalone_xml_history

5. CLI

C:\>EAP_HOME\bin\jboss-cli.bat

   connect
   quit
or

$ EAP_HOME/bin/jboss-cli.sh --connect --controller=192.168.0.1:9999

[standalone@localhost:9999 /] help

[standalone@localhost:9999 /] deploy --help

Batch processing allows a number of operation requests to be grouped in a sequence and executed together as a unit. If any of the operation requests in the sequence fail, the entire group of operations is rolled back.

[standalone@localhost:9999 /] batch

:whoami

[domain@localhost:9999 /] version

show JBoss system and server information: version
From the Management CLI, enter the history command:

C:\bin>  add-user.bat

EAP_HOME/standalone/configuration/application-users.properties

6. Deploy
Copy the application file to the deployment folder found at EAP_HOME/standalone/deployments/.

7. log

Standalone mode

EAP_HOME/standalone/configuration/logging.properties

8. MQ
Be aware that WebSphere MQ 8.0 and above is not supported in EAP 6.x.?
Copy the wmq.jmsra-VERSION.rar file to the EAP_HOME/standalone/deployments/directory?

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/6.4/html/administration_and_configuration_guide/deploy_the_websphere_mq_resource_adapter

9. add user:
add-user.bat -u admin -p adminPass1!
add-user.bat -a -u quickstartUser -p quickstartPwd1! -g guest