Implementing the Java RSSE interface
BIRT iHub Integration Technology provides sample applications that demonstrate Java RSSE interface implementations. In the installation, each sample application is located in a separate subdirectory under the Java Report Server Security Extension directory.
Each sample application provides the following resources:
*The reference implementation of the RSSE interface.
Table 29‑1 lists the package for each sample application.
Table 29‑1 Sample application packages
RSSE application
Package
LDAP authentication
com.actuate11.rsse.authenticationSample
LDAP external registration
com.actuate11.rsse.ldapSample
Page Security
com.actuate11.rsse.aclSample
*The file, lib/rsse.jar, contains the RSSE interface and related classes.
The documentation for the package, com.actuate11.rsse.interfaces, is in the Java Report Server Security Extension/docs folder. To implement a class for the RSSE interface, refer to this API reference.
*The object renderer package, com.actuate11.rsse.or, contains a set of helper classes for logging RSSE objects to a file.
The package uses the open source logging tool, Apache log4j. Using the Apache log4j API, a developer can write log statements in the application code, then configure the logging level through a property file.
To configure the logging level for a Java RSSE application, modify the property, log4j.logger.com.actuate11.rsse, in the file, log.properties. The file, log.properties, is in the application package.
Apache log4j supports logging at the following levels:
*FATAL describes a severe error event that typically causes the application to abort.
*ERROR describes an error event that typically allows the application to continue running.
*WARN provides an alert to a potential problem.
*INFO provides a general message that describes the application’s progress.
*DEBUG provides information on an application event that is useful for debugging.
*ALL turns on all logging options.
*OFF turns off logging.
For more information about the Apache Logging Services Project and the log4j tool, see http://logging.apache.org/.