. . . "
    \n
  1. \n Prerequisites:\n
      \n
    • You MUST be proficient in using a Unix shell.
    • \n
    • You MUST be proficient in using a Unix editor such as vi.
    • \n
    • You MUST be in possession of relevant database connectivity details such as Database name, Username, password, etc.
    • \n
    \n
  2. \n
  3. \n Open the file <OPENLINK_INSTALL>/bin/odbc.ini with a suitable text editor such as vi.\n
  4. \n
  5. \n Locate and edit the sample OpenLink SQL Server ODBC data source (DSN) created during the installation process and edit as follows:\n
    \n      [sqlserver]\n      Driver            = <OPENLINK_INSTALL>/lib/sql_mt_lu.so\n      ServerType        = SQLServer 2000\n      Options           = -H sqlserver.hostname -P 1433\n      Database          = database\n      UserName          = sa\n      Password          = **********\n      FetchBufferSize   = 99\n      ReadOnly          = no\n      DeferLongFetch    = no\n      JetFix            = no\n      Description       =\n    
    \n
  6. \n
  7. \n Use the iodbctest tool which is packaged with the HTTP-based OpenLink ODBC Administrator as follows:\n
    \n      # cd <OPENLINK_INSTALL>\n      # . ./openLink.sh\n      # iodbctest sqlserver\n    
    \n
    \n iODBC Demonstration program
    \n This program shows an interactive SQL processor
    \n Driver Manager: 03.52.0507.0105
    \n Driver: 06.02.1217 OpenLink Generic ODBC Driver (sql_mt_lt.so)
    \n
    \n SQL>\n
    \n
  8. \n
  9. \n You should now be able to issue SQL statements directly against the target database.\n
  10. \n
\n

\n Additional Information:
\n The bitness of the ODBC Driver for MySQL is determined by the bitness of your ODBC client application.
\n That is, if your ODBC client application is 32-bit then the Generic ODBC Driver component MUST also be 32-bit.\n

" . . . . "Installation and Configuration of Single-Tier (Lite Edition) ODBC Driver for Microsoft SQL Server Linux or Unix" . . . . "Installation and Configuration of Single-Tier (Lite Edition) ODBC Driver for Microsoft SQL Server Linux or Unix" . . "Configuration of Single-Tier (Lite Edition) ODBC Driver for Microsoft SQL Server Linux or Unix" . . . . . "Configuration of Single-Tier (Lite Edition) ODBC Driver for Microsoft SQL Server Linux or Unix" . . "Data Source Name Configuration Guide" . . . . . . . . . . "
    \r\n
  1. \r\n Prerequisites:\r\n
      \r\n
    • You MUST be proficient in using a Unix shell.
    • \r\n
    • You MUST be proficient in using a Unix editor such as vi.
    • \r\n
    • You MUST be in possession of relevant database connectivity details such as Database name, Username, password, etc.
    • \r\n
    \r\n
  2. \r\n
  3. \r\n Open the file <OPENLINK_INSTALL>/bin/odbc.ini with a suitable text editor such as vi.\r\n
  4. \r\n
  5. \r\n Locate and edit the sample OpenLink SQL Server ODBC data source (DSN) created during the installation process and edit as follows:\r\n
    \r\n      [sqlserver]\r\n      Driver            = <OPENLINK_INSTALL>/lib/sql_mt_lu.so\r\n      ServerType        = SQLServer 2000\r\n      Options           = -H sqlserver.hostname -P 1433\r\n      Database          = database\r\n      UserName          = sa\r\n      Password          = **********\r\n      FetchBufferSize   = 99\r\n      ReadOnly          = no\r\n      DeferLongFetch    = no\r\n      JetFix            = no\r\n      Description       =\r\n    
    \r\n
  6. \r\n
  7. \r\n Use the iodbctest tool which is packaged with the HTTP-based OpenLink ODBC Administrator as follows:\r\n
    \r\n      # cd <OPENLINK_INSTALL>\r\n      # . ./openLink.sh\r\n      # iodbctest sqlserver\r\n    
    \r\n
    \r\n iODBC Demonstration program
    \r\n This program shows an interactive SQL processor
    \r\n Driver Manager: 03.52.0507.0105
    \r\n Driver: 06.02.1217 OpenLink Generic ODBC Driver (sql_mt_lt.so)
    \r\n
    \r\n SQL>\r\n
    \r\n
  8. \r\n
  9. \r\n You should now be able to issue SQL statements directly against the target database.\r\n
  10. \r\n
\r\n

\r\n Additional Information:
\r\n The bitness of the ODBC Driver for MySQL is determined by the bitness of your ODBC client application.
\r\n That is, if your ODBC client application is 32-bit then the Generic ODBC Driver component MUST also be 32-bit.\r\n

" . . . . .