Previous Page Next Page

Lesson 5: Administration of Resources

JReport Server provides the administration console that allows the system analyst, report administrator, or application server administrator to manage the resources, databases, configuration, security and so on of JReport Server. This lesson describes the administrative tasks that you can perform through the administration console.

Task 1: Access the administration console

Task 2: Review the Resources page

Task 3: Review the Configuration page

Task 4: Understand the Monitor page

Task 5: Review the remaining pages

Task 1: Access the administration console

1. Click System Admin in the JReport folder on the Start menu.
2. A browser window with the Sign in dialog is displayed. Enter admin for the user name and admin for the password, then click Login.

   These are the initial administrative user credentials built-in to JReport Server. One of the first things an administrator should do is to set up the correct user credentials so that appropriate access to the reports is granted.

   The JReport Administration page is displayed:

   

Task 2: Review the Resources page

The Resources page of the administration console lists the resources that have been published to JReport Server. The resource list shown here is similar to that of the user console, however the report name is not a link so you cannot run report from the administration console.

The User Directory is hidden on the left showing the folders of published resources. By default, the root folder is open when you first log onto the administration console.

The NLS Editor button allows you to translate a report or dashboard into a different language from the original one.

Other buttons, Versions , Properties and Delete , are the same as described in Lesson 1 of this track.

Task 3: Review the Configuration page

The Configuration page allows you to configure and manage JReport Server as follows:

• Service - Used to set attributes of the HTTP connection.
• Log - Used to configure the JReport logging system.
• Performance - Used to preload particular catalogs and reports in cache so they will be faster to access the first time they are used.
• LDAP - Used to configure LDAP as a security provider for JReport 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.
• Export - Used to configure the default settings for exporting report results to e-mail, to configure your FAX hardware and software settings. You cannot distribute reports via e-mail or fax until these settings are configured.
• Connection - Used to reload the connection settings after datasource.xml file is modified when JReport Server is running.
• Connection Pool - Used to keep cached connection for reuse.
• Upload - Used to specify the allowed image types when end users insert images from the local file system into reports or dashboards.
• Custom Fields - Used to manage user defined fields which can be used as resource properties in JReport Server.
• Dashboard Listeners - Used to manage implementations of the Dashboard Listener API.
• Dynamic Connections - Used to manage dynamic connections.
• Dynamic Display Names - Used to manage dynamic display names for business view elements.
• Organizations - Used to organize users into different groups.
• E-mail Server - Used to set up the linkage to your SMTP server to enable sending report results and notifications via e-mails.
• License Key - Used to update the server license with a new one.
• Advanced - A miscellaneous set of options and settings.

Task 4: Understand the Monitor page

JReport Server Monitor allows system administrators to log, monitor and report on real-time system status and the performance of the JReport Server. It can be accessed via any web browser, enabling administrators to remotely monitor and manage JReport Servers.

JReport Server Monitor allows you to track the status of JReport Server, see what reports are running or have run as well as which users are accessing the system.

JReport Server Monitor is downloaded separately from JReport Server, and must be installed before this page can be used.

Task 5: Review the remaining pages

• Security
  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 reports in the My Reports folder. For more details about security, see Lesson 6 in this track.
• Profile
  Allows you to customize general settings of JReport Server, Page Report Studio, Web Report Studio and JDashboard.
• Cluster
  Allows you to set up groups of servers in a clustered environment.
• Triggers
  Allows you to create and manage triggers.
• Data
  JReport Server needs to read and write to a DBMS system to store information about the server and the available reports and report version. By default the DBMS is the 100% Java Apache Derby DBMS embedded in JReport. This can easily be changed to use your preferred DBMS such as Oracle or MySQL.
• Cube
  Creates and manages in-memory cubes for business views.
• Cache
  Allows you to cache data, reports, security objects, and images. 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.

Previous Page Next Page