Domain.xml – HP Integrity NonStop H-Series User Manual
Page 45
Table 7 Contents of host.xml (continued)
Description
Component
For more information, see
In NSASJ, there is no distinction between the Host Controller
and the Domain Controller. The Host Controller plays the role
domain-controller
of Domain Controller. This is indicated by the local child
element in the domain-controller.
JBoss AS 7 uses named interface references throughout the
configuration. A network interface is declared by specifying
interfaces
NOTE:
The interface definition here overrides the one
in domain.xml.
a logical name and selection criteria for the physical interface.
The management interface is used for all components and
services that are required by the management layer (that is
the HTTP Management endpoint).
NOTE:
As of NSASJ 1.0 release, HTTP management is not
supported by NSASJ.
The public interface binding is used for any application
related network communication such as JNDI lookup, EJB
invocation and so on.
This is not relevant in NSASJ as configuring servers is
controlled by TS/MP and not by the Domain Controller.
jvms
In NSASJ, the domain configuration contains only one server
group and within the group only one server definition.
servers
domain.xml
The domain.xml is the file where the Java EE container is configured. The extensions defined
in the domain.xml file are modules that provide a certain set of features for the container. The
features offered by the container are a sum of all the features offered by the extension modules.
NSASJ defines and configures extensions that are required for the container to provide all the
necessary EJB and JPA functionalities.
Host Controller and NSASJ Server components
45