Assumptions and Requirements

This section discusses basic assumptions about your environment and requirements of your system so that you can run Oracle SQLJ.

Assumptions About Your Environment

The following assumptions are made about the system on which you will be running Oracle SQLJ.

• You have a standard Java environment that is operational on your system. This would typically be using a Sun Microsystems JDK, but other implementations of Java will work. Make sure you can run Java (typically java) and your Java compiler (typically javac).

  To translate and run Oracle SQLJ applications on a Sun JDK you must use a JDK 1.2.x or 1.1.x version, with an appropriate JDBC driver. There are Oracle JDBC Thin and OCI drivers for either of these JDK versions.

  For more information, see "Supported JDK Versions".

• You can already run JDBC applications in your environment.

  If you are using an Oracle database and Oracle JDBC driver, then you should complete the steps in Chapter 2, "Getting Started", of the Oracle8i JDBC Developer's Guide and Reference. You can also refer to Chapter 1, "Overview", of that document for information about the Oracle JDBC drivers and how to decide which is appropriate for your situation.

  Notes: If you are using a non-Oracle JDBC driver, you must do the following: Modify connect.properties, as discussed in "Set Up the Runtime Connection". Modify the sample applications, as discussed in "Driver Selection and Registration for Runtime", so that your driver is registered before the call to the Oracle.connect() method.

Requirements for Using Oracle SQLJ

The following are required to use Oracle SQLJ:

• a JDBC driver implementing the standard java.sql JDBC interfaces from Sun Microsystems

  Oracle SQLJ works with any standards-compliant JDBC driver.

• a database system that is accessible using your JDBC driver

• class files for the SQLJ translator, SQLJ profile customizer, and SQLJ runtime

  These class files are all available in the file:

  [Oracle Home]/sqlj/lib/translator.zip
  
  

  Notes: If you have a system where you will be running only SQLJ applications that have already been translated, compiled, and customized, then you will need only the runtime classes, not the translator or profile customizer classes. The runtime classes are in the file: [Oracle Home]/sqlj/lib/runtime.zip This is a subset of the translator.zip file. The translator.zip and runtime.zip files are uncompressed for maximum portability.

Supported JDK Versions

If you are using a Sun Microsystems JDK, note that the 8.1.6 release of Oracle SQLJ works in both the JDK 1.2.x and JDK 1.1.x environments. There are just single versions of the translator.zip and runtime.zip files that work in either environment.

Note the following regarding migration of SQLJ source code:

• If you translate under JDK 1.1.x, Oracle supports running the application under either JDK 1.1.x or JDK 1.2.x. (This assumes you do not have any JDBC code that uses the oracle.jdbc2 package. This is how Oracle JDBC supported JDBC 2.0 types under JDK 1.1.x.)

• If you translate under JDK 1.2.x, Oracle supports running the application under JDK 1.2.x.

Be sure to use an appropriate version of the JDBC driver. See "PATH and CLASSPATH for Oracle JDBC".

Note that as of release 8.1.6, neither Oracle SQLJ nor Oracle JDBC support JDK 1.0.2. This includes applets running in browsers that use JDK 1.0.2 except where special preparations have been made. (Applets are not discussed here. Refer to "Running SQLJ in Applets".)

JServer Configuration

This document presumes that system configuration issues are outside the duties of most SQLJ developers. Therefore, configuration of the Oracle8i JServer (formerly referred to as the Java Option) is not covered here. For information about setting Java-related configuration parameters (such as JAVA_POOL_SIZE), see the Oracle8i Java Developer's Guide.

If you need information about configuring the multi-threaded server, dispatcher, or listener (which may be particularly relevant if you are coding Enterprise JavaBeans or CORBA objects), see the Net8 Administrator's Guide.

---