Another customer reported this issue in 3.2 and was a confirmed documentation defect. I did not see this added in the 3.4 IBM TRIRIGA Reporting Guide and thought this would be useful to someone who is encountering the same roadblock.
1. Copy JDBC JAR files
I copied over the two TRIRIGA jar files into the ecilipse plugin directory, you only need one depending on your database platform.
C:\Tririga\lib
-jtds-1.2.5.jar (SQLServer)
-ojdbc6.jar (Oracle)
<installdir>\eclipse\plugins
2. Click Manage Drivers... button
Depending on whether you connecting to Oracle or SQLServer.
Click manage Drivers... button.
Click add jar and add the two jars from above step 1.
You should then beable to select Driver class
Step 5,6,7,8 :-
Oracle
Driver Class: oracle.jdbc.OracleDriver (v11.2)
Database URL: jdbc:oracle:thin:@databaseserver:1521:orcl
User Name: tririga
Password: password
JNDI URL: jdbc/local/Datasource-TRIRIGA-data
SQLServer
Driver Class: net.sourceforge.jtds.jdbc.Driver (v1.2)
Database URL: jdbc:jtds:sqlserver://demobase/tridata
User Name: tririga
Password: password
JNDI URL: jdbc/local/Datasource-TRIRIGA-data
Step 9
Test Connection...
Then click finish and setup the dataset.
Taken from: http://www-01.ibm.com/support/docview.wss?uid=swg1IV15813
No comments:
Post a Comment