Tags:
create new tag
view all tags

Configuring APPX and RDBMS

Compatibility with newer versions of popular databases is among the many features of APPX 5.0 & higher. This page gives some examples of configuring APPX to work with various RDBMS's

Oracle

APPX has been tested with the following versions of Oracle:

  • Oracle 10g R2 (10.2.0.1)
  • Oracle 11g
  • Oracle 12c

The Oracle connectivity is provided by the Oracle Instant Client.

APPX to Oracle quick installation steps, with the assumption that you have a working install of Oracle 10g R2:

  • Install Oracle Instant Client Basic.
  • Make the Oracle Instant Client library files visible to the system with the ldconfig tool or it's equivalent.
  • Set, in either the APPX Login Manager's daemon environment or the appx.env file, the APPX environment variable APPX_OCI_LIB equal to the file name of the liblcntsh.so contained in the Oracle Instant Client library files (For example APPX_OCI_LIB=libclntsh.so.10.1).
  • Define APPX FMS settings.

APPX to Oracle detailed installation example:

Here are the steps I used to make connection with APPX and Oracle 10gR2 with both installed on the same Red Hat Enterprise 5.1, 32 bit server. I assume that you already have a working installation of Oracle 10g R2.

Create directory for Oracle Instant Client bundle to download to.

I'm going to create a directory to place the zipped bundled Oracle Instant Client files. For my example, I'm going to use /usr/local/src/oracle/instantclient/.

[root@tubes /]# *mkdir -p /usr/local/src/oracle/instantclient/* 
[root@tubes /]# *cd /usr/local/src/oracle/instantclient/*
[root@tubes instantclient]# 

Download the Oracle Instant Client files for Linux.

APPX requires at least the Basic package, but it is recommended that you grab the SQL*Plus package too for debugging. http://www.oracle.com/technology/tech/oci/instantclient/index.html

For 10gR2

If you are running Oracle 10gR2, then use the 10gR2 Instant Client. At the time this document was created, the current version for Linux X86 is 10.2.0.4, oracle-instantclient-basic-10.2.0.4-1.i386.zip (34,687,861 bytes), and oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip (744,730 bytes). Place the downloaded files in the /usr/local/src/oracle/instantclient/ directory.

For 11g

If you are running Oracle 11g, then use the 11g Instant Client. At the time this document was created, the current version is 11.1.0.6.0 , basic.zip (42,285,643 bytes), and sqlplus.zip (784,417 bytes). Place the downloaded files in the /usr/local/src/oracle/instantclient/ directory, then unzip them.

Place the basic and sqlplus zipped files into /usr/local/src/oracle/instantclient/, and unzip them:

[root@tubes instantclient]# *pwd*
/usr/local/src/oracle/instantclient
[root@tubes instantclient]# *ls -la*
total 34656
drwxr-xr-x 2 root root     4096 Jun  5 15:01 .
drwxr-xr-x 3 root root     4096 Jun  5 14:59 ..
-rw-r--r-- 1 root root 34687861 Jun  5 15:01 oracle-instantclient-basic-10.2.0.4-1.i386.zip
-rw-r--r-- 1 root root   744730 Jun  5 15:01 oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip
[root@tubes instantclient]# *unzip oracle-instantclient-basic-10.2.0.4-1.i386.zip* 
Archive:  oracle-instantclient-basic-10.2.0.4-1.i386.zip
  inflating: instantclient_10_2/BASIC_README  
  inflating: instantclient_10_2/classes12.jar  
  inflating: instantclient_10_2/genezi  
  inflating: instantclient_10_2/libclntsh.so.10.1  
  inflating: instantclient_10_2/libnnz10.so  
  inflating: instantclient_10_2/libocci.so.10.1  
  inflating: instantclient_10_2/libociei.so  
  inflating: instantclient_10_2/libocijdbc10.so  
  inflating: instantclient_10_2/ojdbc14.jar  
[root@tubes instantclient]# *unzip oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip*
Archive:  oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip
  inflating: instantclient_10_2/SQLPLUS_README  
  inflating: instantclient_10_2/glogin.sql  
  inflating: instantclient_10_2/libsqlplus.so  
  inflating: instantclient_10_2/libsqlplusic.so  
  inflating: instantclient_10_2/sqlplus  
