Comparison of jboss and nsasj – HP Integrity NonStop H-Series User Manual
Page 15
state of a SFSB (Stateful Session Bean). For more information on Infinispan, see
•
Post Master: A Post Master acts as a postmaster between remote Java EE clients and NSASJ
Server. Post Master does not participate in data processing. It just acts as an agent, which
transfers data between the remoting client and NSASJ serverclass, so that the instances can
effectively handle client requests. For more information on Post Master, see
configuration files” (page 48)
Comparison of JBoss and NSASJ
provides a component-wise comparison between JBoss and NSASJ.
Table 2 Component-wise comparison of JBoss and NSASJ
NSASJ
JBoss
Component
Server
•
Only one server can be configured for each
NSASJ deployment.
•
More than one instance of server can be
configured.
•
•
Each server has its own configuration. A
server group is a logical grouping of one or
The server is configured as a TS/MP serverclass
with multiple instances.
more servers sharing a single configuration.
•
All the instances share the same configuration
and file system resources.
All servers in the server group have a common
configuration.
•
Host Controller serves as Domain Controller in
NSASJ.
Domain
Controller
•
Only one instance of Domain Controller is
available.
•
This is the single point of control for the
various Host Controllers.
•
The management interfaces interact with the
Domain Controller.
Host
Controller
•
Only one Host Controller per NSASJ deployment.
•
One Host Controller per host in a domain.
•
•
Acts as a single point of management for all
the server nodes on the host.
Acts as a single point of management for all the
NSASJ serverclass instances.
Process
Controller
•
Not available for NSASJ as all components of
NSASJ are configured as TS/MP serverclasses.
•
Manages all processes in the domain.
•
Starts and in case of a failure restarts
components of the domain.
•
Process management is done by TS/MP rather
than any of NSASJ component.
lists the subsystems in a JBoss that are supported by NSASJ.
Table 3 JBoss subsystems support
NSASJ
Description
Subsystem Name
Supported
The logging subsystem contains the logging configuration for the container.
Logging
Not Supported
A CMP bean is an entity bean whose state is synchronized with the database
automatically. In the current Java EE specification, CMP is replaced by JPA.
CMP
Not Supported
The OSGi Componendium Configuration Admin Service specifies a service,
which allows easy management of configuration data for configurable
ConfigAdmin
components. The ConfigAdmin subsystem provides this service in JBoss. Since
NSASJ does not supports OSGi framework, the feature to configure the OSGi
bundles are also not required. Therefore, ConfigAdmin subsystem is not a
part of NSASJ profile.
Supported
This is the subsystem where the data sources are configured. The data sources
can be either XA data sources or non-XA data sources.
DataSources
Supported
This subsystem enables the deployment of EAR files, and NSASJ uses this
subsystem as is.
EE
Comparison of JBoss and NSASJ
15