NonStop Application Server for Java (NSASJ )

NSASJ is a application server for HP Nonstop platform. The architecture of JBoss is modified and re-engineered to transform it to NSASJ and enable it to work along with various NonStop technologies to exhibit and inherit JBoss’s features.

Before understanding NSASJ, it is recommended to have a prior knowledge of Java EE platform, EJB,and web container components.

Java EE components supported by NSASJ
Following table describes Java EE components supported by NSASJ.

Component NSASJ
EJB (Enterprise JavaBeans) Supported
Servlet Supported
JSP Supported
JavaMail Not Supported
Java Persistence Supported
JTA (Java Transaction API) Supported
Connector Supported
JMS (Java Message Service) Supported
WS Metadata Supported
Web Services Supported
CDI (Context and Dependency Injection) Supported
JACC (Java Authorization for Container Contracts) Supported
JAXR ( Java API for XML Registries) Supported
JAX-RS (Java API for RESTful web services) Supported
JAX-WS (Java API for XML web services) Supported
JAX-RPC ( Java API for XML-based RPC) Supported


Components of NSASJ

The following list describes the various components of NSASJ

  • NSASJ Server: This is a single instance of NSASJ Java EE container. We can create multiple instances of the server which can share the same file system resources and configurations.
  • Host Controller: Each NSASJ Server instances has only one Host Controller. This is the responsible component for the domain controlling. It provides a single point management for all NSASJ server instences.
  • Infinispan Cache Cluster: The purpose of this component is to store and share state information across the instances of NSASJ server classes. Each installation of NSASJ has only an Infinispan cache server defined as a TS/MP serverclass. 
  • Post Master: A Post Master  acts as an agent, which transfers data between the remoting client and NSASJ serverclass, so that the  instances can effectively handle client requests.


Configuring NSASJ

NSASJ consist of multiple components such as Server, Host Controller, Cache Server, and Post Master. Each of these components have a specific set of configuration files defined for them.


This file is located in the <NSASJ_HOME>/domain/configuration folder.


This file is located in the <NSASJ_HOME>/domain/configuration folder.The domain.xml is the file where the Java EE container is configured.

Cache server configuration files

The cache server has two configurations. You can find those in <NSASJ_HOME>/infinispan-5.1.4.FINAL/bin folder.



Post Master configuration files


This configuration file contains information about the binding port and connection address. The bind port is indicated by the attribute localPort, and the address to which the Post Master connects, is indicated by the attributes dstAddress and dstPort.


This is the configuration file used by JI to make Post Master behave like a path send client. There is a single line of entry in this file, and is of the format

“client_socket-<host name>:<port number> pathmon=<pmon name>:serverclass=<name of NSASJ SERVER serverclass>”


host name is the name of the host of the IP address indicated by dstAddress in proxy-conf.xml.

port number this is the same as dstPort in proxy-conf.xml.

pmon name is the name of the pathmon where the NSASJ serverclasses are configured.

serverclass is the xx-SERVER serverclass.


Session replication in NSASJ

In NSASJ, this is achieved through Infinispan Cache servers.

  • Session replication configuration for NSASJ

For an application to have session replication on failover, the application must be distributable. Indicate that the application is distributable. If the application is marked as distributable, the session details are stored in the cache. To achieve this, add the <distributable/> element inside the <web-app> tag of the application’s web.xml file.


DataSource configuration


Configuring a DataSource in NSASJ involves the following steps:

  1. Installing the JDBC driver
  2. Configuring the DataSource

Installing the JDBC driver

    Installing the driver jar as a deployment

Deployment can perform either CLI (Command Line Interface ) or WEB console. NSASJ deployment will discussed later.

   Configuring the DataSource

 The DataSource can be configured in the domain configuration file (domain.xml). Can add connection   properties by using web console. Following XML fragment shows how to configure datasource in domain.xml file. 

  <datasource jta="false" jndi-name="java:/test99" pool-name="test99" enabled="true" use-ccm="false">
     <connection-property name="catalog"> 
     <connection-property name="schema"> 

Deployment/ Un-Deployment in NSASJ

Deployment and Un- Deployment is pretty much easier in NSASJ. There are two methods.

  • Web Console
  • CLI

Deployment with CLI

  • Steps
    • FTP the file to be deployed to server.
    • Execute <NSASJ_HOME>/bin/ (./
    • Run command “connect <host>:<controller port>”
      • eg:  connect
    • Run command “deploy< full path to file> –all-server-groups”
      • eg : deploy /abc/test/test.war –all-server-groups

Undeployment with CLI

  • Steps
    • Execute <NSASJ_HOME>/bin/ (./
    • Run command “connect <host>:<controller port>”
      • eg:  connect
    • Run command “undeploy war file name  –all-relevant-server-groups”
      • eg : undeploy  test.war –all-relevant-server-groups
Reference : -NonStop Application Server for Java(NSASJ) 1.3 User Guide