|
- Overview
- Required configuration
- Necessary client layer
- Instant Client (recommended solution)
- Full Oracle client layer
- Notes common to the 2 client layers
- Compatibility
- Compatibility with the Oracle 8i client layers
- Compatibility with Oracle 7.3
- Compatibility with WDORAINS.EXE
- Use
- To use Native Oracle Connector in your WINDEV applications or WEBDEV sites:
- Optimizing HFSQL functions
- Managing the set of characters/the language/the territory
- Operating mode
- Caution
Native Oracle Connector for WINDEV and WEBDEV
 Available only with this kind of connection
WINDEV and WEBDEV 26 propose an optional Native Oracle Connector (also called Native Oracle Access). This Native Connector allows you to access an Oracle database from a WLanguage program without using any external driver. Benefits of using Native Oracle Connector: - The HReadxxx functions (HReadNext, HModify, ...) can be used on the Oracle databases. Therefore, an Oracle database and a HFSQL database are handled by the same commands. Porting an existing application to external databases is simplified.
- The RAD allows you to generate the code with the Hxxx functions (HReadNext, ...) or with the SQLxxx functions.
- Direct access to an Oracle database with no intermediate layer: MDAC, OLE DB and ODBC are useless.
- WDMap (data viewer) can be used on your Oracle databases.
- The setup is straightforward: No OLE DB or ODBC layer required on the user computer.
- All versions of Oracle databases are supported.
- etc.
The use of this Native Connector is highly recommended when developing Client/Server applications (that access the Oracle databases) with WINDEV. Feel free to contact us for any additional information. Remarks: - To purchase Native Oracle Connector, contact PC SOFT sales department.
 Versions 16 and laterThe Native Oracle Connector is available in 32 bits and in 64 bits.  New in version 16The Native Oracle Connector is available in 32 bits and in 64 bits. Versions 21 and laterThe Native Oracle Connector is available in Windows and Linux. New in version 21The Native Oracle Connector is available in Windows and Linux. The Native Oracle Connector is available in Windows and Linux.
