Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
BIRT 2.6 Data Analysis and Reporting

You're reading from   BIRT 2.6 Data Analysis and Reporting Create, Design, Format, and Deploy Reports with the world's most popular Eclipse-based Business Intelligence and Reporting Tool

Arrow left icon
Product type Paperback
Published in Jul 2010
Publisher Packt
ISBN-13 9781849511667
Length 360 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
John Ward John Ward
Author Profile Icon John Ward
John Ward
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

BIRT 2.6 Data Analysis and Reporting
Credits
About the Author
About the Reviewers
1. Preface
1. Getting Started 2. Installing BIRT FREE CHAPTER 3. The BIRT Environment and First Report 4. Visual Report Items 5. Working with Data 6. Report Parameters 7. Report Projects and Libraries 8. Charts, Hyperlinks, and Drilldowns 9. Scripting and Event Handling 10. Deployment

The BIRT perspective


We are ready to begin. We have defined a clear objective for our basic report, and now is the time to jump into the basic concepts of the BIRT Environment.

Once we start BIRT/Eclipse for the first time, we will be asked to select a location for our workspace.

A workspace is the location where projects get stored. This is very useful for Java developers who may want to reuse projects. However, for a report developer, a single workspace should suffice. In our case, we will set our workspace to C:\eclipse\birt_book_workspace.

If you're running the BIRT All-in-One package, you will start up in the default Eclipse screen and will need to change to the BIRT report perspective. Eclipse uses different "perspectives" as interfaces for different functionality and tools for particular tasks. For instance, if we are writing a Java program, we would use one of the Java perspectives available. This would allow us access to outlines, class views, and other relevant tabs. If we are debugging...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime