TIBCO Omni-Insurance™ Installer User's Guide > Omni-Gen Installer Components Configuration Overview and Prerequisites > Omni-Gen Installation Prerequisites

Omni-Gen Installation Prerequisites

Before the Omni-Gen Server (OGS) and the Omni Governance Console (OGC) are installed, ensure that the following prerequisites are configured on your environment:

  1. One or two empty database schemas must be built and ready for use.

    Note: The creation of the database is generally the responsibility of a database administrator.

    • A database administrator user name and password for the database or databases must also be available.

      Omni-Gen uses the following logical sets of tables to perform Master Data Management (MDM) and OGC functions:

      • Mastering (Database) Tables. This is automatically created in the same database, specified in the prompts for the Remediation Database of the Omni-Gen Installer.
      • Remediation Tables. This is automatically created in the same database, specified in the prompts for the Remediation Database of the Omni-Gen Installer.
      • Data Quality Repository Tables (commonly referred to as the "repo" database). This is created in the location specified in the prompts for the Data Quality (DQ) Database of the Omni-Gen Installer. When configuring the two (Remediation and DQ) database locations, you can configure two separate locations for Remediation and DQ, or you can configure one location for all the tables. The example in this document uses two different database names, one for Remediation tables and the other for DQ tables.

  2. Omni-Gen Master Data and Data Quality Editions require JDK version 8. The user is advised to consult with their JDK provider for the latest build and licensing.

    Note: Omni-Gen Master Data and Data Quality Editions have been certified with OpenJDK 8 build 232, as well as with Oracle JDK 8 build 231.

    1. Verify that the JAVA HOME environment variable is defined properly.
    2. Verify that %JAVA HOME%\bin is the first element in your PATH.
  3. Acquire the required DBMS specific JDBC .jar files for use by the OGC and ensure these files are available on the machine where the OGC will be installed.
    • Db2: db2jcc4.jar, db2jcc_license_cu.jar
    • Oracle: ojdbc8.jar
    • Postgres: postgresql-9.3-1102.jdbc4.jar
    • SQL Server (Microsoft): sqljdbc42.jar
    • SQL Server (Open Source): jtds-1.3.1.jar
  4. Ensure that the database server is configured to allow TCP connections and that the TCP ports are active.
  5. Ensure that you have the proper administrative rights to modify the Java CA certificate (cacerts) store and add files to the following directory:
    JAVA_HOME/jre/lib/security

    Modifying cacerts is required for interacting with the WSO2 Identity Server (WSO2 IS).