Connecting to the CLI

To start a CLI session, you need to launch a shell script located in the $JBOSS_HOME/bin folder, named jboss-cli.sh (or jboss-cli.bat if you are running Windows).

As you execute the script, you will start a disconnected session, as shown here:

./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /]

As suggested by the shell, you need to hit the connect command to connect to a running EAP instance, as follows:

./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9990 /] 

By default, the host and port coordinates are localhost:9990, so the connect command is the same:

./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect localhost:9990
[standalone@localhost:9990 /] 

Those default settings are specified in the jboss-cli.xml file available under the $JBOSS_HOME/bin folder.

You can have an already connected session by enabling the flag connection while invoking the script via shell, as follows:

./bin/jboss-cli.sh --connect
[standalone@localhost:9990 /]

And if you need to provide different schema, host, and port values, you can use the controller directive, as follows:

./bin/jboss-cli.sh --connect --controller=http-remoting://localhost:9990
[standalone@localhost:9990 /] 

To close the CLI session you can just invoke the quit command. There are also aliases, such as exit and q, to close the CLI.