Java Reference
In-Depth Information
Managing the application server
JBoss AS 7 provides three different approaches to configure and manage servers: a
web interface, a command-line client, and a set of XML configuration files. No matter
what approach you choose, the configuration is always synchronized across the dif-
ferent views and finally persisted to the XML files.
Managing JBoss AS 7 with the web interface
The web interface is a Google Web Toolkit ( GWT ) application, which can be used
to manage a standalone or domain JBoss AS distribution. By default, it is deployed
on a local host on the 9990 port; the property that controls the port socket binding is
jboss.management.http.port , as contained in the server configuration ( stan-
dalone.xml/domain.xml ):
<socket-binding-group name="standard-sockets"
default-interface="public">
<socket-binding name="management-http"
interface="management"
port="${jboss.management.http.port:9990}"/>
. . . . . . . . .
</socket-binding-group>
JBoss AS 7.1.x is distributed and is secured by default, and the default security mech-
anism is username- or password-based, making use of HTTP Digest for the authen-
tication process.
Note
The reason for securing the server by default is that, if the management interfaces
are accidentally exposed on a public IP address, authentication is required to con-
nect. For this reason, there is no default user in the distribution.
The users are stored in a properties file called mgmt-users.properties under
standalone/configuration or domain/configuration depending on the
Search WWH ::




Custom Search