WildFly CLI Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 11: | Line 11: | ||
If the server's management bind address changes and it cannot be reached at its default endpoint anymore, modify <tt>default-controller</tt> in the client's configuration file. | If the server's management bind address changes and it cannot be reached at its default endpoint anymore, modify <tt>default-controller</tt> in the client's configuration file. | ||
In EAP 6 | In EAP 6: | ||
<pre> | <pre> | ||
| Line 26: | Line 26: | ||
</pre> | </pre> | ||
In EAP 7 | In EAP 7: | ||
<pre> | <pre> | ||
| Line 40: | Line 40: | ||
</jboss-cli> | </jboss-cli> | ||
</pre> | </pre> | ||
=Subjects= | |||
* [[Add Domain Controller Public Key to CLI Truststore]] | |||
Latest revision as of 19:09, 20 March 2017
Internal
Overview
The CLI is configured in $JBOSS_HOME/bin/jboss-cli.xml.
Server's Management Bind Address
If the server's management bind address changes and it cannot be reached at its default endpoint anymore, modify default-controller in the client's configuration file.
In EAP 6:
<jboss-cli xmlns="urn:jboss:cli:1.3">
<default-controller>
<host>localhost</host>
<port>9999</port>
</default-controller>
...
</jboss-cli>
In EAP 7:
<jboss-cli xmlns="urn:jboss:cli:2.0">
<default-controller>
<protocol>http-remoting</protocol>
<host>localhost</host>
<port>9990</port>
</default-controller>
...
</jboss-cli>