In this section:
This section provides a brief overview of repository concepts related to the WebFOCUS Client and ReportCaster.
Repositories should be stored in a certified relational database management system (RDBMS), such as Derby, SQL Server, Oracle, MySQL, or DB2. ReportCaster communicates with an RDBMS using Java Database Connectivity (JDBC).
JDBC provides a way for Java programs to access databases and other data sources. Using JDBC, ReportCaster connects to your repository. It then creates and executes SQL statements to access and write repository information. In theory, JDBC provides a level of abstraction so that most SQL statements work on most databases. However, in practice, differences occur and you should ensure you choose a database and driver that are supported by WebFOCUS.
In order for the WebFOCUS Client to connect to a repository using JDBC, the following are required:
The credentials you provide to the database are critical, as they determine how you access the repository. Depending on the type of database, if you wish to maintain separate repositories for separate instances of WebFOCUS Client, you may need separate user IDs.
During the WebFOCUS Client installation, this is set in the WebFOCUS configuration file (webconfig.xml). If you need to change this, you can edit it using the WebFOCUS Administration Console , or dbuser and dbpass scripts.
The JDBC driver is a class name used to access the driver. This varies depending on the driver.
During the Distribution Server installation, this is determined and set.
This value is stored in the WebFOCUS configuration file (webconfig.xml). If you need to change this, you can edit it using the ReportCaster Server Configuration Interface or the repclass script.
A JDBC driver is usually packaged as one or more JAR or ZIP files. Each target data source has its own JDBC driver, so you would use the Oracle JDBC driver to access Oracle and the SQL Server JDBC driver to access SQL Server. Some vendors may also require different drivers for different database releases.
There are two types of JDBC drivers that connect in different ways. WebFOCUS normally uses a Type 4 or Type 2 driver. A Type 4 driver is entirely Java-based. A Type 2 driver includes files compiled for a specific platform (native files).
The JDBC driver must be installed on the machine or machines that run WebFOCUS Client and ReportCaster Distribution Server. For Type 4 drivers, you can normally just copy the driver into a directory on the WebFOCUS machines. For Type 2 drivers, you may need to install separate components.
The JDBC driver is used by both the Distribution Server and the application server. For ReportCaster to find the driver, the JDBC driver must be included in their CLASSPATH variables.
Note: You can also copy driver files into the WEB-INF/lib directory located inside the webfocus.war file or WebFOCUS81 directory before you deploy the web application.
You must always specify the driver file or files, not just the directory containing the driver. You enter the JDBC driver file name in the JDBC Path field.
During the Distribution Server installation, this is created and set.
This value is stored in the WebFOCUS configuration file (webconfig.xml). If you need to change this, you can edit it using the Repository section of the Administration Console.
Or you can edit the file using the repurl script and/or repclass script. For example,
repurl jdbc_urlrepclass class_name
The JDBC class is a value used to access the JDBC driver. The JDBC class value varies depending on the driver.
During the WebFOCUS Client installation, the JDBC class value is determined and set based on the database selection.
The JDBC class value is stored in the WebFOCUS configuration file (webconfig.xml). The WebFOCUS Administration Console or the repclass script can be used to edit the JDBC class value if you change your configuration to use a JDBC driver with a different JDBC class value.
The JDBC URL is a value used to access the driver and repository. This varies depending on the driver and other connection information.
During the WebFOCUS Client installation, the JDBC URL is set based on the selected database.
The JDBC URL value is stored in the WebFOCUS configuration file (webconfig.xml). The WebFOCUS Administration Console or the repclass script can be used to edit the JDBC URL if you change your configuration to use a JDBC driver with a different JDBC URL.