WildFly CLI Connect to a Controller: Difference between revisions
Jump to navigation
Jump to search
| 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, use <tt>--connect=</tt> option immediately followed by the controller URL or the <tt>--controller</tt> option. | To log in into a specific controller, use <tt>--connect=</tt> option immediately followed by the controller URL or the <tt>[[#--controller_Option|--controller]]</tt> option. | ||
The client can connect over the JMX or Remoting protocols. | The client can connect over the JMX or Remoting protocols. | ||
Revision as of 20:04, 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 or the --controller option.
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]