FM / AdministratorManual

/usr/share/doc/unixODBC/doc/AdministratorManual/

/usr/share/doc/unixODBC/doc/AdministratorManual

Name	Size	Mode	Actions
index.html	12313	0644	edit dl rm
odbcinst.html	9660	0644	edit dl rm
php3.html	1992	0644	edit dl rm
unixODBC.gif	858	0644	edit dl rm
unixODBCsetup.html	12892	0644	edit dl rm

Edit: /usr/share/doc/unixODBC/doc/AdministratorManual/index.html (12313B)

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <meta name="Author" content="Peter Harvey">
 <meta name="GENERATOR" content="Mozilla/4.77C-CCK-MCD Caldera Systems OpenLinux [en] (X11; U; Linux 2.4.2 i686) [Netscape]">
 <title>unixODBC - Administrator Manual</title>
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000">
<img SRC="unixODBC.gif" height=32 width=32>unixODBC
 
<hr WIDTH="100%">
<center>ADMINISTRATOR MANUAL</center>

Introduction
Welcome to the unixODBC Administrator Manual.
This manual has been created to help system administrators install and
manage the ODBC sub-system.
Getting Started
At this point you know what ODBC is and
what it can offer the Users of your system(s) - now you want to get it
on your system(s).
Platforms
unixODBC implements ODBC on the following
platforms;
<ul>
<li>
Linux</li>

<li>
and various flavours of UNIX</li>
</ul>
This manual covers all platforms and will
give special indication of differences for any particular platform.
Do You Have It?
 &nbsp;
 It is possible that your system already
has unixODBC installed. The best way to check for this is to drop to a
terminal and execute 'odbcinst --version'.
 &nbsp;
<table BORDER COLS=1 WIDTH="100%" BGCOLOR="#FFFFCC" NOSAVE >
<tr>
<td>[root@p12 qt]# odbcinst --version
 unixODBC 2.1.1
 [root@p12 qt]#</td>
</tr>
</table>

Downloading
You can get the source from <a href="http://sourceforge.net/projects/unixodbc">Source
Forge</a>.
You can get binary distributions from various
places. One place to look is with the vendor of your operating system.
You can also go to <a href="http://sourceforge.net/projects/unixodbc/">Source
Forge</a> and take a look at the Home Page to see the availability and
location of binary distributions.
Whether you choose a binary distribution
or source code depends largely upon your site policy and which operating
system you are working with. I recommend the following;
<ul>
<li>
Mac OSX - use a binary distribution</li>

<li>
Others - use a source distribution (tar-ball
NOT CVS)</li>
</ul>

 Installing From Source
There are two options when installing from
source. You can install from a source distribution (a gzipped tar-ball)
or from CVS. In either case you will find README files in the main directory
which should help you build and install unixODBC.
The unixODBC build process uses the GNU&nbsp;auto-tools.
This will be a concern to you if you choose to build from CVS because you
must start the build process with 'make -f Makefile.cvs' - this, in turn,
uses the GNU&nbsp;auto-tools (i.e. automake, autoconf) to build a 'configure'
script. Unfortunately; the GNU&nbsp;auto-tools can be very version sensitive.
See the README file(s) for more on this if you plan to build from CVS source.
 &nbsp;
<table BORDER COLS=1 WIDTH="100%" BGCOLOR="#FFFFCC" NOSAVE >
<tr>
<td>[root@p12 unixODBC]# make -f Makefile.cvs&nbsp;</td>
</tr>
</table>

You do not have to 'make -f Makefile.cvs'
when using a source distribution. Regardless of whether you choose to use
CVS or a source distribution you will want to execute the 'configure' script
with options appropriate for your needs.
 &nbsp;
<table BORDER COLS=1 WIDTH="100%" BGCOLOR="#FFFFCC" NOSAVE >
<tr>
<td>[root@p12 unixODBC]# ./configure --help</td>
</tr>
</table>