Necessary client layer The Native Connector is compatible with the following Oracle client layers : Versions 17 and laterInstant Client (recommended solution). New in version 17Instant Client (recommended solution). Instant Client (recommended solution).- Full Oracle client layer.
Versions 17 and laterInstant Client (recommended solution) This client layer, available from Oracle 10g, requires no setup or no configuration. It is the lightest client layer. Versions 21 and later New in version 21 The "Data Source" parameter of the WINDEV or WEBDEV connection will have the following format :
"//host:[port][/service name]"
With: - host: Name of the computer that hosts the Oracle server.
- port: Number of the port chosen when installing the Oracle server.
- service name: Name of the service chosen when installing the Oracle server.
New in version 17Instant Client (recommended solution) This client layer, available from Oracle 10g, requires no setup or no configuration. It is the lightest client layer. Versions 21 and later New in version 21 The "Data Source" parameter of the WINDEV or WEBDEV connection will have the following format :
"//host:[port][/service name]"
With: - host: Name of the computer that hosts the Oracle server.
- port: Number of the port chosen when installing the Oracle server.
- service name: Name of the service chosen when installing the Oracle server.
Instant Client (recommended solution) This client layer, available from Oracle 10g, requires no setup or no configuration. It is the lightest client layer. Versions 21 and later New in version 21 The "Data Source" parameter of the WINDEV or WEBDEV connection will have the following format :
"//host:[port][/service name]"
With: - host: Name of the computer that hosts the Oracle server.
- port: Number of the port chosen when installing the Oracle server.
- service name: Name of the service chosen when installing the Oracle server.
Full Oracle client layer This client layer, available from Oracle 8i , requires a setup and a configuration. In most cases, the setup is followed by the definition of aliases with "Oracle Net Manager" that is used to specify the content of the "tnsnames.ora" file. The "Data Source" parameter of the WINDEV or WEBDEV connection will have the following format: With Alias corresponding to the name of the alias configured by "Oracle Net Manager". In this case, when opening the connection, the Oracle client layer searches for the parameters corresponding to this alias (server name, port number, service name) in the "tnsnames.ora" file. The following errors can be reported by the Oracle client layer when opening the connection if the alias is not configured properly: - ORA-12514: TNS: the listening process does not currently know the requested service in the connection descriptor
- ORA-12154: TNS: the specified connection identifier cannot be resolved
This type of error must be corrected in the configuration of aliases. The "tnsnames.ora" file is exclusively used by the Oracle client layer and not by the Native Connector. See the Oracle documentation for more details. Notes common to the 2 client layers Compatibility with the Oracle 8i client layers From version 17, the Native Connector connects by using the set of UTF16 characters when the client layer is recent enough, in order to eliminate any risk of inconsistency regarding the set of characters between the application and the client layer. However, the Oracle 8i client layer not offering this possibility, when the Native Connector detects that the client layer is in version 8i, the Native Connector specifies no set of characters (operating mode of versions 16 and earlier of Native Connector).
In this case, the Oracle client layer considers that the set of characters used is the set of characters selected when installing the client layer. The developer must check that the set of characters configured in the client layer on the computer of the end user is identical to the set of characters used in the WINDEV application or in the WEBDEV site.
A risk of data corruption exists if the sets of characters are not consistent. The execution of queries without Unicode correction is not available with an Oracle 8i client layer. Compatibility with Oracle 7.3 The Native Connector can be forced to operate in mode compatible with Oracle 7.3 is problems occur when connecting to an Oracle 7.3 server. In this case, the Native Connector is using the OCIW32.DLL DLL..
However, some operations will no longer be available because of the limitations of the Oracle 7.3 client layer. To force the Native Connector to operate in mode compatible with Oracle 7.3, the following string must be added into the optional information of WINDEV or WEBDEV connection:
Compatibility with WDORAINS.EXE A full compatibility is ensured with the configuration tool WDORAINS.EXE historically supplied with the Native Connector (in Windows only, in 32 bits). However, its use is not recommended for the new developments. To use Native Oracle Connector in your WINDEV applications or WEBDEV sites: To use ORACLE in native mode, you must program: Remarks: - Don't forget to read the limitations regarding the use of Native Oracle Connector.
- To deploy sites that use Native Oracle Connector, the Native Oracle Connector must be installed on the server (WEBDEV application server). This setup is performed from the DVD or setup package of the Native Oracle Connector.
Versions 24 and laterManaging thread errors: When a call to the Native Oracle Connector is made
from a thread, it is possible to manage errors in a normal way. New in version 24Managing thread errors: When a call to the Native Oracle Connector is made
from a thread, it is possible to manage errors in a normal way. Managing thread errors: When a call to the Native Oracle Connector is made
from a thread, it is possible to manage errors in a normal way.Versions 24 and laterThe Native Oracle Connector manages UUIDs. New in version 24The Native Oracle Connector manages UUIDs. The Native Oracle Connector manages UUIDs.
Optimizing HFSQL functions - The "Browsing table" controls based on queries are optimized: the content of the Table control can be sorted by clicking one of its columns.
- To avoid re-running the same query several times when browsing its result, we advise you to use the hNoRefresh constant (if the data is modified by a single computer for example).
Managing the set of characters/the language/the territory Operating mode The Native Connector fixes the NLS_LANGUAGE and NLS_TERRITORY properties to the values corresponding to the language and to the country used in the application when opening the connection. Oracle 8i client layers (and earlier)
Operating mode identical to the earlier versions : The Native Connector specifies no set of characters and the developer must check that the WINDEV or WEBDEV application is using the same set of characters as the one configured in the Oracle client layer. Oracle 9i client layers (and later)
The Native Oracle Connector connects to the database by using the set of UTF16 characters.
The ANSI data is exchanged (bind and define) in the set of ANSI characters used when opening the connection. Therefore, there is no risk of inconsistency regarding the set of characters between the configuration of the client layer and the WINDEV or WEBDEV application. You also have the ability to use the "Oracle Instant Client" client layer that requires no setup (simple copy of DLLs) and no configuration. Caution In any case, we recommend that you do not change the character set once the connection is opened otherwise inconsistencies may occur.
This page is also available for…
|
|
|
| |
| Click [Add] to post a comment |
|
| |
|
| |
| |
| |
| |
| |
| |
| | |
| |