text
|
- Open the file
$OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi .
- Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
[OpenLink]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = localhost:5000
ServerType = Oracle 8.1.x
Database =
Options =
Username =
Password =
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample DSN
- Example MySQL Data Source:
[mysql5]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = MySQL 5.x
Database = test
Options = -H mysql_hostname -P 3306
Username = root
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample MySQL 5.x Connection
- Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
- Use the
iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
# cd OPENLINK_INSTALL
# . ./openlink.sh
# iodbctest mysql5
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0507.0105
Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
SQL>You should now be able to issue SQL statements directly against the target database.
- Additional Information
- The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.
- That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.
- Open the file
$OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi .
- Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
[OpenLink]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = localhost:5000
ServerType = Oracle 8.1.x
Database =
Options =
Username =
Password =
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample DSN
- Example MySQL Data Source:
[mysql5]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = MySQL 5.x
Database = test
Options = -H mysql_hostname -P 3306
Username = root
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample MySQL 5.x Connection
- Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
- Use the
iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
# cd OPENLINK_INSTALL
# . ./openlink.sh
# iodbctest mysql5
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0507.0105
Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
SQL>You should now be able to issue SQL statements directly against the target database.
- Additional Information
- The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.
- That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.
- Open the file
$OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi .
- Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation processâSample DSN as created by installer:
[OpenLink]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = localhost:5000
ServerType = Oracle 8.1.x
Database =
Options =
Username =
Password =
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample DSN
- Example MySQL Data Source:
[mysql5]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = MySQL 5.x
Database = test
Options = -H mysql_hostname -P 3306
Username = root
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample MySQL 5.x Connection
- Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
- Use the
iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
# cd OPENLINK_INSTALL
# . ./openlink.sh
# iodbctest mysql5
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0507.0105
Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
SQL>You should now be able to issue SQL statements directly against the target database.
- Additional Information
- The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.
- That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.
- Open the file
$OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi .
- Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation processâSample DSN as created by installer:
[OpenLink]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = localhost:5000
ServerType = Oracle 8.1.x
Database =
Options =
Username =
Password =
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample DSN
- Example MySQL Data Source:
[mysql5]
Driver = /OPENLINK_INSTALL/lib/oplodbc.so
Host = requestbroker_hostname:5000
ServerType = MySQL 5.x
Database = test
Options = -H mysql_hostname -P 3306
Username = root
Password = **********
FetchBufferSize = 99
ReadOnly = no
DeferLongFetch = no
JetFix = no
Description = Sample MySQL 5.x Connection
- Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
- Use the
iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
# cd OPENLINK_INSTALL
# . ./openlink.sh
# iodbctest mysql5
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0507.0105
Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
SQL>You should now be able to issue SQL statements directly against the target database.
- Additional Information
- The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.
- That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.
|