[root@tubes instantclient]# *ls -la*
total 34660
drwxr-xr-x 3 root root     4096 Jun  5 15:01 .
drwxr-xr-x 3 root root     4096 Jun  5 14:59 ..
drwxr-xr-x 2 root root     4096 Jun  5 15:01 instantclient_10_2
-rw-r--r-- 1 root root 34687861 Jun  5 15:01 oracle-instantclient-basic-10.2.0.4-1.i386.zip
-rw-r--r-- 1 root root   744730 Jun  5 15:01 oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip
[root@tubes instantclient]# *ls -la instantclient_10_2/*
total 102424
drwxr-xr-x 2 root root     4096 Jun  5 15:01 .
drwxr-xr-x 3 root root     4096 Jun  5 15:01 ..
-rw-rw-r-- 1 root root      238 Feb 17 03:57 BASIC_README
-r--r--r-- 1 root root  1609607 Feb 17 03:57 classes12.jar
-rwxrwxr-x 1 root root    67766 Feb 17 03:57 genezi
-r--r--r-- 1 root root     1525 Feb 17 03:58 glogin.sql
-rwxrwxr-x 1 root root 19076649 Feb 17 03:57 libclntsh.so.10.1
-r-xr-xr-x 1 root root  5656445 Feb 17 03:57 libnnz10.so
-rwxrwxr-x 1 root root  1398244 Feb 17 03:57 libocci.so.10.1
-rwxrwxr-x 1 root root 72698427 Feb 17 03:57 libociei.so
-r-xr-xr-x 1 root root   120443 Feb 17 03:57 libocijdbc10.so
-r-xr-xr-x 1 root root  1434263 Feb 17 03:58 libsqlplusic.so
-r-xr-xr-x 1 root root  1069221 Feb 17 03:58 libsqlplus.so
-r--r--r-- 1 root root  1555682 Feb 17 03:57 ojdbc14.jar
-r-xr-xr-x 1 root root     8903 Feb 17 03:58 sqlplus
-rw-rw-r-- 1 root root      242 Feb 17 03:58 SQLPLUS_README
[root@tubes instantclient]# 

Place unzipped Oracle Instant Client files into permanent installation target directory.

Now move the unzipped directory (instantclient_10_2) that contains both the basic and SQL*Plus files from the Oracle Instant Client, into the desired permanent directory. In my example, I'm using /usr/local/, so that the Oracle files will be in a directory /usr/local/instantclient_10_2/.

[root@tubes instantclient]# *pwd*
/usr/local/src/oracle/instantclient
[root@tubes instantclient]# *ls -la*
total 34660
drwxr-xr-x 3 root root     4096 Jun  5 15:01 .
drwxr-xr-x 3 root root     4096 Jun  5 14:59 ..
drwxr-xr-x 2 root root     4096 Jun  5 15:01 instantclient_10_2
-rw-r--r-- 1 root root 34687861 Jun  5 15:01 oracle-instantclient-basic-10.2.0.4-1.i386.zip
-rw-r--r-- 1 root root   744730 Jun  5 15:01 oracle-instantclient-sqlplus-10.2.0.4-1.i386.zip
[root@tubes instantclient]# *ls /usr/local/*
appx  appx.tgz  basic.zip  bin  etc  games  include  lib  libexec  sbin  share  src
[root@tubes instantclient]# *mv instantclient_10_2/ /usr/local/*
[root@tubes instantclient]# *ls /usr/local/*
appx  appx.tgz  basic.zip  bin  etc  games  include  instantclient_10_2  lib  libexec  sbin  share  src
[root@tubes instantclient]# 

Configure the operating system's dynamic linker run time bindings

Now we must register the Oracle Instant Client library files with the system to make the shared library's path known. I'm going to use ldconfig.

[root@tubes instantclient]# *ldconfig -v|grep libclntsh*
[root@tubes instantclient]# *ldconfig -v|grep instant*
[root@tubes instantclient]# 
[root@tubes instantclient]# *cat /etc/ld.so.conf*
include ld.so.conf.d/*.conf
[root@tubes instantclient]# *echo /usr/local/instantclient_10_2/ >> /etc/ld.so.conf*
[root@tubes instantclient]# *cat /etc/ld.so.conf*
include ld.so.conf.d/*.conf
/usr/local/instantclient_10_2/
[root@tubes instantclient]# 

Build cache used by the operating system's run-time linker

Now, let's rebuild the ldconfig cache, and verify that the library's are available system wide.

[root@tubes instantclient]# *ldconfig*
[root@tubes instantclient]# *ldconfig -v|grep libclntsh*
 libclntsh.so.10.1 -> libclntsh.so.10.1
[root@tubes instantclient]# *ldconfig -v|grep instant*
/usr/local/instantclient_10_2:
[root@tubes instantclient]# 

Identify version of libclntsh.so that is included with downloaded Oracle Instant Client bundle

APPX needs to know the name of the Oracle libclntsh.so file on your system. This file name changes from version to version. We must now identify the libclntsh file name that was distributed in the Oracle Instant Client bundle. Look inside the instantclient directory for a file that begins with libclntsh. To show you examples of Oracle Instant Client 10.2 and Oracle Instant Client 11.1, I have installed both versions in /usr/local/.

[joe@tubes instantclient_10_2]$ *ls -la /usr/local/instantclient_1*/libclnt**
-rwxrwxrwx 1 root   root     19076649 Feb 17 03:57 /usr/local/instantclient_10_2/libclntsh.so.10.1
-rwxrwxrwx 1 root   root     35295891 Aug  1  2007 /usr/local/instantclient_11_1/libclntsh.so.11.1
[joe@tubes instantclient_10_2]$ 

