To allow the use of application drivers on connecting Foresight Analytics Platform started at a web server, to a database server using a server filter, the platform supports a number of external drivers loaded from the Drivers.xml file stored in the same directory with installed platform.
The Drivers.xml file has the following structure:
<PP>
<Drivers>
<Driver Id="HTTP (ORCL8)" Name="HTTP Orcl Driver" ModuleName="HttpOrcl8" ProgId="P9.Driver.HttpOrcl8" Versiondependent="TRUE"/>
</Drivers>
</PP>
where:
<PP>. Global chapter.
<Drivers>. Drivers collection.
<Driver>. Driver description:
Id. Driver identifier may contain DBMS identifier. For example, identifier for custom Oracle DBMS driver 9.x\10.x\11.x. may look as follows: HTTP (ORCL8).
Name. Driver name.
ModuleName. Name of DLL library.
ProgId. Identifier used to create a COM object.
Versiondependent. Release dependency, if TRUE, the version of Foresight Analytics Platform release is added to the specified ProgId when creating a COM object (For example: P7.Driver.HttpOrcl8.26).
The folder with installed Foresight Analytics Platform must contain the Drivers.xml file as well as DLL libraries defined in this file and their manifests. The Drivers.xml file is a primary file and redefines system drivers using corresponding identifiers (ORCL8, MSSQL2008 and others).
See also: