Connection sharing for embedded JDBC and DatabaseController

Question

<p> </p><p>I would like to share an existing JDBC connection with the DatabaseController (i.e. same session in database).  Basically I need to call a stored proc in the JSP page then use the same (already established and open) connection for the DatabaseController to run the report.</p><p>Is that possible?  If so, can you give me a brief example.  I&#39;m well versed in Java, but not at all in CR.  I&#39;m trying to help evaluate the effort to merge existing web application code with CR reports.  The company has many existing CR files that I would like to "take to the web", but the underlying database uses session information and VPD for security.</p><p>For reference I&#39;m using an Oracle 10g database.  I would also welcome an answer that uses connection pooling and I could simply hand out pooled connections to the DatabaseController.</p><p>Thanks! <br /></p><p> </p><p> </p>

Answer 1

<p>Hi, </p><p>      Unfortunately there currently is no way to pass a JDBC connection to the report at runtime (this would be a great idea to track under the enhancement requests forum section). That being said there are other options you can do to get connection pooling functionality within your application. Probably the easiest way is to use JNDI. This will allow the application server to handle the Connection Pool. There is an optional property of the database connection of a report which allows the report designer to specify a JNDI lookup name. At runtime the report will look for this lookup name first prior to attempting to make the JDBC connection.</p><p>You can look at this comment on another question for instructions on how to set the JNDI optional name:</p><p><u><strong><a href="/node/483#comment-79">http://diamond.businessobjects.com/node/483#comment-79</a></strong></u>  </p><p>Another option is for you to pass in a java.sql.ResultSet at runtime to the report. It sounds like you are already making a JDBC connection at runtime so it shouldn&#39;t be too difficult for you to add the SQL query statement to populate a ResultSet. Once you have the ResultSet populated you can pass it into the report. In fact the wizard which is outlined on the comment listed above has a screenshot of the wizard which will generate the code at runtime to view a report. If you select the option in the wizard to "<strong>Populate the report with a java.sql.ResultSet"</strong> it will generate the necessary code stub to demonstrate how this will work.</p><p>The only downside to passing in the resultset at runtime is that it requires the entire dataset to be populated prior to passing it to the report. If the dataset is relatively small the performance impact will likely be acceptable, however if you start getting in to the tens of thousands of records then you may start seeing some performance implications. </p><p>Hope this helps. Let me know if you have any follow-up questions. </p><p>Regards,<br />Sean Johnson (CR4E Product Manager) </p>