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

To modify CLASSPATH, use the following command:
export CLASSPATH=.:/h/custom_path/myclasses.jar
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 /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 directories. For information
about this Makefile, see /usr/tandem/java/install/README.
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.
Compiling the JVM Objects Using the SQL
Compiler
To use JDBC
TM
to access SQL/MP databases, you must compile the java object using the
SQL Compiler. You can do this either directly or by using
/usr/tandem/java/install/Makefile. Using the Makefile is recommended. For
information about the Makefile, see /usr/tandem/java/install/README.
You need to compile the JVM objects with the SQL Compiler only once after installing the
latest version of the JDK.
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