2016-04-27 03:02:53 +00:00
[[_app_server_cli]]
== Manage Configuration at Runtime
In the upcoming chapters, you'll often be provided two options for applying application server configuration changes to your deployment. You'll be
shown how to edit the _standalone.xml_ or _domain.xml_ directly. This must be done when the server (or servers) are offline.
2017-08-28 12:50:14 +00:00
Additionally, you may be shown how to apply config changes on a running server using the app server's command line interface ({appserver_name} CLI). This chapter discusses
2016-04-27 03:02:53 +00:00
how you will do this.
2016-04-30 04:39:32 +00:00
2017-08-28 12:50:14 +00:00
=== Start the {appserver_name} CLI
2016-04-27 03:02:53 +00:00
2017-08-28 12:50:14 +00:00
To start the {appserver_name} CLI, you need to run the `jboss-cli` script.
2016-04-27 03:02:53 +00:00
.Linux/Unix
[source]
----
$ .../bin/jboss-cli.sh
----
.Windows
[source]
----
> ...\bin\jboss-cli.bat
----
This will bring you to a prompt like this:
.Prompt
[source]
----
[disconnected /]
----
There's a few commands you can execute without a running standalone server or domain controller, but usually you will
have to have those services booted up before you can execute CLI commands. To connect to a running server simply
2016-04-29 20:12:12 +00:00
execute the `connect` command.
2016-04-27 03:02:53 +00:00
.connect
[source]
----
[disconnected /] connect
connect
[domain@localhost:9990 /]
----
2016-04-29 20:12:12 +00:00
You may be thinking to yourself, "I didn't enter in any username or password!". If you run `jboss-cli` on the same machine
2016-04-27 03:02:53 +00:00
as your running standalone server or domain controller and your account has appropriate file permissions, you do not have
2018-05-29 08:02:18 +00:00
to setup or enter in an admin username and password. See the link:{appserver_admindoc_link}[_{appserver_admindoc_name}_] for more details on how to make things more secure if you are uncomfortable with that setup.
