Embedded Reporting for ISVs: Webinar Q&A

Share on LinkedInTweet about this on TwitterShare on FacebookShare on Google+

Yesterday’s webinar highlighted many of the different benefits for ISVs to include an embedded reporting solution like JReport as part of their application. JReport’s 100% Java architecture gives users flexibility to run on any platform, connect to any data source, and customize to match the existing UI as much or as little as you need.

So if you weren’t able to attend, click here to access a copy of the recording or take a look below at some of the great questions we received during the presentation. And don’t forget to register for next month’s webinar Introducing JReport 11: Visualization, Dashboards, and Mobile Solution!

1) Can JReport be white-labeled for embedding into my application and is there anything that shows JReport to end users?
Most people use JReport and have no idea that there is a 3rd party product included in the application. Some of our customers like IBM, HP, and many others include JReport as part of their application but there is no visible JReport labeling or images that are shown to users. We can teach you how to private-label in our training courses.

2) Our application is all written in PHP will JReport work transparently in our application?
Yes. JReport is 100% Java and the UI is JSP based but the actual calling to request a report is via a URL in most cases. So the URL comes in, JReport responds to that request, and creates a report to send back to the browser or creates a report exported to a particular format such as PDF or Excel finally giving the request back to the calling program. It really doesn’t matter what the calling program is. It can be PHP, .NET, or any other language—any language that is a web based application that can send a URL request to JReport. JReport doesn’t even know what language the calling program is, it’s just responding to the URL request and executing that request and sending the report back to the calling program.

The only requirement for JReport is that there be a JDK installed on the server system where JReport is running.

3) Can the JReport user interface be customized as much as an open source product?
On the surface, it seems like having the source code would make it easier to customize the product but actually in the case of JReport it makes it more difficult. JReport provides the source code for JSP and JavaScript for the entire user interface that the user is going to see. Everything is very easily localizable because all of the UI elements are in Java Resource Bundles so it is very easy to modify those and to translate them into whatever languages that you need. It is also well documented on what you need to do and since you only have the source code for just what you need to localize and customize for your application its really much easier to do than with an open source product. With open source you’ll have to sift through many lines of code, that are a combination of user interface code and everything else to find out what you need to do and what you need to modify. It’s also not that well documented because they aren’t expecting you to make those types of changes. JReport is going to be much easier to customize than I think you’ll find in any open source product.

Share on LinkedInTweet about this on TwitterShare on FacebookShare on Google+

Leave a Reply

Your email address will not be published. Required fields are marked *

Test * Time limit is exhausted. Please reload CAPTCHA.