As you can see my libclntsh files are libclntsh.so.10.1, which came bundled with the Oracle Instant Client 10.2 Basic bundle, and libclntsh.so.11.1, which came bundled with the Oracle Instant Client 11.1 Basic bundle.

To let APPX know the version of the Instant client you have installed, perform just one of the following two options:
Create libclntsh.so symbolic link and set the APPX_OCI_DIR environment variable

  • I can now either create a symbolic link named libclntsh.so that points to the version I want to use and set the APPX_OCI_DIR environment variable equal to the location of the Oracle Instant Client files:
[root@tubes appx]# *cd /usr/local/instantclient_10_2/*
[root@tubes instantclient_10_2]# *ln -s /usr/local/instantclient_10_2/libclntsh.so.10.1 /usr/local/instantclient_10_2/libclntsh.so*
[root@tubes appx]# *ls -la /usr/local/instantclient_10_2/libclntsh.so*
lrwxrwxrwx 1 root root 47 Jun  5 15:56 libclntsh.so -> /usr/local/instantclient_10_2/libclntsh.so.10.1
[root@tubes instantclient_10_2]# 
[root@tubes appx]# *grep APPX_OCI_DIR /usr/local/appx/data/appx.env*
[root@tubes instantclient_10_2]# 
[root@tubes appx]# *echo APPX_OCI_DIR=/usr/local/instantclient_10_2/ >> /usr/local/appx/data/appx.env*
[root@tubes appx]# *grep APPX_OCI_DIR /usr/local/appx/data/appx.env*
APPX_OCI_DIR=/usr/local/instantclient_10_2/
[root@tubes appx]# 

Set APPX_OCI_LIB

  • Or I can set an APPX environment variable equal to the name of the file. First let's see if it is set in the %APPXPATH%/appx.env file:

[root@tubes appx]# 
[root@tubes appx]# *grep APPX_OCI_LIB /usr/local/appx/data/appx.env*
[root@tubes appx]# 
[root@tubes appx]# *echo APPX_OCI_LIB=libclntsh.so.10.1 >> /usr/local/appx/data/appx.env*
[root@tubes appx]# 
[root@tubes appx]# *grep APPX_OCI_LIB /usr/local/appx/data/appx.env*
APPX_OCI_LIB=libclntsh.so.10.1
[root@tubes appx]# 

Use the Oracle Instant Client's version of SQL*Plus to verify connectify to Oracle.

Now let's verify that we can connect to Oracle using Oracle's SQL*Plus tool. I'm going to use the following parameters for my example, be sure and use values that are correct for your Oracle instance. user=scott, password=password, server=tubes, port=1521, and Oracle Instance=appx.

