Preparing for Installation › Prerequisites › Database Prerequisites › Embedded Database

Embedded Database

If you choose the embedded database option with application level internal configuration, CA OM Web Viewer creates and initializes an embedded database (Apache Derby embedded database) with the proper settings. CA OM Web Viewer stores administrative data in this embedded database.

Note: The embedded database with application level internal configuration is created under a directory according to the type of application server where CA OM Web Viewer is deployed. For example:

• Tomcat: apache-tomcat/webapps/CAOMWebViewer12/database
• WebSphere: WebSphere/AppServer/derby/database

Important! With application level internal configuration on Apache Tomcat, an embedded database is a component that belongs to the installed CA OM Web Viewer application, undeploying or uninstalling, CA OM Web Viewer also removes the embedded database if the embedded database is created under the application’s working folder.

This situation is applicable with application level internal configuration on some application servers such as Apache Tomcat. To keep the content of an existing embedded database, you must manually back up and copy the database directory.

If you choose the embedded database option with external system level configuration or application level external configuration, CA OM Web Viewer creates and initializes an embedded database under the install directory, external system level configuration parent location pointed to by the CAOMWV12_HOME variable, or the application level configuration context folder. For example:

External System Level: <CAOMWV12_HOME>\database
Application Level External Configuration: <CAOMWV12_HOME>\<Application Context>\database

External Database

We recommend that you use an external database to keep administrative data from being affected by undeploying/uninstalling or redeploying/re-installing CA OM Web Viewer.

• If you choose an external database server, the system administrator sets up the database.
  • On the database server, you must create a specific database for CA OM Web Viewer.
  • If you used a Microsoft SQL Server database with CA OM Web Viewer 11.5 or a prior release, you must create a new database to be compatible with CA OM Web Viewer 12.0 or later releases.
  • This database must be writable with a valid user account that has permission to access it.
  • The external database server must provide a JDBC-3 or JDBC-4 compliant interface.
  • For DB2 Version 9, you must set up and run your DB2 server in new function mode (NFM). Version 10 or later does not require NFM.
  • If you are using DB2 on z/OS, you must provide a license jar file for the JDBC connection.

    The JDBC connection to DB2 on z/OS uses a JDBC driver, which requires a license file to connect to the DB2 endpoint. The license file is available only if you already have a license for DB2 Connect.

    The db2jcc_license_cisuz.jar file is included in all DB2 Connect server editions including DB2 Connect Personal Edition. The license is also part of the IBM Database Enterprise Developer Edition. If you already have one of these products, then use the license file from the DB2 Connect Activation CD. If you have a Passport Advantage account, then remember to download the activation key from Passport Advantage for the DB2 Connect edition that you have purchased. If you have not purchased the DB2 Connect edition contact IBM to purchase the product.

    You can find and download db2jcc_license_cisuz.jar in the following location on the DB2 Connect activation CD or in the FMID JDBAA12 for a Release 10.x DB2 SMP/E install on z/OS.

    /db2/license
    

The tables of the database can be created manually or automatically, depending on whether the account is granted with CREATE TABLE privileges:

• If this account has the CREATE TABLE privileges, this database can be empty and CA OM Web Viewer automatically creates the necessary tables.
• If this account does not have the CREATE TABLE privileges, ask your database administrator (DBA) to create tables. The tables must be created according to the Data Description Language (DDL) statements that are provided with CA OM Web Viewer.

Note: These DDL statements can be found under the ddl folder in your installation media or the installed directory. For each supported database type, a pair of SQL scripts is provided as follows:

• create.sql - For creating tables in the precreated database
• drop.sql - For deleting tables from the precreated database

See the specific instructions in either the GUI or Console mode of installation.

Note: Currently we provide DDLs for the following types of database: DB2, Derby, Oracle, and Microsoft SQL Server. For the DB2 mainframe, a template is provided so that the DBA can employ a schema which is not the default. If this is chosen, then you must add the current Schema property with a value followed by a semicolon in the JDBC URL.

Example:

jdbc:db2://<server>:<port-number>/<databaseName>:currentSchema=<schemaName>;