| Products | Minisoft News | Events | Downloads | Product Manuals
 
  News

Minisoft Releases PCI Compliant Versions of ODBC, JDBC, and OLE DB

Demo and Updates


FREE Demo! - Click Here

Update Registration

Documentation


Release Notes

Installation Release Notes

JDBC Manual

FAQ

Product Review


What is JDBC?

Brochure -
"Minisoft PCI Compliant"

Tracing Facilities

Java.jar files

URL Formatting

Using SQL Functions

JDBC for UNIX

Sun's Java™ site http://www.javasoft.com. Contains references to the JDK download page, books on Java™, and general Java™ examples.

Information on setting properties can be found at Creating a File DSN (SQLDriverConnect)

 
   

UNIX

Minisoft JDBC driver components for HP-UX

The Minisoft JDBC driver can be implemented in a 2-tier and/or 3-tier configuration on HP-UX. In the 2-tier scenario, a JAVA program running on the HP-UX machine will use the JDBC driver to access data on a HP e3000 server. In the 3-tier configuration a JAVA program running on a client machine connected to the HP-UX machine will use the JDBC driver to access data on a HP e3000 server.


Extracting the HP-UX files.

The files for the JDBC driver are contained in a shell archive named 3KJDBC. Transfer this file to the HP9000 using ftp in binary mode. To extract the files, type:

    $sh 3KJDBC

The following files will be extracted into the current directory:

    3KMidTierListener - The mid-tier listener program for 3-tier deployment
    3kjdbc.sl - The sharable library for 2-tier deployment
    MSJDBCThin.jar - The JDBC driver classes for 3-tier deployment
    MSJDBCFat.jar - The JDBC driver classes for 2-tier deployement

At this point the 3KJDBC file is no longer needed and may be removed.


Configuration for 3-tier deployment.

The file MSJDBCThin.jar should be moved to the client machine(s) or moved into a web server directory that the clients can load from. JAVA programs running on the clients will need to access this directory when they make JDBC API calls.

The file 3KMidTierListener can be put into any directory. 3KMidTierListener is designed to run under inetd. First a service name for it needs to be entered into the /etc/services file ( or NIS configuration ). Any service name that is not being used can be entered. The port number for the service can be any port number that does not conflict with one that is already being used, but the JDBC driver will connect to port 30504 by default. The following is an example of an entry in the /etc/services file for a new service for 3KMidTierListener:

    jdbcd 30504/tcp # JDBC service

Next an entry in the /etc/inetd.conf file must be made to instruct inetd how respond to connection requests for the above service. The following is a sample entry in /etc/inetd.conf:

    jdbcd stream tcp nowait root /usr/minisoft/3KMidTierListener 3KMidTierListener

This example assumes that the program file 3KMidTierListener was installed in the /usr/minisoft directory.

After these configuration changes are made inetd should be stopped and restarted.

Now clients using the Minisoft JDBC driver can use the HP9000 as a mid-tier machine to access data on a HP e3000 machine.


Configuration for 2-tier deployment.

The file MSJDBCFat.jar should be moved into a directory that will be in the user's CLASSPATH environment variable. The file 3kjdbc.sl should be moved into a directory that will be in the user's SHLIB_PATH environment variable. If the MSJDBCFat.jar file is put in the /usr/minisoft directory, then the CLASSPATH variable should be set as follows:

    export CLASSPATH=/usr/minisoft/MSJDBCFat.jar

You will also need to add other directories that contain the user's JAVA programs to the CLASSPATH variable.

If the file 3kjdbc.sl is put in the /usr/minisoft directory, then the SHLIB_PATH variable should be set as follows:

    export SHLIB_PATH=/usr/minisoft

Typically these statements are put in a user's .profile file.