Forum Discussion
Using Oracle for storing roles and permissions
Using Oracle for storing roles and permissions
Hi - I am trying to use the Roles and permissions feature of the RMA (BA 7.1.1) by storing the users, roles and permissions in Oracle database instead of HSQL database.
Per the documentation, I made the following changes:
1. Generated DB Scripts and created the tables in Oracle database
2. Ran the seed data sql scripts to populate the tables with "admin" user and other basic information
3. Updated jdbc.properties to point to the oracle database
4. updated applicationContext.xml and specified the schema
5. Placed the ojdbc6.jar in the WEB-INF/lib folder
I have triple verified the database connection parameters and all parameters are correct. I even used the same properties file from a java program and ran a simple query it worked fine.
When I run the RMA and try to login using admin user, I get "Database connection could not be opened".
If I revert back to the HSQL settings in the jdbc.properties file, the RMA works fine.
There is no information in the tomcat log file which could tell me why database connection could not be opened. I am running the RMA through tomcat started from Eclipse IDE.
I have spent my entire day figuring this out, but of no use...any help will be appreciated.
Using Blaze Advisor 7.1.1
JVM: 1.6.0.33
Oracle 11g
Thanks
3 Replies
I don't think putting jars into WEB-INF/lib when starting RMA from Eclipse actually works. Try placing ojdbc6.jar into Advisor's lib folder (c:\Blaze\Advisor71\lib) or start the RMA using startserver.bat (and in that case I would also put a reference to that jar in the global Tomcat classpath).
Thanks Andrei - If I do not put eh ojdbc6.jar in the RMA WEB-INF/lib folder, I get class not found errors...Anyway, I tried putting the jar file in Blaze Advisor lib folder and still got the same "Database connection could not be opened".
But, launching the tomcat using the startserver.bat solved the problem.
Thanks
Baljeet
Eclipse is a weird beast when it comes to resolving class dependencies... At least in case of Blaze and other Eclipse-based FICO products I worked with (e.g. Model Builder).
