Owner's manual

Table 3 JBoss subsystems support (continued)
NSASJDescriptionSubsystem Name
SupportedThis is the subsystem that defines the entire infrastructure required by the
container to support EJBs. This subsystem does not define the beans.
EJB3
SupportedThis is the subsystem where the Infinispan subsystem configuration is defined.
In case of NSASJ, Infinispan is configured in a distributed mode. The EJB
Infinispan
subsystem references the Infinispan subsystem for caches and passivation
stores.
Not SupportedAn ORB is required for any communication using the IIOP. IIOP can be used
to invoke EJBs or can be used as the transaction manager (called the
Jacorb
coordinator) for distributed transactions spanning multiple transaction
managers. Since there are no components within NSASJ that need IIOP,
JacORB is disabled for NSASJ.
Not SupportedJava API for XML Registries (JAXR) is a new technology specified in the Java
EE Version 6 specification. JAXR is a client API that can lookup underlying
Jaxr
XML registry implementation such as ebXML or UDDI. JBoss does not ship
the registry implementation itself but ships only the client library implementing
JAXR.
Not SupportedJAX-RS defines an API for development of web services built according to
the REST (Representational State Transfer) architectural style. JAX-RS style
web services have to be deployed in a web container.
Jaxrs
SupportedThere are no NonStop specific JCA components provided by NSASJ. Hence,
this subsystem is not a part of the default NSASJ profile.
JCA
Not SupportedIf the JDR (JBoss Diagnostic Reporting) subsystem is enabled, an administrator
can generate a run time diagnostic report on a running instance of JBoss
JDR
server. By default, this subsystem is not enabled in NSASJ as the diagnostics
report can be obtained for only one instance at a time. A useful report for
NSASJ must include a report of the deployment rather than just a single
instance.
SupportedJGroups is a toolkit for reliable multicast communication. This is the toolkit
used by other subsystems of the JBoss container for reliable communication.
NSASJ inherits the JGroups setup from JBoss.
JGroups
Not SupportedThis subsystem when enabled allows JMX management of the nodes within
the cluster. NSASJ allows management through CLI and does not support
JMX
JMX management. Due to the nature of deployment (TS/MP serverclass), the
JMX clients cannot identify any particular instance to connect. If this subsystem
is enabled, then all the instance of the serverclass listens to the JMX
connections on the same port.
SupportedThe Java Persistence API is the standard API for the management of
persistence and object-relational mapping. JBoss internally uses Hibernate
JPA
as the JPA provider. NSASJ provides the necessary NonStop specific tooling
(such as the dialect file) to support Hibernate on NSASJ.
Not SupportedJSR77 defines a well defined model to abstract the fundamental manageable
aspects of a Java EE environment. JBoss provides an MEJB, a Management
JSR77
EJB to provide the necessary information in the model specified by the JSR.
The information can be obtained per server and not for the entire cluster.
Not SupportedThis is the implementation of JavaMail API that enables Java EE application
to send mails.
Mail
SupportedThe JMS server configuration is done through the Messaging subsystem.
NSASJ can integrate with NSMQ.
Messaging
Not SupportedModcluster is a subsystem that interfaces with Apache HTTPD to provide
certain HA and load balancing features.
Modcluster
NOTE: Modclusterhas more use cases than just HA and load balancing.
It is out of scope of this document to explain them.
16 Introduction