NonStop Server for Java (NSJ) Programmer's Guide (NSJ 2.1+)

Binding Libraries Into the JVM
To establish an environment that permits the use of servlets and similar clients, you must bind the
appropriate libraries into the JVM. To bind the libraries, use
/usr/tandem/java/install/Makefile. This Makefile relinks java with any libraries
in the directories /usr/tandem/java/lib,
/usr/tandem/java/lib/oss/posix_threads, /usr/tandem/java/jre/lib, and
/usr/tandem/java/jre/lib/oss/posix_threads. For information about this
Makefile, see /usr/tandem/java/install/README. See also the latest version of the
Software Release documentation (Softdoc) for information on how to install the JVM, the JDBC
Driver for SQL/MX, and the JDBC Driver for NonStop SQL/MX.
Note: To use clients with other programs (for example, using servlets with the iTP
Secure WebServer), you must install the JVM before installing the other programs.
Native Libraries
Native libraries, such as those that are supplied with the iTP Secure Webserver and the NonStop
Enterprise Application Server, are typically installed in one or more directories under the NonStop
Java directory. These libraries are then automatically linked into the Java executable when you run
the make utility to rebuild the Java executable.
To reinstall the native libraries, reinstall the products that own those libraries or copy the library files
manually from the old location to the new location. Use care when copying files manually so that you
do not overwrite any native libraries included with NonStop Java. You can use the -i option of the
cp command to preserve existing files in the destination directory. If you are not sure which native
libraries should be copied, do not attempt a manual copy.
Configuring TCP/IP and DNS for RMI
For Remote Method Invocation (RMI) API to work, TCP/IP and its component, DNS, must be
configured correctly.
A network administrator usually configures TCP/IP and DNS, but you can determine if an incorrect
TCP/IP configuration is causing a JVM problem. To check the TCP/IP configuration, use the Java
Checker, javachk, which is available in the /usr/tandem/java/install directory. Execute
javachk in the same environment as the JVM has (that is, using the same defines that were used to
run the JVM). The Java Checker will identify failing Guardian socket routine calls. When you know
which calls are failing, you can fix or work around the problems.
For information about javachk, see the file
/usr/tandem/java/install/README_javachk.