[root@tubes instantclient_10_2]# */usr/local/instantclient_10_2/sqlplus scott/password@tubes:1521/appx*
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Jun 4 09:17:55 2008
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> *show all*
appinfo is OFF and set to "SQL*Plus"
arraysize 15
autocommit OFF
autoprint OFF
autorecovery OFF
autotrace OFF
blockterminator "." (hex 2e)
btitle OFF and is the first few characters of the next SELECT statement
cmdsep OFF
colsep " "
compatibility version NATIVE
concat "." (hex 2e)
copycommit 0
COPYTYPECHECK is ON
define "&" (hex 26)
describe DEPTH 1 LINENUM OFF INDENT ON
echo OFF
editfile "afiedt.buf"
embedded OFF
escape OFF
escchar OFF
FEEDBACK ON for 6 or more rows
flagger OFF
flush ON
heading ON
headsep "|" (hex 7c)
instance "local"
linesize 80
lno 14
loboffset 1
logsource ""
long 80
longchunksize 80
markup HTML OFF HEAD "" BODY "" TABLE "border='1' width='90%' align='center' summary='Script output'" SPOOL OFF ENTMAP ON PREFORMAT OFF
newpage 1
null ""
numformat ""
numwidth 10
pagesize 14
PAUSE is OFF
pno 0
recsep WRAP
recsepchar " " (hex 20)
release 1002000100
repfooter OFF and is NULL
repheader OFF and is NULL
serveroutput OFF
shiftinout INVISIBLE
showmode OFF
spool OFF
sqlblanklines OFF
sqlcase MIXED
sqlcode 0
sqlcontinue "> "
sqlnumber ON
sqlpluscompatibility 10.2.0
sqlprefix "#" (hex 23)
sqlprompt "SQL> "
sqlterminator ";" (hex 3b)
suffix "sql"
tab ON
termout ON
timing OFF
trimout ON
trimspool OFF
ttitle OFF and is the first few characters of the next SELECT statement
underline "-" (hex 2d)
USER is "SCOTT"
verify ON
wrap : lines will be wrapped
SQL> *quit*
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[root@tubes instantclient_10_2]# 

Configure APPX FMS settings

Well, that looks good. Let's configure our FMS settings inside APPX and make a connection!

  • In APPX, Go to System Administration, then File Management, then FMS Groups.

oracle-fms-01.jpg

  • Create an FMS group with an appropriate name, and specify type 5.

oracle-fms-02.jpg

  • File in the Server Name and Table Naming Scheme in the FMS Group Attributes of your new FMS group. The Server Name field has a format of ORACLE-HOST-NAME:ORACLE-PORT/ORACLE-SID. The Table Naming Scheme could be picked from the suggestions shown when clicking on the Hints button.

oracle-fms-03.jpg

  • Under Identities, define at least a default identity.

oracle-fms-04.jpg

  • Enter the Oracle account to use for the Default Identity, leave Realm empty.

oracle-fms-05.jpg

  • Enter the Oracle account's password.

oracle-fms-06.jpg

This completes the setup. To move any existing data to Oracle, use Data File Management to export the file(s), change the FMS type and name under File Specifications, then import the data.

ODBC

The ODBC connection type allows you to connect to any RDBMS that supports ODBC. This example uses MySQL.

MySQL 5.0.22

Quick installation steps of the APPX to MySQL connection:

  • Install MySQL.
  • Install UnixODBC
  • Install mysql-connector-odbc (version 3.51.22 or newer)
  • Define DSN files, odbc.ini and odbcinst.ini.
  • Set, in either the APPX Login Manager's daemon environment or the appx.env file, the APPX environment variable APPX_ODBC_LIB equal to the file name of the unixodbc shared library file from the UnixODBC install. (For example APPX_ODBC_LIB=/usr/lib/libodbc.so).
  • Define APPX FMS settings.

Detailed installation example of the APPX to MySQL connection:

Here are the steps I used to make connection with APPX and MySQL 5.0.22 with both installed on the same Red Hat Enterprise 5.1, 32 bit server. The MySQL and UnixODBC will be provided by Red Hat, and the mysql-connector-odbc will be provided by MySQL. Red Hat's Yum repositories do contain mysql-connector-odbc, but at the time of this test, it was 3.51.12 (too old). For this connection we need 3.51.22 or newer. We'll get this component from the MySQL.com website.

Download mysql-connector-odbc from MySQL.com website.

You should go to MySQL.com's ODBC Connector download site and get the mysql-connector-odbc in the format that is right for your platform. My test server is Red Hat 5.1 32 bit, so I'll download the RPM format for x86 Red Hat.

[root@tubes ~]# *cd /usr/local/src*
[root@tubes src]# *mkdir mysql-connector-odbc.from.mysql.com*
[root@tubes src]# *cd mysql-connector-odbc.from.mysql.com/*
[root@tubes mysql-connector-odbc.from.mysql.com]# *wget http://mirror.trouble-free.net/mysql_mirror/Downloads/Connector-ODBC/3.51/mysql-connector-odbc-3.51.25-0.i386.rpm*

Resolving mirror.trouble-free.net... 66.45.230.130
Connecting to mirror.trouble-free.net|66.45.230.130|:80... connected.


