9.8.2. Specify Which Network Interface the JBoss Enterprise Application Platform Uses
Isolating services so that they are accessible only to the clients who need them increases the security of your network. The JBoss Enterprise Application Platform includes two interfaces in its default configuration, both of which bind to the IP address
localhost, by default. One of the interfaces is called
management, and is used by the Management Console, CLI, and API. The other is called
public, and is used to deploy applications. These interfaces are not special or significant, but are provided as a starting point.
managementinterface uses ports 9990 and 9999 by default, and the
publicinterface uses port 8080, or port 8443 if you use HTTPS.
Stop the JBoss Enterprise Application Platform.Stop the JBoss Enterprise Application Platform by sending an interrupt in the appropriate way for your operating system. If you are running the JBoss Enterprise Application Platform as a foreground application, the typical way to do this is to press Ctrl+C.
Restart the JBoss Enterprise Application Platform, specifying the bind address.Use the
-bcommand-line switch to start the JBoss Enterprise Application Platform on a specific interface.
Example 9.21. Specify the public interface.
EAP_HOME/bin/domain.sh -b 10.1.1.1
Example 9.22. Specify the management interface.
Example 9.23. Specify different addresses for each interface.
EAP_HOME/bin/domain.sh -bmanagement=127.0.0.1 -b 10.1.1.1
Example 9.24. Bind the public interface to all network interfaces.
EAP_HOME/bin/domain.sh -b 0.0.0.0
-bcommand-line switch to specify an IP address at run-time, so this is not recommended. If you do decide to do this, be sure to stop the JBoss Enterprise Application Platform completely before editing the XML file.