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:

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.

Troubleshoot isql problems.

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

[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]#

[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_SS_LOG=/usr/local/appx/appx_ss_log.txt APPX_SS_CODE=0xFFFFFFFF 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

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
up and running (process 2652 servicing port 8071)
Installation Complete

[root@tubes tools]# License server started as process 2657, logging to /usr/local/appx/tools/../data/license.log

[root@tubes tools]# 

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

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

• 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.

• Under Identities, define at least a default identity.

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

• Enter the MySQL account's password.