Lesson 4: Administration of report sets
JReport Enterprise Server provides Administration pages that allow the system analyst, report administrator, or application server administrator to manage the report sets and operations of JReport Enterprise Server. This lesson describes the administrative tasks that you can perform through the Administrative pages.
These tasks include publishing report sets, deleting published report sets and report versions, and setting properties for report sets.
Task 1: Access the JReport Administration page
- Click Start > All Programs > JReport 9.0 > Server > JReport Server Administration, or open a web browser and set the URL to http://localhost:8889.
- In the Connect to localhost dialog, enter admin for the user name and admin for the password.
These are the initial administrative user credentials built in to JReport Enterprise Server. One of the first things an administrator should do is to set up the correct user credentials so that appropriate access to the report sets is granted.
The JReport Administration page is displayed:
Task 2: Review the Reports page
The Reports page of JReport Administration lists the report sets that have been published to JReport Enterprise Server.
The User Directory is hidden on the left showing the folders of published report sets. By default, the root folder is open when you first log onto JReport Administration page.
The report set list shown on the Reports tab of the Reports page is similar to that in the JReport Console; however, the report set name is not a link and there isn't an interface to run a report set.
The Versions button 
allows you to set the maximum number of versions of report set results to keep in the JReport Version library. When report sets are run, either in Advanced mode or scheduled, the report set results are stored in the Version library. The report administrator can control how many versions to maintain for each report set.
The NLS Editor button 
allows you to translate a report set into a different language from the original one.
The Cube Security button 
allows you to update a catalog's business cube permission settings without re-publishing the catalog.
Another two buttons, Properties 
and Delete 
, are the same as described in Lesson 1 of this trail.
Task 3: Review the Configuration page
The Configuration page allows you to control the operation of JReport Enterprise Server as follows:
- The Cluster tab allows you to configure clustering of multiple JReport Enterprise Servers.
A JReport Enterprise Server Cluster is a group of servers that work together to provide cluster-wide shared resource, security, schedule and version services. There is one admin server, one or more backup servers, and zero or one or more slave servers in a JReport Enterprise Server Cluster.
JReport Enterprise Server Cluster provides the following major features:
- Manageability: All users and resources can be controlled from a central place, remotely.
- High-Availability: When one server fails to perform, the tasks running on it will be reallocated to other servers. If one server has already been fully utilized, the tasks sent to it will be allocated to other servers.
- Scalability: You can add or remove servers dynamically according to your requirement.
- The Service tab is used for setting attributes of the HTTP connection.
- The Log tab gives you fine grained control of what information is logged.
- The Cache settings control report cache, security cache, and image cache. These settings affect how quickly resources can be accessed; however, the more resources that are cached, the more memory is used and thus would harm performance rather than increase performance.
- The Performance tab allows you to specify preloading particular catalogs and report sets in cache so they will be faster to access the first time they are used.
- The Advanced tab is a miscellaneous set of options and settings.
- The LDAP tab allows you to configure LDAP as a security provider for JReport Enterprise Server. A large number of different LDAP products are supported. In order to use them, a detailed knowledge of how to talk to your LDAP product is required.
- The Export tab allows you to set up the linkage to your SMTP server to enable sending report results and notifications via E-mail, to configure your FAX hardware and software settings, and to define the precision level with which the report result will be exported. You cannot distribute reports via e-mail or fax until these settings are configured.
- The Connection tab allows you to reload the connection settings after datasource.xml file is modified when JReport Enterprise Server is running.
- The Upload tab allows you to specify the allowed image size and types for the images which are uploaded from the local file system when end users insert images into reports in JReport Web.
Task 4: Understand the Monitor page
JReport Enterprise Server Monitor allows system administrators to log, monitor and report on real-time system status and the performance of the JReport Enterprise Server. Server Monitor can be accessed via any web browser, enabling administrators to remotely monitor and manage JReport Servers.
Server Monitor allows you to track the status of JReport Enterprise Server, see what report sets are running or have run as well as which users are accessing the system. JReport Enterprise Server Monitor is downloaded separately from JReport Enterprise Server, and must be installed before this page can be used.
Task 5: Review the remaining pages
- Security
The tab allows you to create and manage realms, users, groups, roles, privileges, and alias. This is required if you are going to use My Reports so that users will only see their own report sets in the My Reports folder. For more details about security, see Lesson 6 in this trail.
- Profile
This tab allows you to customize general settings as well as DHTML features in JReport. The DHTML tab is particularly useful to control the options that are displayed when users view DHTML reports.
- Cluster
Allows you to set up groups of servers in a clustered environment.
- Triggers
Allows you to create and manage triggers.
- Data
JReport Enterprise Server needs to read and write to a DBMS system to store information about the server and the available report sets and report set version. By default the DBMS is the 100% Java HSQLDB DBMS embedded in JReport. This can easily be changed to use your preferred DBMS such as Oracle or MySQL.
Exit JReport Administration pages by clicking the Logout link in the upper right corner of the page.
Lesson 4 summary
This lesson briefly introduced the JReport Administrative page.