NonStop Server for Java 4.2 Programmer's Reference

JAAS Enhancement
In NonStop Server for Java 3.x and earlier versions, the Java Authentication and Authorization Service
(JAAS) was an optional package (extension). JAAS is integrated into the NonStop Server for Java 4.
JAAS augments the core Java 2 platform with APIs that allow authenticating users and enforcing access
controls upon users. Traditionally, Java 2 provided code-source-based access controls (access controls
based on where the code originated and who signed the code). However, Java 2 lacked the ability to
additionally enforce access controls based on who runs the code. In NonStop Server for Java 4, JAAS
provides a framework that augments the Java 2 security architecture with this additional capability.
For more information on JAAS, see Java Authentication and Authorization Service (JAAS).
Migrating Applications to TNS/E Systems
The NonStop Server for Java 4 on TNS/E has the same Java features and functions as version 2, NonStop
Server for Java 4 on TNS/R. This topic summarizes the differences between using the NonStop Server
for Java 4 on TNS/R systems and on TNS/E systems. For differences documented in another section of
the manual, follow the link provided.
The NonStop Server for Java 4 installation directory in TNS/E systems is
/usr/tandem/nssjava/jdk142_H10.
●
The NonStop Server for Java 4 supports Dynamic-Link Libraries (DLLs) on TNS/E; therefore:
All the Java libraries are built as DLLs.
❍
When using the JNI code, use DLLs instead of static libraries. For further information, see
Java Native Interface (JNI). A public library directory does not apply for Java applications
on the TNS/E platform.
❍
All DLLs must be in files that have specific naming requirements. For further information
see DLL names.
❍
On TNS/E, the -Dcompaq.liblist option is not supported.❍
The customer Makefile no longer exists in the NonStop Server for Java 4 on TNS/E because
DLL support precludes the need to bind user native code into the java executable.
❍
●
The _RLD_LIB_PATH environment variable, used only on the TNS/E platform, specifies the
library path for user DLLs. For further information, see _RLD_LIB_PATH (TNS/E Only).
●
The invocation API uses the JVM as a DLL; therefore, if you use this API, you do not need to
statically link Java into your programs.
●
Change the JNI_OnLoad function call. For further information, see the discussion about the
JNI_OnLoad function.
●
Visual Inspect is the preferred debugger for applications on TNS/E. For debugging native code,
you can also use Native Inspect ($System.SYSnnn.EINSPECT command).
●
For TNS/E, you can use C++ code compiled using either a dialect of version 2 or version 3●