Java Reference
In-Depth Information
/subsystem=datasources/:read-resource
{
"outcome" => "success",
"result" => {
"data-source" => {"ExampleDS" => undefined},
"jdbc-driver" => {"h2" => undefined},
"xa-data-source" => undefined
}
}
If you want to query for a specific attribute of your node, you can use the
read-at-
tribute
operation instead. For example, the following code shows how to read the en-
abled attribute from the data source:
/subsystem=datasources/data-source=ExampleDS/
:read-attribute(name=enabled)
{
"outcome" => "success",
"result" => false
}
Note
Apart from the operations on a specific resource, you can also perform a set of commands
that are available on every path of your WildFly subsystem, such as
cd
or
ls
commands.
These commands are pretty much equivalent to their Unix shell counterparts, and they al-
low you to navigate through the WildFly subsystems. Other important additions are the
deploy
and
undeploy
commands that, as you might guess, allow you to manage the
deployment of applications. These key commands are discussed in the
Deploying applica-
tions using the CLI
section of this chapter.
The CLI, however, is not just about querying attributes from the WildFly subsystems; you
can also set attributes or create resources. For example, if you were to set the HTTP port
of the HTTP connector, you will have to use the corresponding
write
attribute on
HTTP's socket binding interface, shown as follows:
/socket-binding-group=standard-sockets/socket-binding=http/
:write-attribute(name=port,value=8080)
{
