WildFly CLI Concepts: Difference between revisions
No edit summary |
|||
| Line 27: | Line 27: | ||
Commands correspond to higher-level interactions with the controller. They are supposed to have user-friendlier syntax, but ultimately they translate into operations, or even composite operation requests. | Commands correspond to higher-level interactions with the controller. They are supposed to have user-friendlier syntax, but ultimately they translate into operations, or even composite operation requests. | ||
= | =Node= | ||
=Attribute= | |||
=Resource= | =Resource= | ||
Revision as of 04:36, 10 February 2016
Internal
Overview
The management CLI is a command line administration tool that manages WildFly nodes running in both standalone and domain mode. The tool exercises the native management API of the application server. The CLI client works with a managed domain or a standalone instance, allowing the user to control either the domain controller or the standalone server and execute management operations through a de-typed (string-driven) management model.
The Management CLI may be used to start and stop servers, deploy and undeploy applications, configure system settings and perform other administrative tasks. Operations can be performed in batch mode, allowing multiple tasks to be executed as a group. For servers running in domain mode, the CLI connects to the domain controller and can be used to manage the entire domain.
The Management CLI can perform all tasks the web-based management console can perform, as well as many other lower level operations that are not available to the web-based administration tool.
CLI and Management Interfaces
CLI clients connect to the managed WildFly instances over management interfaces. There are two types of management interfaces: native and http. For more details on management interfaces see:
Command and Operations
The CLI interacts with the target controller by reading the user's commands and issuing operations.
Operations are the finest-possible grained interaction mode with the controller: if it can't be done with an operation, it can't be done in any other way.
Commands correspond to higher-level interactions with the controller. They are supposed to have user-friendlier syntax, but ultimately they translate into operations, or even composite operation requests.