Hi,
At the moment I have two identical Pentaho instances to provide identical reports. The only difference is the connection source. I have labeled my JNDI connection CONN on both instances and configured it differently on each instance respective PAC. Unfortunately this implementation can't scale really well since one customer will mean one pentaho instance.
The idea here would be to have a single pentaho instance and somehow pass the JNDI/JDBC informations as parameters, this - for my needs - would scale much better.
Based on Taqua's last comment on this ticket - PRD-2854 - passing JNDI as a parameter is not an option. However it is said :
Given that JNDI customization can be done via scripting now
I have been looking at the three examples on PRD-3657, they all seem to only deal with the datasource via the computeQuery function (ie. the query) but not the connection itself.
My question is : is there anyway to dynamically select a specific connection on runtime, be it via a script (Global Scripting?) or via any other way ?
I am using Pentaho 4.8 and Pentaho Reporting 3.9.1.
Thank you,
At the moment I have two identical Pentaho instances to provide identical reports. The only difference is the connection source. I have labeled my JNDI connection CONN on both instances and configured it differently on each instance respective PAC. Unfortunately this implementation can't scale really well since one customer will mean one pentaho instance.
The idea here would be to have a single pentaho instance and somehow pass the JNDI/JDBC informations as parameters, this - for my needs - would scale much better.
Based on Taqua's last comment on this ticket - PRD-2854 - passing JNDI as a parameter is not an option. However it is said :
Quote:
Given that JNDI customization can be done via scripting now
My question is : is there anyway to dynamically select a specific connection on runtime, be it via a script (Global Scripting?) or via any other way ?
I am using Pentaho 4.8 and Pentaho Reporting 3.9.1.
Thank you,