ReportWeaver provides direct data bindings to the (*database*) database system. The (*database*) release required for the bindings to work:

JPublisher provides reporting capabilities for filero through its bindings for the (*database*) database system. JPublisher for Filero contains some specific extensions and configurations for better Filero support. You can upgrade your version to any other product of the JPublisher/ReportWeaver product line, without loosing your Filero extensions.

Since Caché version 5.0. has some problems with generic access, ReportWeaver provides a specific cachedb.jar file. This file should only be used in conjunction with ReportWeaver. It does not interfere if you use a different version of Caché. If you are using Caché 5.0.13 or 5.1 or above please do not use the supplied jar file, but rather the cachedb.jar from your Caché installation.

When you install ReportWeaver with the (*database*) binding you will use the (*database*) connection wizard to connect to a (*database*) database via a schema definition file.

Note: ReportWeaver for (*database*) always uses the object model and its relationships to access data. It doesn't need or use the SQL based access.

In addition to the database ReportWeaver needs some additional information that it reads from the schema definition file. The schema information file is an xml file with configuration information. (The schema definition file) The usual extension is ".rsd".

The schema file allow you to define filters on the packages, so that irrelevant classes and packages are not shown.

The (*database*) Connection Wizard

The Connection wizard consists of three pages. One for the database, the schema definition file and one to extend the classpath.

jvi wizard- user schema page
  1. The name of the server where the database resides.
  2. The port to use for database access.
  3. The namespace, where your data resides.
  4. Database user for database login.
  5. Password for database login.
  6. If you are processing very large result sets, then you should use the light database interface. This turns off server side methods which significantly reduces the load on the server.
  7. For your first project, you can skip the schema extensions, and press finish directly.

Once the database is open the schema file and class path are stored in the repository. We recommend, that you save your repository after the database is open. You can then use this saved repository as a template for any work with this database.

If you want to change the schema file location or if your classpath must be modified, please use the command Open template set and reconfigure.

Note:Because there can only be one primary database attached during a session, the new/open action is disabled once you have a database open or after you have loaded a saved repository.