Management interfaces

Management interfaces

One of the innovating features of the application server is the powerful administration and management channels that include a CLI and a web-based administration console. The native CLI interface, by default, runs on port 9999, while the web console is bound on port 9990.

<socket-binding-group name=”standard-sockets” default-interface=”public”>

<socket-binding name=”management-native” interface=”management” port=”9999″/>

<socket-binding name=”management-http” interface=”management” port=”9990″/>


Management interfaces are discussed in detail in Chapter 7, Managing the Application Server, which provides a detailed coverage of the application server management tools.


Letting the configuration file flow, you can find the definition of the server’s profiles, which is one of the core concepts introduced in AS. A profile can be seen as a collection of subsystems: each subsystem in turn contains a subset of functionalities used by the application server. For example, the web subsystem contains the definition of a set of connectors used by the container, the messaging subsystem defines the JMS configuration and modules used by the AS’s messaging provider, and so on.


One important difference between a standalone and a domain configuration file is the number of profiles contained in it. When using a standalone configuration, there’s a single profile that contains the set of subsystem configurations. Domain configuration can, on the other hand, provide multiple profiles.


The interfaces section contains the network interfaces/IP addresses or host names where the application server can be bound.

By default, the standalone application server defines two available network interfaces: the management and the public interface:


<interface name=”management”>

<inet-address value=”${jboss.bind.address.management:}”/>


<interface name=”public”>

<inet-address value=”${jboss.bind.address:}”/>



The public network interface is intended to be used for the application server core services:

<socket-binding-group name=”standard-sockets” default-interface=”public”>


The management network interface is referenced by the AS management interfaces, as shown in the management interfaces section.

Both network interfaces resolve, by default, to the loop back address This means that, by default, the application server public services and the management services are accessible only from the local machine. By changing the inet-address value, you can bind the network interface to another IP address, which is available on the machine:

<interface name=”public”>

<inet-address value=”″/>


If, on the other hand, you want to bind the network interface to all available sets of IP address, you can use the <any-address /> element:

<interface name=”public”>

<any-address /> </interface>

Another useful variation of network interface is the Network Interface Card (NIC) element, which gathers the address information from the network card name:

<interface name=”public”>

<nic name=”eth0″ />


Using command-line options to change network interface bindings

In earlier releases of the application server, you used to launch the startup script with the additional -b parameter, followed by a valid host/IP address. This would cause the server to bind on the host/IP address provided. This option was not available in the initial AS 7 release however it has been restored in the AS 7.1.0 release.

Socket binding groups

A socket binding makes up a named configuration of a socket. Within this section, you are able to configure the network ports, which will be open and listening for incoming connections. As we have just seen, every socket binding group references a network interface through the default-interface attribute:

<socket-binding-group name=”standard-sockets” default-interface=”public”>

<socket-binding name=”jndi” port=”1099″/>

<socket-binding name=”jmx-connector-registry” port=”1090″/>

<socket-binding name=”jmx-connector-server” port=”1091″/>

<socket-binding name=”http” port=”8080″/>

<socket-binding name=”https” port=”8447″/>

<socket-binding name=”osgi-http” port=”8090″/>

<socket-binding name=”remoting” port=”4447″/>

<socket-binding name=”txn-recovery-environment” port=”4712″/>

<socket-binding name=”txn-status-manager” port=”4713″/>

<socket-binding name=”txn-socket-process-id” port=”4714″/>

<socket-binding name=”messaging” port=”5445″/>

<socket-binding name=”messaging-throughput” port=”5455″/>


In order to change the ports where services are bound, you can change the port attribute of its service. A definitely better approach is, however, to use management interfaces that provide an immediate outcome of the affected change. In the following example, we are changing the default port for the http connector using the CLI:

[standalone@localhost:9999 /] /socket-binding-


attribute(name=”port”, value=”8090″)

{   “outcome” => “success”,   “response-headers” => {

“operation-requires-reload” => true,

“process-state” => “reload-required”



System properties

This section contains a set of system-wide properties, which can be added to the application server as part of the booting process. The following configuration snippet sets the property named example to dummyvalue:


<property name=”myproperty” value=”dummyvalue”/>


The property can be later retrieved on the application server using:

String s = System.getProperty(“myproperty”);


The last section of the configuration file contains the deployed application, which has been registered on the application server. Each time a new application is deployed or un-deployed, this section is updated to reflect the new application stack.

0 Responses on Management interfaces"

Leave a Message

Your email address will not be published. Required fields are marked *

Copy Rights Reserved © Mindmajix.com All rights reserved. Disclaimer.