README: IOM Java Client Archive
Version 1.5

Installing the IOM Java Client Archive

The information provided here is for Java program developers and SAS users who want to write their own programs that access the computing and processing power of SAS software.

To install the iomjava.zip archive, use an unzip utility to unpack the iomjava.zip file. You can unpack to any directory.

To install the iomjava.tar archive, use the TAR command to unpack the file. You can unpack to any directory.

Note: The Java Runtime Environment must include the Java 2 SDK, Standard Edition, v 1.2 (J2SDK) or later.

Contents of the Archive

This archive contains the following JAR files:

iomdriver.jar: The SAS Integrated Object Model Driver for JDBC 2.0 classes and the Java Workspace Factory classes. These drivers provide top-level interfaces for communication with the IOM Server.
brgorb.jar: The classes related to the IOM Bridge for Java implementation. The IOM Bridge for Java is a standard CORBA ORB that can communicate with an IOM BRIDGE server. However, because it does not use IIOP, it cannot interoperate with other CORBA ORBs.
iomprx.jar: The generated CORBA stubs for IOM components for use with the IOM Bridge for Java and other CORBA ORBs.
orb.jar: The CORBA ORB interface. You do not need this if you are running J2SDK.
netutil.jar: Utility classes, including the implementation of the proprietary encryption algorithm from SAS Institute, that are used by Java development tools provided by SAS.
idl2java.jar: A CORBA IDL-to-Java compiler. This is a stand-alone development tool that may aid in CORBA development. All of the stubs in iomprx.jar were generated with this tool. This archive also contains an HTML file called idl2java.html that explains how to use this tool.
binder.jar: A stand-alone tool that may aid in the development of Java CORBA servers and event listeners. This archive also contains an HTML file called binder.html that explains how to use this tool.

Additional Requirements

If you are using WorkspaceFactory and LDAP to obtain an IWorkspace object, which is used in constructing a JDBC connection object, you need the following JAR files: jndi.jar, ldap.jar, and providerUtil.jar. These files are not provided in the IOM Java Cl ient Archive.

Note: These three JAR files are not necessary if you are using Java 2 SDK, Standard Edition, v 1.3 (J2SDK).

The above JAR files are part of the Java Naming and Directory Interface (JNDI) API from SUN Microsystems. The JNDI API is a standard extension to the Java platform. You can download the JAR files from the JavaSoft site at www.javasoft.com/products/jndi/.

If you are using WorkspaceFactory to obtain an IWorkspace object without using LDAP, you do not need to download the above JAR files.

CLASSPATH Environment Variable

If you are setting up the Java client on a local machine, you must set your CLASSPATH environment variable. Setting your CLASSPATH environment variable ensures that your applets have access to the classes provided in our packages.

The exact steps for setting CLASSPATH are specific to your machine type as well as how you plan to use your programs.

Setting CLASSPATH in a Windows Environment

The documented Windows installation process installs the expanded archive in the directory C:\inttech\iomjava. If you installed the archive in this directory, set CLASSPATH by adding the following line to your autoexec.bat file:

  set CLASSPATH=C:\inttech\iomjava;

If you do not unzip the JAR files, then set CLASSPATH as follows:

  set CLASSPATH=C:\inttech\iomjava\iomdriver.jar;
  C:\inttech\iomjava\brgorb.jar;C:\inttech\iomjava\orb.jar;C:\inttech\
  iomjava\iomprx.jar;C:\inttech\iomjava\netutil.jar

Setting CLASSPATH in a UNIX Environment

The documented UNIX installation process installs the expanded archive in the directory /usr/local/lib/inttech/iomjava. If you installed the archive in this director, set CLASSPATH by executing the following command from a command prompt:

  export CLASSPATH=/usr/local/lib/inttech/iomjava;