SQL/MX 3.2.1 Guide to Stored Procedures in Java (H06.26+, J06.15+)

Figure 10 Specifying the Node in the External Path
When an application on the remote \NODEB calls the SPJ, the JVM looks for the Java class in the
/E/NODEA/usr/mydir/myclasses directory on \NODEA. Regardless of where you issue the
CALL statement, the JVM in the SPJ environment always tries to load the Java class from the OSS
directory on the node that you specify in the EXTERNAL PATH clause.
Advantages of Specifying the Node
The Java classes exist in only one location, which eliminates the need to maintain them on separate
nodes.
Disadvantages of Specifying the Node
By using this approach, you sacrifice local node autonomy. For example, applications running on
\NODEB rely on the Java class stored on \NODEA to function properly. If \NODEB becomes
disconnected from \NODEA, an application on \NODEB that calls the SPJ on \NODEA will not work.
This approach also involves the overhead of loading Java classes from a remote node instead of
from the local node.
Distributing Application Classes
If an SPJ method in a distributed database environment relies on application classes outside the
external path, you must either copy these classes to the same OSS directory on the remote node
or include the full path of these classes in the class path. For more information about how to set
the class path, see Setting the Class Path (page 43).
100 Managing SPJs in NonStop SQL/MX