Supported Applications	Top

LabVantage supports Jaspersoft Jasper Reports and SAP Business Objects. See the LabVantage Installation Documentation for currently supported versions.

Jasper Reports	Top

LabVantage's Jasper Report integration provides the following reporting capabilities:

LabVantage provides default M18N support for all Reports. If additional support is required to be in locale/timesone/language compliance, LabVantage provides the sapphire.report.JasperReportScriplet class in the LabVantage Java Public API. Methods in this class can format dates/numbers, adjust for timezone offsets, and translate language.

If creating a Report using a client application, you must include sapphire.jar in the client CLASSPATH of the local machine.

Note that the Report will not be M18N-compliant until executed from within LabVantage.

To assist in creating Jasper Reports, LabVantage provides templates in the options\Jasper\templates folder of the LabVantage distribution:

These templates automatically define:

The GenerateReport Action can:

Business Objects	Top

See the LabVantage Installation Documentation to determine the Business Objects versions currently supported.

To work with BO reports, LabVantage provides:

LabVantage uses these BO Web Services:

LabVantage provides administrators with global (system-wide) and user (user-specific) profile properties to authenticate a user accessing BO:

Typically, the BO Administrator sets the BO Authentication Type on the BO Server. The LabVantage Administrator then sets the BO Username, BO Password and BO Authentication Type in the User Profile for each user, and the BO Authentication Type as a global property (Reporting Options in System Configuration).

LabVantage passes each user's properties to BO Web Services to authenticate and establish a connection. Following connection, the Web Service Login function also performs authentication. This lets you use row restriction, table mapping, and report filtering for all users accessing reports or the report list. A successful connection creates a session object.

After authenticating the user, the following steps are executed to locate and execute a report.

LabVantage recognizes a report only if you register it. Registering a report makes it a Report SDI. This means that Reports are covered by LabVantage security, and can be configured from within LabVantage. For example, you can specify how the argument is obtained from LabVantage and the user.

You can register a report only after it has been published to the BO Repository.

For details concerning the registration interface, see Reports and Execute Reports.

To find the reports in the Repository, LabVantage uses the BiPlatform service and ResponseHolder objects to get a report list from a root directory.

After saving the Report SDI, LabVantage determines prompts using the BO ReportEngine service. LabVantage then saves reports and their parameters (arguments) in the database.

Any registered report can be executed and viewed. For details, see Reports and Execute Reports.

LabVantage processes the ReportId, corresponding BO repository path location, and prompt values in the database. When executing a report, LabVantage accesses report information from the Registered Report SDI as follows:

The GenerateReport Action can:

The GenerateReport Action identifies the report. The ReportId and corresponding BO repository path location and prompt values for the registered report are then processed as follows:

A Connection Test is provided in the System Configuration User Options. These properties are replicated in the User Maintenance "User Profile" detail.

Controlled Reports	Top

"Controlled Reports" is a process that generates a unique event when certain operations are performed on the report. For more information, see Controlled Reports.