Kbase P5613: Can the ODBC driver be installed without installing Client networking?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/07/2010 |
|
Status: Verified
GOAL:
Is there a standalone setup for the OpenEdge ODBC driver ?
GOAL:
Is there a standalone installation file for the OpenEdge ODBC driver ?
GOAL:
How to install ODBC driver without installing entire Client Network license
GOAL:
Can the ODBC driver that is packaged with Progress Client Products be installed without installing the Progress Client?
GOAL:
Can the ODBC driver be installed without installing Client Networking?
GOAL:
Can a install a ODBC driver in a machine that does not have any Progress product installed?
GOAL:
Is there a way to install only the ODBC driver without installing the Progress Client?
GOAL:
How to perform a custom install to remove the JDBC support
GOAL:
Is it possible to install JBDC or ODBC driver separated from regular installation?
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
Progress 9.x
FIX:
It is not possible to only install ONLY the ODBC driver via the Progress installation utility separately from the Progress Client Product. The ODBC driver that is packaged with Progress Client Products cannot establish a connection to the Database unless at least a Progress Client license exists. The ODBC driver is an Optional component so a Complete or Custom installation of the Progress Client product is required.
The Data Direct driver that is packaged with the Progress Client Networking and/or other Progress Client Products can not be installed separately from the Progress Client Product. To obtain the ODBC driver a complete installation of the Progress Client product is required.
The minimum Progress license that includes the ODBC driver is the Progress SQL Client Access Product. Please refer to Progress Solution P3842 to list of licenses that installs the ODBC drivers.
Although it is not possible to install ODBC standalone, some of the mandatory components (such as JDBC support) can be removed if not needed. This brings the install down to around 50MB.
** Please note, the following is under advisement and has not been fully verified. Any issues experienced would first have to be proven against a FULL Client Product installation. **
With the Client-Networking license:
- leave PROMSGS and Common Files checked, as without them it will not be a valid installation; registry entries are not added and the product will not uninstall.
- de-select Mandatory components to configure the installation as follows:
Remove Components:
Runtime Client
Client-Networking
ActiveX Control Support
Character Runtime Client DEV
Report Engine
Graphical Base Tools
- Add Component:
Progress SQL ODBC Clients
- Remove Components from Progress SQL ODBC Clients:
SQL Common
JRE
Progress Class Files
leave Common Files selected.
Starting from OpenEdge 10.1C, a minimal ODBC installation was introduced. The necessary files are located in : %DLC%\install\odbc
To install from the client, a mapped drive or UNC path to this folder needs to be created (ie on a machine with a full installation), then run %DLC%\install\odbc\sql-odbc-setup.exe from the Client's machine to install the OpenEdge SQL Drivers. Similarily, the ds-setup.exe can be run to install the DataServer Drivers on the client. In effect, this is a netsetup for ODBC clients.
All the files for the ODBC drivers will be on the centrally located file server.
If at any time the file server changes, the relevant setup executable above will need to be run from each machine to update the location of the ODBC driver files.
Existing DataSources will have outdated definitions of the location of the DLL file used by ODBC and will need to be recreated.
The setup program can not change existing datasource definitions.