To compile and run a Java SDK application, you need to set up the CLASSPATH and
PATH (or
LD_LIBRARY_PATH on UNIX). The shared library path must be set because the TIBCO Rendezvous Java implementation uses JNI to access its shared libraries at runtime. If the TIBCO Rendezvous shared library path is not specified, a runtime exception of
Native Implementation required is thrown.
Assuming that the TIBCO Runtime Agent (with SDK suite) has been installed in C:\tibco\tra,
TPCL in
C:\tibco\tpcl, Rendezvous in
C:\tibco\tibrv\8.1, and JDK in
C:\jdk, the
CLASSPATH and
PATH should be set as follows:
Generally speaking, a security provider JAR must be part of CLASSPATH whenever encryption or secure connections are used. Specific scenarios are:
For example, if your applications require SSL and you are using Entrust, ensure that the CLASSPATH includes the Entrust JAR file. See
install-path\tibco\tpcl\version_number\lib\entrust.
To use a different security vendor, change the TIBCO_SECURITY_VENDOR java property. For example, if you use J2SE as the vendor then you must either: