WildFly CLI Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 9: Line 9:
=Server's Management Bind Address=
=Server's Management Bind Address=


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


<pre>
<pre>
Line 19: Line 21:
     </default-controller>
     </default-controller>


    ...
</jboss-cli>
</pre>
In EAP 7
<pre>
<jboss-cli xmlns="urn:jboss:cli:2.0">
  <default-controller>
        <protocol>http-remoting</protocol>
        <host>localhost</host>
        <port>9990</port>
    </default-controller>
     ...
     ...


</jboss-cli>
</jboss-cli>
</pre>
</pre>

Revision as of 22:39, 13 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>