JasperReports Server Installation Guide<>

Deployment Considerations and Options

Introduction

JasperReports Server is a powerful Java based reporting engine which institutions can deploy on most Java based application servers including Apache Tomcat, Oracle WebLogic, IBM Websphere, Glassfish Server and Red Hat JBoss.

Jaspersoft provide extensive documentation on the installation of the server and this should be your first port of call for installation-related queries. Our recommendation is an installation based on Apache Tomcat and this document is based on a Tomcat deployment. This document will help you understand the type of deployment that best fits your institution and guide you through the Ellucian Quercus specific tasks of the deployment.

Ellucian have described a number of suggested architectures for deploying JasperReports Server.

These are provided as an aid to you when considering the installation and deployment of this server. However, there are other architectures that you might want to explore before making a final decision. Ellucian therefore recommends that you also consult the Jaspersoft installation guides, which are available on the Jaspersoft website, as part of the decision-making process.

Supported Versions of JasperReports Server

JasperReports Server v6.1.1 is supported from Ellucian Quercus 8.5.0.

Installation Types

JasperReports Server has two main distribution packages – an installer and a WAR file distribution (Table 1).

Table 1: JasperReports Server Distribution Packages

Distribution Package

Description

Installer

Runs on:

Windows (64-bit)

Linux (32-bit or 64-bit)

Mac OSX (64 bit)

WAR File Distribution

Used for manual installation on Windows, Linux, Mac and other platforms.

The installer package installs JasperReports Server, automatically configures the JasperReports Server database, and installs sample data for working with tutorials.

The WAR file binary distribution contains the JasperReports Server Web Archive (WAR) file and the scripts to create and load the database. It also supports additional applications not supported by the installers.

For more information on which platform versions are supported by each installation type, see the JasperReports Server Install GuideRelease 6.1 (available on the Jaspersoft community site http://community.jaspersoft.com/).

Installation Considerations

Before you install and deploy JasperReports Server, consider the following options for deployment, and then choose the installation that best matches your requirements:

Will you deploy JasperReports Server as part of the Ellucian Quercus installation or on a separate infrastructure?

Will JasperReports Server be publicly available to the end-users, or is it for use only within a LAN?

Is a bundled installation sufficient for development and test environments?

Is a bundled installation sufficient for a production environment?

Is high availability a requirement for reporting?

This installation matrix (Table 2) is provided to help you when considering these options.

Table 2: Installation Matrix

Distribution Package

Requirement

Installer

WAR File Distribution

Windows or Linux Installation

Y

Y

Production or Development Environment

Y

Y

Publicly Available

Y

Y

High Availability Required

N

Y

Installed with Ellucian Quercus

N

Y

Use existing infrastructure

N

Y

Bundled Installer Architecture

This diagram shows the bundled installer architecture.

The installer installs Apache Tomcat 7 and a PostgreSQL 9 database, which functions as a repository database. As part of the installation, the JasperReports Server is deployed as a Tomcat application. A connection to one or multiple data sources can be made once installed.

This architecture is simple and can be deployed quickly and easily. It is ideal if you want to:

have an all-in-one installation.

deploy the JasperReports server in a test or development environment.

deploy a stand-alone reporting environment which can be easily upgraded.

WAR File Distribution Architecture

This diagram shows the WAR file distribution architecture.

The WAR file distribution installation is more flexible than the bundled installer, as it allows you to define the component parts of the installation. The WAR file distribution must be installed into an existing Java-based application server such as Tomcat (Tomcat is used as an example in the diagrams).

A repository database must be available for the WAR file distribution installation, and this database can be Oracle, SQL Server, MySQL, DB2, or PostgreSQL.

The advantages of this architecture are:

it allows system administrators to define the installed components.

the repository database can be installed separately from the web server, thus allowing for independent backups.

it allows system administrators to reuse existing web servers with Java applications installed.

the deployment of the JasperReports Server is reasonably simple with the supplied installer scripts supplied by Jaspersoft.

WAR File Distribution with Ellucian Quercus Installation Architecture

This architecture is the same as the WAR file distribution architecture but with Ellucian Quercus installed on the same web server, as shown in the diagram below:

The two additional components of this architecture are:

An Apache httpd server, which provides a front-end for web requests to Ellucian Quercus and JasperReports server.

Oracle REST Data Services (ORDS), which is a Java application that provides the bridge between the application server and the Oracle database.

The advantages of this architecture are:

it provides the same advantages listed for the standard WAR file distribution architecture.

it reuses existing application server components already installed for Ellucian Quercus.

installation is relatively simple, with very little interruption to the existing Ellucian Quercus installation (updates to the httpd configuration files are required).

Bringing the architecture one step further to allow for high availability, it is possible to cluster the web server instance and introduce a load balancer that will service the HTTP requests and route them to an available web server.

Both web servers will read the same repository database for JasperReports Server and the same data source.

The advantages of this architecture are:

it allows for multi-tenancy, if this is a requirement

it is highly-available

it allows system administrators add more web servers to the cluster during peak times

the set-up is relatively simple (you can set-up one web service and then copy it to a second and consecutive servers).