...
Upoad New Database Driver
If the provider you are looking for is not listed in the Provider drop-down but dropdown and you have its library files, click Upload Driver Driver button (under the ellipsis Actions menu next to Help icon) to add respective driver files (if not added already). You need to then select ‘Others’ Select the Others option in Provider. In this case you will also have to specify Driver Class Name and Connection String.Figure 7: Add Driver dialog box
...
To add a driver you need to:, perform the following steps.
Click Upload Driver button to open the Upload Driver dialog box.
In Name entry box, specify the driver file name along with the path or simply browse the driver file.
Click Upload.
The file will be updated and success message will appear. Failure message will appear in case driver could not be uploaded.
Click Close button to close the dialog box.
| Panel |
|---|
...
| ||||||
Note You need to restart Report Engine for the added driver(s). |
Connect using Oracle client installed on Windows
...
Kyvos Reporting recommends Oracle JDBC THIN connections for smooth and compatible access to Oracle Databases of various versions – 8, 9, 10, 11g or 12c.
...
Kyvos Reporting also supports OCI_TNS (Oracle Call Interface Net Service Names) for those who want to use their Oracle client installations to connect to Oracle databases.
If Oracle client is not installed on report server machine, then
...
Kyvos Reporting chooses to use ojdbc14.jar, for THIN connections.
If the report server machine has Oracle client installed, then
...
Kyvos Reporting chooses to use classes12.zip, assuming that client is compatible with the server version being connected to.
...
Kyvos Reporting allows Administrator to decide which driver
...
Kyvos Reporting should use by following the below mentioned steps.
Steps to make changes in Report Engine loader batch file are as below:.
Open the file from path<install dir>/\ReportEngine/\bin/\run.bat
Add the highlighted line to the file:@echo offset JRE_HOME=….jreset ORACLE_DRIVER=..libojdbc14.jarset PATH=”.”;%JRE_HOME%bin;%JRE_HOME%lib;%JRE_HOME%binserver;%PATH%SET INTELLICA_CLASSPATH=FOR %%i in (“..lib*.jar”) DO CALL includelib %%i notIncludeIEngineFOR %%i in (“..lib*.ZIP”) DO CALL includelib %%i notIncludeIEngineiEngine –oracledriver%ORACLE_DRIVER%%INTELLICA_CLASSPATH% “../config/ReportEngine.properties” -Xms20M -Xmx128MIn the batch file, a variable is being set to the name & path of the oracle driver we wish Intellicus Kyvos Reporting to use.set ORACLE_DRIVER=..libojdbc14.jar
Change the iEngine calling line to pass the variable.iEngine -oracledriver%ORACLE_DRIVER%%INTELLICA_CLASSPATH% “../config/ReportEngine.properties” -Xms20M -Xmx128MThe above example forces Intellicus Kyvos Reporting to use ojdbc14.jar driver for Oracle connections.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note Kyvos Reporting can use only one type of Oracle driver, so cannot make connections to various server versions, if it needs different drivers. |
| Note |
|---|
Warning |
...
|
...
|