15:35:31 (158 KB/s) - `mysql-connector-odbc-3.51.25-0.i386.rpm' saved [1862076/1862076]
 

Install MySQL, MySQL -Server, and UnixODBC

We will now install MySQL 5.0.22 (MySQL client programs and shared libraries.), MySQL -Server 5.0.22-2.2 (The MySQL server and related files.) and UnixODBC 2.2.11-7.1 (includes low-level drivers for MySQL, PostgreSQL, and local files.)

[root@tubes mysql-connector-odbc.from.mysql.com]# *yum install mysql mysql-server unixODBC*
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package mysql.i386 0:5.0.22-2.2.el5_1.1 set to be updated
---> Downloading header for mysql-server to pack into transaction set.
mysql-server-5.0.22-2.2.e 100% |=========================|  33 kB    00:00     
---> Package mysql-server.i386 0:5.0.22-2.2.el5_1.1 set to be updated
---> Downloading header for unixODBC to pack into transaction set.
unixODBC-2.2.11-7.1.i386. 100% |=========================|  28 kB    00:00     
---> Package unixODBC.i386 0:2.2.11-7.1 set to be updated
--> Running transaction check
--> Processing Dependency: perl-DBD-MySQL for package: mysql-server
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for perl-DBD-MySQL to pack into transaction set.
perl-DBD-MySQL-3.0007-1.f 100% |=========================| 8.3 kB    00:00     
---> Package perl-DBD-MySQL.i386 0:3.0007-1.fc6 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 mysql                   i386       5.0.22-2.2.el5_1.1  updates           3.0 M
 mysql-server            i386       5.0.22-2.2.el5_1.1  updates            10 M
 unixODBC                i386       2.2.11-7.1       base              832 k
Installing for dependencies:
 perl-DBD-MySQL          i386       3.0007-1.fc6     base              147 k

Transaction Summary
=============================================================================
Install      4 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 14 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): perl-DBD-MySQL-3.0 100% |=========================| 147 kB    00:01     
(2/3): mysql-server-5.0.2 100% |=========================|  10 MB    01:20     
(3/3): unixODBC-2.2.11-7. 100% |=========================| 832 kB    00:05     
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: mysql                        ######################### [1/4] 
  Installing: perl-DBD-MySQL               ######################### [2/4] 
  Installing: mysql-server                 ######################### [3/4] 
  Installing: unixODBC                     ######################### [4/4] 

Installed: mysql.i386 0:5.0.22-2.2.el5_1.1 mysql-server.i386 0:5.0.22-2.2.el5_1.1 unixODBC.i386 0:2.2.11-7.1
Dependency Installed: perl-DBD-MySQL.i386 0:3.0007-1.fc6
Complete!
[root@tubes mysql-connector-odbc.from.mysql.com]# 

Install mysql-connector-odbc version 3.51.22 or newer.

We need to install mysql-connector-odbc version 3.51.22 or newer. We already downloaded it in an earlier step.

[root@tubes mysql-connector-odbc.from.mysql.com]# *rpm -ivh mysql-connector-odbc-3.51.25-0.i386.rpm* 
error: Failed dependencies:
   libltdl.so.3 is needed by mysql-connector-odbc-3.51.25-0.i386

As you can see, my server is missing libltdl.so.3. That file is found in the libtool-ltdl package. Let's install it now.

[root@tubes mysql-connector-odbc.from.mysql.com]# *yum install libtool-ltdl*
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for libtool-ltdl to pack into transaction set.
libtool-ltdl-1.5.22-6.1.i 100% |=========================|  15 kB    00:00     
---> Package libtool-ltdl.i386 0:1.5.22-6.1 set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 libtool-ltdl            i386       1.5.22-6.1       base               37 k

Transaction Summary
=============================================================================
Install      1 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 37 k
Is this ok [y/N]: y
Downloading Packages:
(1/1): libtool-ltdl-1.5.2 100% |=========================|  37 kB    00:00     
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: libtool-ltdl                 ######################### [1/1] 

Installed: libtool-ltdl.i386 0:1.5.22-6.1
Complete!
[root@tubes mysql-connector-odbc.from.mysql.com]# 

Success! Now let's resume our installation of mysql-connector-odbc.

[root@tubes mysql-connector-odbc.from.mysql.com]# *rpm -ivh mysql-connector-odbc-3.51.25-0.i386.rpm* 
Preparing...                ########################################### [100%]
   1:mysql-connector-odbc   ########################################### [100%]
[myodbc3i.c][589][INFO] Driver registered. Usage count is 1. Location "/etc" 
[root@tubes mysql-connector-odbc.from.mysql.com]# 

Create MySQL database and database user.

If you don't already have a MySQL database created along with a MySQL database user, you need to create one. Our example will use a database named appx. The MySQL user name will be appx, which is a preexisting OS user. Substitute your own values for database name and database/OS user.

[root@tubes mysql-connector-odbc.from.mysql.com]# *mysql -uroot -p*
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3 to server version: 5.0.22

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> *create database appx;*
Query OK, 1 row affected (0.00 sec)

mysql> *grant all on appx.* to appx@localhost identified by "password";*
Query OK, 0 rows affected (0.00 sec)

mysql> *flush privileges;*
Query OK, 0 rows affected (0.00 sec)

mysql> *quit*
Bye
[root@tubes mysql-connector-odbc.from.mysql.com]# 

Determine where UnixODBC expects odbc.ini and odbcinst.ini configuration files to be located.

The odbc.ini and odbcinst.ini configuration files can be located on various places in your server's file system. The safest way to make sure you are working on the correct location is to run odbcinst -j. Here is an example:

[root@tubes tools]# *odbcinst -j*
unixODBC 2.2.11
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
USER DATA SOURCES..: /root/.odbc.ini
[root@tubes tools]# 

Here you can see that UnixODBC is expecting the two system configuration files to be located at /etc/odbc.ini and /etc/odbcinst.ini. Now that we know the location, let's configure the files. Both files can contain multiple sections or stanzas that are each identified by bracked values. Each bracked value is followed by property value definitions, one per line, in the format PROPERTY NAME=PROPERTY VALUE.

Configure /etc/odbc.ini

The odbc.ini file contains a list of Data Sources and any properties for each. There are two types of odbc.ini files; 1) System and 2) User. We will be working with the System DSN files only, and not the User DSN files. The System odbc.ini file usually exists at /etc/odbc.ini or /usr/local/etc/odbc.ini while the user usually exists at ~/.odbc.ini.

We need to build the odbc.ini file. The odbc.ini file can contain stanzas for different drivers. The content of each driver's stanza is driver specific (MySQL, PostgreSQL, FreeTDS, MiniSQL etc...). My /etc/odbc.ini file looks like this:

[root@tubes tools]# 
[root@tubes tools]# *cat /etc/odbc.ini*
[mysql]
Driver      = mysql
Database   = appx
Description   = mysql odbc connection for appx
Pwd      = password
Port      = 3306
Server      = localhost
UID      = appx
[root@tubes tools]# 

The [mysql] bracketed value is the Data Source Name. The Driver field is referenced in the APPX FMS settings, and in the odbcinst.ini file as a bracked value stanza header. The Database field is the name of the database that you want APPX to store data in. This database was created in an earlier step. The Description is informational only. The Pwd field contains the password for the MySQL user. Port is the port that MySQL is configured to listen on. The default is 3306. If it is something else, it would be listed in /etc/my.cnf. Server is the servername containing the MySQL instance we are connecting to. UID is the DSN's user account to connect to MySQL.

Configure /etc/odbcinst.ini

This ini file simply lists all installed drivers. It is usually located in either /etc/odbcinst.ini, or /usr/local/etc/odbcinst.ini.

We need to build the odbcinst.ini file. The odbc.ini file content is driver specific (MySQL, PostgreSQL, FreeTDS, MiniSQL etc...). My file looks like this:

[root@tubes tools]# *cat /etc/odbcinst.ini*
[PostgreSQL]
Description      = ODBC for PostgreSQL
Driver      = /usr/lib/libodbcpsql.so
Setup      = /usr/lib/libodbcpsqlS.so
FileUsage      = 0

[MySQL ODBC 3.51 Driver]
DRIVER      = /usr/lib/libmyodbc3.so
UsageCount      = 0

[mysql]
Description   = mysql odbc connection for appx
Driver      = /usr/lib/libmyodbc3.so
UsageCount   = 1
[root@tubes tools]# 

We are only interested in the [mysql] stanza. The [mysql] value matches the Driver and [mysql] bracked stanza DSN name values from the odbc.ini file. The Description field is informational only. The Driver field is the name of the driver file that was provided by the mysql.com mysql-connector-odbc-3.51.25-0 RPM. The Pwd field contains the password for the MySQL user. Port is the port that MySQL is configured to listen on. The default is 3306. If it is something else, it would be listed in /etc/my.cnf. Server is the servername containing the MySQL instance we are connecting to. UID is the DSN's user account to connect to MySQL.

The mysql-connector-odbc that we downloaded from mysql.com did not have a Setup library included, so we skipped that property. The Setup property points to a shared lib containing functions to be called by ODBC Config. By convention it usually has a capitol S towards the end of the file name such as libmyodbc3S.so. ODBC Config would call this library to get driver specific property names during data source configuration. If ODBC Config can not find or use this file it will assume some defaults.

Verify DSNs are working.

Now that the configuration files are in place, and the DSN is defined, let's test it out. We will use the isql command to make a connection to our DSN named mysql.

[root@tubes mysql-connector-odbc.from.mysql.com]# *isql -v mysql*
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> *show databases;*
+-----------------------------------------------------------------+
| Database                                                        |
+-----------------------------------------------------------------+
| information_schema                                              |
| appx                                                            |
| test                                                            |
+-----------------------------------------------------------------+
SQLRowCount returns 3
3 rows fetched
SQL> *quit*
[root@tubes mysql-connector-odbc.from.mysql.com]# 

Troubleshoot isql problems.

If isql complains that it can't make a connection to the MySQL socket in /tmp/mysql.sock, then the MySQL configuration file /etc/my.cnf might be set to create the file in /var/lib/mysql/mysql.sock. You should change the my.cnf file to point to /tmp/mysql.sock, or create a symbolic link.

 *isql -v mysql*
[08S01][unixODBC][MySQL][ODBC 3.51 Driver]Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
[ISQL]ERROR: Could not SQLConnect
[root@tubes mysql-connector-odbc.from.mysql.com]# *updatedb*
[root@tubes mysql-connector-odbc.from.mysql.com]# *locate mysql.sock*
/var/lib/mysql/mysql.sock
[root@tubes mysql-connector-odbc.from.mysql.com]# *ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock*

Set the APPX_ODBC_LIB environment variable

APPX needs to what and where the libodbc file is. libodbc is provided by unixODBC. On my system it is libodbc.so.1.0.0. For convenience, libodbc.so is a symbolic link to libodbc.so.1.0.0.

[root@tubes tools]# *updatedb*
[root@tubes tools]# *locate libodbc.so*
/usr/lib/libodbc.so
/usr/lib/libodbc.so.1
/usr/lib/libodbc.so.1.0.0
[root@tubes tools]# *ls -la /usr/lib/libodbc.so**
lrwxrwxrwx 1 root root     16 Jun 11 15:37 /usr/lib/libodbc.so -> libodbc.so.1.0.0
lrwxrwxrwx 1 root root     16 Jun 11 15:37 /usr/lib/libodbc.so.1 -> libodbc.so.1.0.0
-rwxr-xr-x 1 root root 447700 Jan  7  2007 /usr/lib/libodbc.so.1.0.0
[root@tubes tools]#

The APPX environment variable APPX_ODBC_LIB can be set an many places. Where it is set is not so important just as long as it is present at the begining of the appx session. A common convention is to set it either in the /usr/local/appx/data/appx.env file, or in the service daemon file /usr/local/appx/tools/appxd-8060.env. I'm going to place it in the daemon configuration file, after verifing that it is not set in the appx.env file.

[root@tubes tools]# *grep APPX_ODBC_LIB /usr/local/appx/data/appx.env*
[root@tubes tools]# 
[root@tubes tools]# *./appxLoginMgr -install -SockPort=8071 APPX_KEYMAP=WINDOWS APPX_ODBC_LIB=/usr/lib/libodbc.so APPX_SQL_CMD=/usr/local/appx/appx_sql_cmd.txt APPX_DBG_CODE=0xFFFFFFFF*
Warning - the engine that you named has the setuid bit enabled,
          you may not want that bit set for the authentication
          method that you have chosen (OS-User)
       To turn off the setuid bit, chmod u-s ../appx
Configuration written to:  appxd-8071.ini
Environment written to:    appxd-8071.env
Service script written to: /etc/init.d/appxd-8071
Configuration complete
Registering service
Starting appxd-8071: serviceName: appxd-8071
servicePath: /usr/local/appx/tools/
Looking for config file in appxd-8071.ini
Warning - the engine that you named has the setuid bit enabled,
          you may not want that bit set for the authentication
          method that you have chosen (OS-User)
       To turn off the setuid bit, chmod u-s ../appx
Writing process ID to /var/run/appxd-8071.pid
running as process 2652 servicing port 8071
Installation Complete

[root@tubes tools]# 

The service installation completed successfully. I added some optional debug only arguments to the service that create log files. These log files can be very helpful in debugging connection failures. Remove the debug arguments before turning the service over to production use. The arguments I used are APPX_SQL_CMD=/usr/local/appx/appx_sql_cmd.txt APPX_DBG_CODE=0xFFFFFFFF.

Configure APPX FMS parameters.

Well, MySQL is installed, configured to work with UnixODBC. Let's make the FMS settings in APPX to wrap up.

  • In APPX, Go to System Administration, then File Management, then FMS Groups.

oracle-fms-01.jpg

  • Create an FMS group with an appropriate name, and specify type 6 for ODBC.

mysql-fms-01.jpg

  • File in the ODBC DSN name for MySQL, followed by the Table Naming Scheme in the FMS Group Attributes of your new FMS group. The Table Naming Scheme could be picked from the suggestions shown when clicking on the Hints button. Also, add any three character value to the Proxy Lock field, I used LOK.

mysql-fms-02.jpg

  • Under Identities, define at least a default identity.

mysql-fms-03.jpg

  • Enter the MySQL account to use for the Default Identity, leave Realm empty.

mysql-fms-04.jpg

  • Enter the MySQL account's password.

mysql-fms-05.jpg

This completes the setup. To move any existing data to MySQL, use Data File Management to export the file(s), change the FMS type and name under File Specifications, then import the data.

Microsoft SQL Server (2000, 2005, 2008, SQL Server Express)

The setup steps for the Microsoft SQL Server family are the same as ODBC above, except you use the Windows ODBC Administrator tool to define the ODBC Data Source. The FMS group is set up the same way as above. Please note that if you are running a 64 bit OS, you need to use the 32 bit ODBC data source administrator. It can be found in C:\Windows\SysWow64\odbcad32.exe.

Database connectivity debug tools

APPX Environment Variables

If you are having problems connecting using the Oracle Instant client, make sure you have set the APPX_OCI_LIB to point to the Instant Client library, or APPX_OCI_DIR to point to the directory containing the Instant Client libraries. See Setting Environment Variables for more details.

You can also set the following environment variables to get a full log of the SQL commands & results:

  • APPX_SQL_CMD=<some path & flle name>
  • APPX_DBG_CODE=0xFFFFFFFF

Some OS tools to aid in debugging

If availble on your platform, you can use 'strace' to see the details of the files and libraries the engine opens (or tries to open). This can be helpful diagnosing connection problems.

Comments:

Read what other users have said about this page or add your own comments.


-- AlKalter - 04 Apr 2008
Topic attachments
I Attachment History Action Size Date Who Comment
JPEGjpg mysql-fms-01.jpg r1 manage 54.4 K 2008-06-12 - 18:40 JoeOrtagus Create FMS group name, and specify type 6 for ODBC.
JPEGjpg mysql-fms-02.jpg r1 manage 66.0 K 2008-06-12 - 18:51 JoeOrtagus Enter MySQL DSN name, Table naming scheme, and any three character value for Proxy Lock ID.
JPEGjpg mysql-fms-03.jpg r1 manage 62.4 K 2008-06-12 - 18:49 JoeOrtagus Specify a default identity for the FMS connection.
JPEGjpg mysql-fms-04.jpg r1 manage 61.9 K 2008-06-12 - 18:47 JoeOrtagus Enter the MySQL user ID here.
JPEGjpg mysql-fms-05.jpg r1 manage 66.2 K 2008-06-12 - 18:46 JoeOrtagus Enter the MySQL password here.
JPEGjpg oracle-fms-01.jpg r2 r1 manage 78.2 K 2008-06-05 - 21:10 JoeOrtagus APPX System Administration, File Management, FMS Groups.
JPEGjpg oracle-fms-02.jpg r1 manage 39.5 K 2008-06-05 - 21:13 JoeOrtagus Create FMS group name, and specify type of 5.
JPEGjpg oracle-fms-03.jpg r1 manage 62.0 K 2008-06-05 - 21:14 JoeOrtagus Oracle server name, port and SID followed by Table naming scheme.
JPEGjpg oracle-fms-04.jpg r1 manage 47.5 K 2008-06-05 - 21:16 JoeOrtagus Specify Identity or the Oracle account to login as.
JPEGjpg oracle-fms-05.jpg r1 manage 46.0 K 2008-06-05 - 21:16 JoeOrtagus Enter the Oracle user ID here.
JPEGjpg oracle-fms-06.jpg r1 manage 50.1 K 2008-06-05 - 21:17 JoeOrtagus Enter the Oracle password here.
Edit | Attach | Watch | Print version | History: r24 < r23 < r22 < r21 < r20 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r24 - 2018-02-15 - JeanNeron
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback