HP Integrity NonStop H-Series - Manual (Page 63)

sure that the session entry is removed from the remote servers, the attribute of the
element of the namedCache must be set to the session-timeout value. Also, the
element of the element must be set to the maxInactiveInterval
of the application. This configuration ensures entries are cleared from the Infinispan Cache servers
on expiration of session.
Java Persistence API subsystem
This subsystem is used to configure the default for JPA. This subsystem configuration is defined by
the schema descriptor in file jboss-as-jpa_1_0.xsd in the docs/schema folder. It supports
the default-datasource attribute which is the JNDI name of the datasource that is to be used
by default by the persistent API.
Naming subsystem
This subsystem configures the Naming subsystem. This subsystem can be used to export named
resources. The schema for the subsystem configuration can be found in
jboss-as-naming_1_2.xsd
located in the docs/schema folder. Table 18 (page 63) lists the
components of Naming subsystem:
Table 18 Components of Naming subsystem
Element/Attribute Component
This element is an empty element that when defined makes the
resources available for remote lookups. remote-naming
This element can be used to create named resources. The named
resources can either be created using the simple element or
object-factory
.
bindings
This element can be used to create named resources of simple types
such as int, long, double and so on. It accepts the following
attributes: simple
•
name : Specifies the JNDI name.
•
value : Specifies the string representation of the value.
•
type : Specifies the type of resource.
This element can be used to create named resources of any object
type. This requires an object factory to create the object. The
following are the attributes defined for this element: object-factory
•
name : Specifies the name of the resource.
•
factoryClass : Specifies the fully qualified name of the factory
class module.
•
module : Specifies the name of the module whose classloader
must be used to search for the factory class.
NSASJ introduces a feature where NSASJ can lookup NSMQ admin objects from NSASJ naming
directory. For this feature NSMQ must be installed. The following subsection explains the steps to
setup the environment:
1. Copy the file $NSMQ/activemq-all-5.6.0.jar and NSMQ/lib/slf4j-api-1.6.4.jar
to <NSASJ_HOME>/modules/com/hp/nsk/nsmq/main, where NSMQ is the location of
NSMQ deployment, and is the location of NSASJ deployment.
2. Make necessary entries in nsmq.jndi.properties file.
3. Add the necessary configuration in the naming subsystem in domain.xml (located in
<NSASJ_HOME>/domain/configuration
)
4. Restart the NSASJ server.
Java Persistence API subsystem 63