Book Image

Pentaho 8 Reporting for Java Developers

By : Jasmine Kaur, Francesco Corti
Book Image

Pentaho 8 Reporting for Java Developers

By: Jasmine Kaur, Francesco Corti

Overview of this book

This hands-on tutorial, filled with exercises and examples, introduces the reader to a variety of concepts within Pentaho Reporting. With screenshots that show you how reports look at design time as well as how they should look when rendered as PDF, Excel, HTML, Text, Rich-Text-File, XML, and CSV, this book also contains complete example source code that you can copy and paste into your environment to get up-and-running quickly. Updated to cover the features of Pentaho 8, this book will teach you everything you need to know to build fast, efficient reports using Pentaho. If your interest lies in the technical details of creating reports and you want to see how to solve common reporting problems with a minimum of fuss, this is the book for you.
Table of Contents (25 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface

Prerequisites of your environment


As described in Chapter 1, Introduction to Pentaho Reporting, Pentaho Reporting is a suite of open source tools, including Report Designer, Reporting Engine, and Reporting SDK. All the preceding tools are written in pure Java, allowing any operating system that supports the Java runtime environment to run the application. The latest version of Pentaho Reporting, the 8th, requires the use of JDK 8 or more recent version.

Pentaho Reporting tools are cross-platform applications and will run in Linux, Windows, macOS, and other Java supported environments. The Reporting Engine is backward compatible with previous versions of JDK, but it is always recommended to use the latest one.

As stated in the introduction, in this chapter we are going to focus our attention on Pentaho Report Designer. The discussion on Pentaho Reporting SDK will be covered in the next chapter. About Reporting Engine, it is used as core component in the designer and the SDK, so it will be treated...