The 'configure' script will check your
system for features of interest and build some make files as well as create
some include file(s) which will ensure that unixODBC will build without
errors and only with features supported by your operating system.
At this point it is important to think
about whether or not GUI&nbsp;tools are important to you (and your Users).
The 'configure' script will try to detect support for the GUI&nbsp;applications
in unixODBC and will build them if such support exists. unixODBC&nbsp;includes
GUI tools based upon the Qt class library and GTK. The Qt based tools will
be built if libqt*so can be found. Linux systems will probably have this.
You can get this from <a href="http://www.trolltech.com">Troll Tech</a>.
Now you are ready to build the sources.
Do this with the usual build sequence of commands.
 &nbsp;
<table BORDER COLS=1 WIDTH="100%" BGCOLOR="#FFFFCC" NOSAVE >
<tr>
<td>[root@p12 unixODBC]# make
 [root@p12 unixODBC]# make install</td>
</tr>
</table>

Mac OSX: The
Apple folks seem to be grappling with their support for the GNU auto-tools
at the time of this writing. I recommend installing from a binary distribution
of unixODBC. If you must install from source, and you are having problems
with the GNU&nbsp;auto-tools, then you may want to try the qmake build.
The qmake build process is not well documented at this time. People familiar
with qmake should be able to build unixODBC with the included qmake project
files.
Installing From Binary
RPM
Various RPMs exist for unixODBC. The best
idea is to use any RPM files you can from your O/S vendor. Typically RPM&nbsp;distributions
break unixODBC into more than one RPM distribution such as; core, and GUI.
Mac OSX Disk Images
A binary distribution for OSX has recently
become available in the downloads section at <a href="http://www.codebydesign.com/DataArchitect">CodeByDesign</a>.
This includes proper Mac installs. The install should be done in the following
order;
<ol>
<li>
Qt Runtime</li>

<li>
unixODBC</li>

<li>
drivers in any order</li>
</ol>
Others
Proper install packages are also available
for other platforms such as the Debian package format for Debian Linux.
Check with the O/S vendor.
Where Are Installed Files
The location for files vary somewhat depending
upon how you installed unixODBC&nbsp;(source or binary) and which platform
you installed on. Furthermore; the location can be changed during a source
install by './configure --prefix='.
Typically;
<ul>
<li>
library files will go in /usr/lib or /usr/local/lib</li>

<li>
binaries will go in /usr/bin or /usr/local/bin</li>

<li>
system config files will go in /etc or /usr/local/etc</li>
</ul>
The system config files are;
<ul>
<li>
odbcinst.ini - list of registered drivers</li>

<li>
odbc.ini - system data source names</li>
</ul>
The location of the system config files can
be changed by setting the ODBCSYSINI&nbsp;environment variable at run-time.
The system config files can be edited using a simple text editor but it
is recommended that you use the ODBCConfig GUI&nbsp;tool or the odcinst
command-line tool because they will validate the reading and writing of
these files while ensuring that the current location is used.
Mac OSX: The
OSX binary install will use; /usr/lib, /usr/bin, /Applications/Utilities
and /etc.
Post Install
You now have an ODBC&nbsp;sub-system installed
on your system(s). What is the system administrators role from here? The
system administrator is the only person who can install and register ODBC&nbsp;drivers
and create/edit/delete system Data Source Names (DSN).
Drivers
Drivers should be installed and configured
based upon the driver vendors instructions. Many drivers do not include
a full install process - lacking the driver registration step. These drivers
can be registered using the ODBCConfig GUI tool or the odbcinst command-line
tool.
System DSN
These can be created using the ODBCConfig
GUI&nbsp;tool or the odbcinst command-line tool. ODBCConfig is the preferred
method but not all drivers have a User Interface (U.I.) part.
Mac OSX: In
some cases the ODBCConfig icon will not open. In such a case you should
drop to a terminal window and use the open command.
 &nbsp;
<table BORDER COLS=1 WIDTH="100%" BGCOLOR="#FFFFCC" NOSAVE >
<tr>
<td># open /Applications/Utilities/ODBCConfig.app</td>
</tr>
</table>

Summary
unixODBC implements an ODBC&nbsp;sub-system
for a wide variety of platforms. unixODBC can be installed using; binary,
source and source from CVS. Drivers can be installed using installation
methods created by the driver vendor with unixODBC tools available to fill
any gaps. ODBC&nbsp;system information can be managed using; ODBCConfig,
odbcinst, or a text editor.
 &nbsp;

<hr WIDTH="100%">
 &nbsp;
 &nbsp;
</body>
</html>

cmd: