1 Planning an Enterprise Data Quality Installation

This chapter helps to prepare you for your Enterprise Data Quality (EDQ) installation. Various topics are covered that should be reviewed thoroughly to help ensure that you do not encounter any problems either during or after the product installation and domain configuration.

This chapter includes the following sections:

Overview of EDQ

EDQ provides a comprehensive data quality management environment that is used to understand, improve, protect and govern data quality. The software facilitates best practice primary data management, data integration, business intelligence, and data migration initiatives. It provides integrated data quality in customer relationship management (CRM) and other applications.

This documentation guides you through the selection, installation and configuration of the components that are needed to support EDQ.

Overview of the Installation and Configuration Tasks

This section (Table 1-1) provides an overview of the EDQ installation and configuration tasks that you will perform, in the order that they should be performed.

Table 1-1 EDQ Product Installation Procedure Tasks

Task Action to Perform

Understand and select the external software components that support EDQ.

See Choosing EDQ Components and Versions

Obtain an EDQ installation file from Oracle Software Delivery Cloud.

See Downloading EDQ

Install the JDK and your chosen application server and database components.

See Installing the Required External Software Components

Install the EDQ software.

See Installing Enterprise Data Quality

Configure EDQ

For instructions see, Configuring Enterprise Data Quality with Oracle WebLogic Server or Configuring Enterprise Data Quality with Apache Tomcat

Set system parameters.

See Setting Server Parameters to Support Enterprise Data Quality

Next Steps

For log in and basic use information, see Next Steps After Configuring Enterprise Data Quality

Choosing EDQ Components and Versions

The following sections show you the components that are required to support EDQ and the supported versions of those components and EDQ.

Choosing the Correct Combination of EDQ Required Components

EDQ is a Java Web Application that uses a Java Servlet Engine, a Java Web Start graphical user interface, and a data repository within a database. As such, it requires access to the following components:

  • a Java Development Kit (JDK)

  • a Java Application Server to supply web services. Oracle WebLogic Server and Apache Tomcat are supported.

  • a structured query language (SQL) relational database management system (RDBMS) to store configuration data, working data, and the results of work performed by the processes. Oracle Database is supported.

Instructions for installing these components are in Installing the Required External Software Components See Supported Platforms and Component Versions for supported versions of each of these components.

Supported Platforms and Component Versions

For the latest supported configurations (for example, JDK versions, Operating System versions, Web server versions, and database versions), see Oracle Fusion Middleware Supported System Configurations on Oracle Technology Network (OTN).

You may be required to upgrade your environments to the supported versions of these and other products.

Downloading EDQ

To download the EDQ installation and configuration files, obtain the generic package installer from the Oracle Technology Network website as follows:

  1. Enter the following URL into a web browser:

    http://www.oracle.com/technetwork/middleware/oedq/overview/index.html

  2. Click Sign-in/Register.

  3. Locate and select Oracle Enterprise Data Quality Media Pack that you want to download.

  4. Click the Download button.

  5. Browse to the directory where you want to save the file. Click Save to start the file download. A ZIP file is downloaded.

  6. Extract the ZIP file to a temporary directory.

Verifying Digital Signature and Integrity of Installation Archive Files

Oracle digitally signs the installation archive files with Oracle certificates to ensure the integrity of the packages before you deploy them in your environments.

Use the Java utility jarsigner to verify the integrity of your installation archive files. You can verify the integrity of the installation archive files before you extract the installation files.

Quick Verification

To quickly verify the installation archive files, use the jarsigner command with the -verify option:

  1. Go to the directory where you have downloaded the installation archive files.
  2. Run this command to check your installation archive file:

    jarsigner -verify installation_archive_file

    For example, to check the Oracle Fusion Middleware Infrastructure archive:

    jarsigner -verify fmw_14.1.2.0.0_infrastructure.jar
    jar verified.

Detailed Certificate Information

If you want detailed certificate information, then use the -verbose:summary and -certs along with the -verify option.

  1. Go to the directory where you have downloaded the installation archive files.
  2. Run this command to check your installation archive file:

    jarsigner -verify -verbose:summary -certs installation_archive_file

    For example, to check the Oracle Fusion Middleware Infrastructure image:

    jarsigner -verify -verbose:summary -certs fmw_14.1.2.0.0_infrastructure.jar

    The output is similar to the following:

    2237119 Fri Dec 6 07:02:30 UTC 2023 META-INF/MANIFEST.MF
    
          >>> Signer
          X.509, CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US
          [
          Signature algorithm: SHA256withRSA, 3072-bit key
          [certificate is valid from 12/19/24 12:00 AM to 12/19/25 11:59 PM]
          X.509, CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [certificate is valid from 4/29/24 12:00 AM to 4/28/36 11:59 PM]
          X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [trusted certificate]
          >>> TSA
          X.509, CN=DigiCert Timestamp 2024 - 2, O=DigiCert, C=US
          [
          Signature algorithm: SHA256withRSA, 4096-bit key
          [certificate is valid from 9/21/24 12:00 AM to 11/21/33 11:59 PM]
          X.509, CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
          [
          Signature algorithm: SHA256withRSA, 4096-bit key
          [certificate is valid from 3/23/24 12:00 AM to 3/22/37 11:59 PM]
          X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [certificate is valid from 8/1/24 12:00 AM to 11/9/31 11:59 PM]
    
           2237281 Fri Feb 17 07:02:32 UTC 2024 META-INF/ORACLE_C.SF (and 1 more)
    
          (Signature related entries)
    
                0 Fri Feb 17 05:41:24 UTC 2023 OPatch/ (and 1897 more)
    
          (Directory entries)
    
           2977 Tue Dec 20 08:02:16 UTC 2024 OPatch/README.txt (and 20199 more)
    
          [entry was signed on 2/17/24 7:02 AM]
          >>> Signer
          X.509, CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US
          [
          Signature algorithm: SHA256withRSA, 3072-bit key
          [certificate is valid from 8/19/24 12:00 AM to 8/19/25 11:59 PM]
          X.509, CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [certificate is valid from 4/29/24 12:00 AM to 4/28/36 11:59 PM]
          X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [trusted certificate]
          >>> TSA
          X.509, CN=DigiCert Timestamp 2024 - 2, O=DigiCert, C=US
          [
          Signature algorithm: SHA256withRSA, 4096-bit key
          [certificate is valid from 9/21/24 12:00 AM to 11/21/33 11:59 PM]
          X.509, CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
          [
          Signature algorithm: SHA256withRSA, 4096-bit key
          [certificate is valid from 3/23/24 12:00 AM to 3/22/37 11:59 PM]
          X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US
          [
          Signature algorithm: SHA384withRSA, 4096-bit key
          [certificate is valid from 8/1/24 12:00 AM to 11/9/31 11:59 PM]
    
    
      s = signature was verified
      m = entry is listed in manifest
      k = at least one certificate was found in keystore
      i = at least one certificate was found in identity scope
    
    - Signed by "CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US"
        Digest algorithm: SHA-256
        Signature algorithm: SHA256withRSA, 3072-bit key
      Timestamped by "CN=DigiCert Timestamp 2024 - 2, O=DigiCert, C=US" on Fri Feb 17 07:02:33 UTC 2024
        Timestamp digest algorithm: SHA-256
        Timestamp signature algorithm: SHA256withRSA, 4096-bit key
    
    jar verified.
    
    The signer certificate will expire on 2025-12-19.
    The timestamp will expire on 2031-11-09.