
           Install readme file for InterClient 1.12

       (c) 1997 InterBase, Inc. All rights reserved.
_________________________________________________________________
Contents:

     I.  Installation Note for Windows NT and 95
    II.  Uninstalling on Windows NT and 95
   III.  Installation Note for Solaris and HP-UX
    IV.  Installation Options
     V.  Testing your Local Installation
    VI.  Software Expiration

__________________________________________________________________
Installation Note for Windows NT and 95

  If you have a previous release of InterClient installed on
  this machine, you MUST uninstall it before continuing.

__________________________________________________________________
Uninstalling on Windows NT and 95.

  Before uninstalling, you should first stop the InterServer 
  service or application if it is running, and then remove the 
  service using the InterServer Configuration Utility.

  When uninstalling on NT, use the add/remove program icon in
  the NT control panel.  On Windows 95, there is an uninstall 
  icon in the InterClient program group if InterServer was 
  previously installed.

__________________________________________________________________
Installation Note for Solaris and HP-UX
 
  After the download files have been extracted using the tar
  command (tar -xvf InterClientV10.tar), a directory will
  be created named interclient_install_temp_dir containing
  the following files.

    install.sh      : the installation program
    interclient.tar : components to be extracted by install.sh

  The installation process creates a log file of the installation 
  session.  It is important to retain the log file in the
  installation directory.  
   - It contains the configuration information specific to your 
     site necessary to complete the installation.
   - It contains a log of your installation choices. It will be 
     required should you require technical support. 

  On both UNIX and 95/NT, the following entry must occur in the
  /etc/services file or the NIS services map:

            interserver 3060/tcp

  You must add this line manually.

  On both UNIX and 95/NT, the following entry must occur in the
  /etc/services file or the NIS services map:

    interserver 3060/tcp

  You must add this line manually.

  An entry in the /etc/inetd.conf file is also required:

    interserver stream tcp nowait root /usr/interclient/bin/interserver interserver

  You must add this line manually also.

  After adding these entries, either reboot the system or restart the
  inet daemon.  To restart the inet daemon, use the ps command to
  discover the process id of the inetd process:

     ps -e | grep inetd
  or 
     ps -ax | grep inetd

  The number in the output column 'PID' is the process id of the inet 
  daemon.  Use the process id with the following command to restart the 
  inet daemon:

    kill -HUP <PID>

  After installing, be sure to add /usr/interclient/interclient.jar 
  to your CLASSPATH.

__________________________________________________________________
Installation Options

During installation you will be prompted to choose one of the 
following.

   o Development Environment

      This selection installs the full development environment.
       - InterClient classes are installed for local JDBC development.
       - InterServer is installed for local or remote access to an InterBase
	     server.

   o Development and Web Deploy Environment

      This selection installs the full development environment
      as above.  In addition the InterClient classes and documentation
      are copied to the document root directory of your web server.
       - InterClient classes are installed for local JDBC development.
       - InterServer is installed for local or remote access to an InterBase
	     server.
       - In addition, InterClient classes are copied to the 
	     document root directory of your Web server.

   o Deploy to Web Server Only

      This selection installs the InterClient classes and documentation
      only to the document root directory of your Web server.
       - InterServer is installed for use by local or remote clients.
       - InterClient classes are copied to the document root directory 
          of the Web server.

   o Client Development Only

      This selection installs the InterClient classes and documentation
      on the local client for use in local Java application development
      against a remote server with a separately installed InterServer.
       - InterClient classes are installed for local development.

__________________________________________________________________
Testing your Local Installation

  First, verify that the installation automatically appended your
  CLASSPATH with <install-dir>/interclient.jar.

  Second, on Windows NT/95, select the InterServer Configuration 
  Utility icon in the InterClient program group and start the
  InterServer service or application (usually, but not necessarily,
  on your InterBase server).  On Unix the interserver service is 
  started automatically by inetd if your /etc/services and 
  /etc/inetd.conf are configured properly.

  Finally, on Windows NT/95, select the Communication Diagnostics
  icon from the InterClient program group.  If Java is installed
  on your local machine and interclient.jar is in your CLASSPATH,
  then a GUI will appear for making a test connection using the
  locally installed driver.  Alternatively, and on Unix, you may
  invoke the Communiation Diagnostics Utility from the command line
    java interbase.interclient.utils.CommDiag

  Note: the instructions outlined above are not relevant for testing
  the deployment of InterClient applets from a web server.
  See Readme.txt for instructions on testing an applet configuration.

__________________________________________________________________
Software Expiration

  This product release of InterClient will expire, but continue to 
  function, on Dec 31, 1988. 
 
  Expired product releases of InterClient will accept connections,
  but will tag the connection with an ExpiredDriverWarning.
  Expired beta releases of InterClient may throw an 
  ExpiredDriverException and refuse connections.

  Upon expiration, it is suggested that you upgrade both InterClient
  and InterServer driver components by downloading a recent release 
  from http://www.interbase.com.

---------------------------------END----------------------------------
