et les remplacer :

Did you look in the system log, tomcat will sometimes put errors there…

I will try this soon and then update this post

I use this tutorial but change all database configurations to use postgres. Pentaho is running but when I try to login it gives an error in a dialog. When I check the logs (pentaho, catalina) there are no errors.

Any ideas what could be wrong?

My user is called pentaho, so that is correct. Also the other two connections are using the exact same user, password and host and they work just fine, only the SampleData connection doesn’t work. I have checked the credentials many times. I also tried logging into MySQL from the command line with the same settings, no problem there.

Since the SampleData datasource is the only one which is defined in the database instead of in a config file I am thinking: Could it be that the password is somehow encrypted before it is sent to MySQL?

Would your configuration work with tomcat 6?

Thanks

I don’t see any difference in your first change Strange that the data connections didn’t work for you… Did you set all hibernate configuration files?

I didn’t get the SEVERE errors, which tomcat version do you use?

I will look into the cache problem which I solved by configuring thetomcat startup file… I will post this later…

My First change:
————————————————————————–
2. Edit /opt/pentaho/pentaho-solutions/system/applicationContext-spring-security-jdbc.xml:

This one needs a class attribute to be set:

<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="com.mysql.jdbc.Driver" />
<property name="url" value="jdbc:mysql://localhost/hibernate" />

<property name="username" value="hibuser" />
<property name="password" value="password" />
</bean>

————————————————————————–

My Second Change:
————————————————————————–

Configuring Data Sources:

putting the conf under /usr/share/tomcat5.5/webapps/pentaho/META-INF/context.xml did not work for me. I put it inside /etc/tomcat5.5/server.xml <Host> tag.

My /etc/tomcat5.5/server.xml ’s Host configuration:

<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">

</Context>
</Host>

————————————————————————–

My Third Change:
————————————————————————–
In the pentaho/WEB-INF/web.xml need to add the following to avoid the
"WARNING: Security role name PENTAHO_ADMIN used in an <auth-constraint> without being defined in a <security-role>" error. While it says warning,
it will throw error next.

The following change should be done just before <security-constraint> tag.

<security-role>

<description>security role</description>
<role-name>PENTAHO_ADMIN</role-name>
</security-role>

————————————————————————–

My Fourth Change:
————————————————————————–
If you get an error in the tomcat logs like: "SEVERE: No Store configured, persistence disabled", you need to do the following in /etc/tomcat5.5/server.xml:

<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>

Change above line to:

<!--<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>-->
<Manager pathname=""/>

If you have copy & pasted, my second change, you would have this already.
————————————————————————–

My Fifth Change:
————————————————————————–
I got an error in the logs saying: "SEVERE: Error reading tld listeners java.lang.NullPointerException", all I had to do is, remove the commons-logging-1.1.jar from /usr/share/tomcat5.5/common/lib as it seems to be conflicting with that comes with pentaho. I guess you should have only one of it in there, so delete the one that you don’t need.
————————————————————————–

After all these changes, pentaho came up and I could see the application in 8080. But ehcache configuration is not right I guess, it keeps throwing

Error was libloader-data Cache: The Disk store is not active.
net.sf.ehcache.CacheException: libloader-data Cache: The Disk store is not active.

This ehcache error has filled up the log to the size of 33 megs in less than 10 requests in frontend!

Anyway, will dig deeper. Good Luck.

-ramki