In this post we will show the necessary steps to connect ReportServer to an Active Directory using LDAP. As there are many valid ways to organize a company’s directory (may it be AD or another vendors product) ReportServer does not come with a predefined LDAP connector. This on one hand means, that the configuration might seem rather complex, but on the other hand it provides you with a maximum of flexibility.
We are happy to announce the release of ReportServer version 2.1 RC1. It is available for download from sourceforge. Version 2.1 is foremost a maintenance release, but it comes with a couple of exciting new features such as experimental support for SAP Crystal Reports and improved support for use with mobile devices.
Besides many detail improvements and some bugfixes we upgraded all the external report libraries to their latest versions. We also added experimental support for SAP Crystal Reports which can now be used to generate graphical reports alongside Jasper and Birt. Currently we support only basic functionality, thus we are happy to hear what you think should be added in upcoming versions. Besides that we made an effort to improve usability for users of mobile devices.
With version 2.1 we have also refactored large parts of the configuration. Most of the configuration is now accessible from the internal filesystem, which makes maintenance and future updates way easier. Detailed instructions on all the available options are given in the Configuration Guide, which will be available later this week.
If you need any help in upgrading from ReportServer 2.0 or have any comments and suggestions, we are happy to hear from you in our forum.
Your ReportServer Team
In our last post we have outlined the general process on how to add support for additional databases to ReportServer. Today we will give another example by explaining the necessary steps on how to access a Vertica database with ReportServer.
By default ReportServer is shipped with support only for the most common database systems, although it can interact with virtually every database, that offers a JDBC compliant driver. In this post we will show how to develop a groovy script that adds support for the firebird database (www.firebirdsql.org) to ReportServer.
In this post we have a look at how ReportServer exposes reports via the URL and how this can be used to implement drilling.
In this post we set the basis for many of the upcoming tutorials. We will show you how to load the democontent into ReportServer’s internal database so that we can later base our reporting tutorial on some data. We assume that you have ReportServer up and running which should be the case after following the quick install guide.
After more than a year of intensive development we have completed ReportServer 2.0 and made it available for download on Sourceforge.
With a completely redesigned interface, many new features and more than 100 detail improvements, Report Server 2.0 further improves the ease and efficiency of your everyday reporting.