Checklist

Developers of Rendezvous programs can use this checklist during the four phases of the development cycle: installing Rendezvous software, coding your Java program, compiling your Java program, and running your program as either an independent application or as a browser applet.

Install

• Install the Rendezvous software release, which automatically includes the Java archive files in the lib subdirectory.
• The CLASSPATH variable must include an archive file that contains the Rendezvous classes.

On UNIX platforms, include the appropriate archive file from Archive Files.

On other supported platforms, this step is automatic.

Code

• Import the correct Rendezvous package.

Import com.tibco.tibrv.*

Compile

• An up-to-date version of Java (JDK) is required.
• The CLASSPATH variable must include an archive file that contains the Rendezvous classes. Include the appropriate archive file from Archive Files.
• To use TIBCO RendezvousÆ Server In-Process Module (IPM), the CLASSPATH variable must include the archive file tibrvnative.jar; it is the only archive file that supports IPM.

Run

• An up-to-date version of Java (JRE) is required.

Run as Independent Application

• Rendezvous software must be properly installed, so that the application can access shared library files. For details, see Shared Library Files.
• The CLASSPATH variable must include the location of the Rendezvous classes. Include the appropriate archive file from Archive Files.
• The application must be able to connect to a Rendezvous daemon process (rvd).

Run as Applet Using rvd Transports

• Rendezvous software must be properly installed on the computer on which the applet is running, so that the application can access shared library files.
• Applets running in a browser gain speed when the Rendezvous package is installed locally. To take advantage of this efficiency, the CLASSPATH variable (as read when the browser starts) must include an appropriate archive file from Archive Files.
• The applet must be able to connect to a Rendezvous daemon process (rvd). If the browser does not permit the applet to connect to rvd, adjust the browser’s security settings to permit TCP connections to the rvd client connection socket (the daemon parameter specifies this socket).

Run as Independent Application with IPM

• Ensure that the IPM C library is in the path variable; see IPM Library.