Bugzilla – Full Text Bug Listing
| Summary: | Tomcat Instance to Support BIRT | ||
|---|---|---|---|
| Product: | Community | Reporter: | Scott Rosenbaum <scottr> |
| Component: | EclipseCon | Assignee: | Karl Matthias <karl.matthias> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jasonweathersby, karl.matthias, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Scott Rosenbaum
My concern here is privacy. I'm ok with providing you a Tomcat instance, but I'm really hesitant about providing a publicly available Tomcat instance running BIRT with full access to our live databases. We could, I suppose, build a shadow database, but then you're talking about real work that, realistically, isn't going to happen. What if we have the BIRT instance hidden behind a web page that is serving up PDF files based on report type? We can control the reports that are published to the server, since I would be the only one committing reports to the server we know that the reports would only expose the data that we feel is appropriate. If you want to go with a more secure solution, Actuate has volunteered an instance of their iServerExpress product for the duration of the conference. Using their product we could lock down the read, write, and run options based to really control the content. An added benefit of the iServerExpress is that it would be easy to add reporting content into the PHP site through the JavaScript API. I am not trying to make this a plug for Actuate's commercial products, I just know that they have built much of the functionality that we would want to have. (In reply to comment #2) > We can control the reports that are published to the server, since I would be > the only one committing reports to the server we know that the reports would > only expose the data that we feel is appropriate. As long as you are the only one committing reports (or the program committee are the only people committing reports), then I'll be fine. But I don't want to open it to anyone in the community without a deeper consideration of the data privacy issues. That would work for me. If it makes sense we can use some form of promotion scheme that moves things in and out of CVS, I just don't know what infrastructure is in place to support this. I have included Jason Weathersby since he may have some thoughts on the best way to manage this as a secure BIRT Viewer instance. Hey Scott, I appreciate the offers of assistance. But with all of the balls we have in the air this EclipseCon season and the limited resources we have, we're just not going to be able to make this happen. If this kind of reporting continues to be a necessary part of planning for future EclipseCons, then we'll figure out a way to plan that into our time allocation. I'm sorry we just didn't do that this time around. It requires a lot of security work to implement this well in our infrastructure and that's really the time sink. I'm sorry if this causes you any inconvenience. The nightly database snapshots could be made twice daily if it would help you out. Just let me know. I heard no, but I need a little clarification of what is and is not possible in the four months between now and the conference. Are you saying that there is no way for us to have a BIRT Web Viewer running on Tomcat? Are you saying no we can't have the promotion? Are you saying there is no way for us to get anything? (In reply to comment #6) > I heard no, but I need a little clarification of what is and is not possible in > the four months between now and the conference. > > Are you saying that there is no way for us to have a BIRT Web Viewer running on > Tomcat? > > Are you saying no we can't have the promotion? > > Are you saying there is no way for us to get anything? Scott, as I read this there is one issue and I'm not clear where it breaks down into parts. We cannot setup a live reporting system using Tomcat for this conference. Not a hidden Tomcat or a public one. It's not clear to me why or how a CVS promotion to production system would be helpful without that. Scott, are Tomcat 5.0.28 and Java JDK 1.5.0.09 good enough to run this? Those are already installed and running the 2005 website on this server. That will work great. Scott Excellent, Scott, that really saves some time and resources. We did this a different way. Closing. |