WildFly CLI Connect to a Controller: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 13: | Line 13: | ||
For more details about configuring CLI, see [[WildFly CLI Configuration|CLI Configuration]] | For more details about configuring CLI, see [[WildFly CLI Configuration|CLI Configuration]] | ||
To log in into a specific controller | To log in into a specific controller, use <tt>--connect=</tt> option immediately followed by the controller URL. | ||
The client can connect over the JMX or Remoting protocols. | |||
==Connecting over Remoting Protocol== | |||
Note that <tt>remoting://</tt> is optional | |||
<pre> | |||
./jboss-cli.sh --connect=localhost:9999 | |||
./jboss-cli.sh --connect=remoting://localhost:9999 | |||
</pre> | |||
==Connecting over the JMX Protocol== | |||
<font color=red>TODO, it seems that jmx:// and remoting:// does not make a difference.</font> | |||
==<tt>--controller Option</tt>== | |||
<font color=red>TODO</font> | |||
<pre> | <pre> | ||
jboss-cli.sh --connect --controller=192.168.0.1:9999 [--user=admin --password=admin123] | jboss-cli.sh --connect --controller=192.168.0.1:9999 [--user=admin --password=admin123] | ||
</pre> | </pre> | ||
Revision as of 20:03, 4 October 2016
Internal
Overview
Login to the controller specified in jboss-cli.xml.
jboss-cli.sh -c
For more details about configuring CLI, see CLI Configuration
To log in into a specific controller, use --connect= option immediately followed by the controller URL.
The client can connect over the JMX or Remoting protocols.
Connecting over Remoting Protocol
Note that remoting:// is optional
./jboss-cli.sh --connect=localhost:9999 ./jboss-cli.sh --connect=remoting://localhost:9999
Connecting over the JMX Protocol
TODO, it seems that jmx:// and remoting:// does not make a difference.
--controller Option
TODO
jboss-cli.sh --connect --controller=192.168.0.1:9999 [--user=admin --password=admin123]