MyODBC Driver Installation and Configuration
Since MySQL has released a new family of ODBC drivers called MyODBC 5.x,
we recommend you to use that instead the version introduced on this page.
MyODBC 5.x gives better performance and enables you to use Unicode characters.
The following URL explains how to download and use MyODBC 5.x:
How to setup SMS feature with MyODBC 5
On this page you can find out how to install
and configure a MyODBC 3.51 driver for Ozeki NG - SMS Gateway to allow SMS
To configure database connectivity in Ozeki NG - SMS Gateway,
you need to set up an ODBC driver. To install and configure a MyODBC
driver (for a MySQL database), follow the instructions below.
The installation and configuration of other database drivers is
similar to the process described here.
Download the MyODBC database driver from the Internet.
You can use the following link:
Install the downloaded MyODBC database driver by starting the
downloaded exe file. The installation is similar to the installation of any
Windows application. Click the Next and the OK button to get
from one dialog box to the next and to finish the installation.
When the driver
is available on your system, you need to set up a datasource. Open Control
click Administrative Tools and click the Data Sources (ODBC)icon.
This will open the ODBC Data Source Administrator panel, which is part
of Windows (Figure 1).
Figure 1 - Opening the ODBC Data Source Administrator panel
In the ODBC Data Source Administrator panel, you have
to define a datasource. Click the User DSN Tab (it is the default tab),
and click Add as shown in the figure below. This will bring
up the "Create New Datasource" dialog box (Figure 2).
Figure 2 - Opening the Create New Datasource dialog box
In this form, select the (newly installed) driver, and click
Finish. In most cases, when you click Finish, a database server
specific configuration form comes up. (You can also open this configuration
form by double-clicking the selected driver.)
You can start start configuring the database driver
in the Login tab (Figure 3).
Figure 3 - The Login tab of the configuration form
Enter the information in the respective edit boxes.
In the Data Source Name box, enter the name of
the data source you want to access. It can be any valid name that you choose.
In the Description box, enter the description needed for the DSN.
In the Server box, enter the name of the MySQL server host that you
want to access.
By default, it is localhost.
In the User box, enter your MySQL username (your database user ID).
In the Password box, enter your password.
In the Database dropdown menu, select the database to be current
In the Connect Options tab, you can make three
specifications (Figure 4).
Figure 4 - The Connect Options tab of the configuration form
In the Port box, enter the port number if it is not
the default (3306).
In the Socket box, enter the name of the socket or the Windows
pipe to connect to.
In the Initial Statement box, you can enter an optional SQL statement
that you want to issue automatically after the connection has been established.
You can also test whether your settings are suitable for
connecting to the server using the Test button. This feature is available
only for the MyODBC 3.51 driver. A successful test results
in the window below (Figure 5).
Figure 5 - Successful test
A failed test results in an error (Figure 6).
Figure 6 - Failed Test
If the connection test succeeds, it means that you have a
working datasource which can be attached to Ozeki NG - SMS Gateway.
When configuring a MySQL database user in Ozeki NG - SMS Gateway,
you have to specify the database connection string in the Database
connection tab. Include the configuration specifications of your ODBC
driver in the connection string (Figure 7).
Figure 7 - Specifying the connection string for the MySQL database
For more information about the configuration of a MySQL user
for SMS messaging using Ozeki NG - SMS Gateway, check out the
MySQL User page.
You can find database connection strings for a wide range of
different databases In Appendix B -
People who read this also read...