Java(tm) Communications API Solaris Installation Instructions

1. Ensure that the library libSolarisSerialParallel.so can be loaded.   You can do this

either by adding libSolarisSerialParallel.so to the environment LD_LIBRARY_PATH  or
by copying libSolarisSerialParallel.so to /usr/lib.
 

Example: Assuming your current working directory is where you extracted the distribution,

     % setenv LD_LIBRARY_PATH `pwd`:$LD_LIBRARY_PATH

      or

   $ export LD_LIBRARY_PATH=$PWD:$LD_LIBRARY_PATH

or, if you have administrative privileges on your machine,

     % cp libSolarisSerialParallel.so /usr/lib
 
 

2. If you are using JDK (not JRE) Add comm.jar to your classpath.

 

 Example: If you don't have a CLASSPATH set currently,

     % setenv CLASSPATH `pwd`/comm.jar

or,  if you have something in your CLASSPATH already,

    % setenv CLASSPATH `pwd`/comm.jar:$CLASSPATH
 

3. Copy the file javax.comm.properties to your <JDK>/lib or your <JRE>/lib directory.

If you don't have write permission to <JDK>/lib or <JRE>/lib, you can keep
javax.comm.properties in the same directory as comm.jar.   The search order for
javax.comm.properties is:
 
1. <JDK>/lib
2. the directory that contains the first valid comm.jar that is included in the classpath.

 
The javax.comm.properties file must be installed. If it is not, no ports will be found by the system.
 
4. Make sure you have the JDK native thread package installed. This implementation only works

with native thread. Look at http://java.sun.com/products/jdk/ for details.
 
5. You should now be able to run your comm application Example:

  % java YourCommAppPkg.YourCommApp

   Note: If you are using JDK 1.1.6, include the -native flag. Example:

   % java -native YourCommAppPkg.YourCommApp
 

6. Several serial port sample applications are provided with this release. One of them is BlackBox.

To run BlackBox, first add BlackBox.jar to your classpath:
 
 
  % setenv CLASSPATH BlackBox.jar:$CLASSPATH

then run BlackBox:

    % java -native BlackBox
 

7. One sample driver NullDriver is included in the samples/NullDriver directory.

This is useful for folks attempting to write a new driver for their own hardware.

Use the -cp option to the JRE to specify the path to the comm.jar file and to your application.

   % jre -cp /home/extra/comm.jar:/home/bin/BlackBox.jar BlackBox

       or, if using  JDK 1.1.6

   % jre -native -cp /home/extra/comm.jar:/home/bin/BlackBox.jar BlackBox
 

The javax.comm.properties file must be in the same location as the comm.jar file or no ports will be found.

The javadocs directory contains the API documentation generated by javadoc(1) from comments
in the source code. To view the HTML files, point your browser at the main documentation page,
javadocs/index.html. 

1. In the current implementation we do not support the notify methods listed below:

 
• SerialPort.notifyOnRingIndicator
• SerialPort.notifyOnOutputEmpty

 
2. The get...() methods can only return what the Solaris driver believes the state to be.

and the following signals are not determined properly as per the following notes
 
• getRI     - Not supported under Solaris

 
• getDSR  - Not supported on SBUS (SPARC) systems because they use the zsdriver,

                 and the zsdriver does not return the state of this pin.
 
3. In the current implementation we do not support port ownership contention resolution across

multiple Java(tm) Virtual Machines. It also does not support uucp style ownership contention
resolution.
 
4. Both parity errors and framing errors are reported as parity errors.

 
5. Support for parallel port is very limited.

   
6. On Solaris platforms the handshake mode needs to be specified for both the
   input and output mode on both the sending and receiving side for it to work properly.