2 Installing the Required External Software Components

This chapter describes how to install the software components that support EDQ.

Note:

These software components must be installed prior to installing EDQ.

This chapter includes the following sections:

Prerequisites for these Procedures

Before performing the procedures in this section, you must first read and satisfy the requirements in Planning an Enterprise Data Quality Installation

Installing a Java Development Kit to Support EDQ

EDQ and the application server both rely on the Java Development Kit (JDK). The JDK provides a Java run-time environment (JRE) and tools for compiling and debugging Java applications.

For supported JDK versions per platform, see the Enterprise Data Quality Certification Matrix at

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Download and install the appropriate JDK using the instructions provided at

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Make a note of the directory into which you installed the JDK. You will need to specify this directory during the installation of the application server. The path to this directory is referred to as the JDK_HOME directory in this documentation.

Installing an Application Server to Support EDQ

For maximum security, you should configure the application server (whether Oracle WebLogic Server or Apache Tomcat) to use HTTPS only. You should disable unencrypted HTTP access. You can alternatively use a frontend such as Oracle HTTP Server or Apache HTTP Server, where HTTPS is provided.

Choose and download one of the following application servers:

Note:

The application server that you choose determines the database that you can use. With Oracle WebLogic Server, you must use Oracle Database, and you must install EDQ within an Oracle Fusion Middleware environment. With Apache Tomcat, you can use either Oracle Database or Derby Database, and you can install EDQ as a standalone application.

Installing Oracle Fusion Middleware Infrastructure (includes Oracle WebLogic Server)

When installing on Oracle WebLogic Server, install both Oracle WebLogic Server and JRF. To view the WebLogic Server versions that are supported by EDQ in this release, see Enterprise Data Quality Certification Matrix at

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

To download and install Oracle WebLogic Server and JRF, see Installing and Configuring Oracle WebLogic Server and Coherence.

Note:

Use the Fusion Middleware Infrastructure installer. Do not use the free WebLogic Server distribution for developers, because this installer does not contain all of the required files for EDQ.

The directory path to your WebLogic Server installation is referenced as the WLS_HOME directory in this documentation.

Installing Apache Tomcat

To view the Tomcat versions that are supported by EDQ in this release, see the Enterprise Data Quality Certification Matrix at

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

To download and install Apache Tomcat, go to the Apache Software Foundation Server website at

http://tomcat.apache.org

After you install Tomcat, perform the following tasks:

  1. To configure Tomcat to use the Java Development Kit (JDK) that you installed in Installing a Java Development Kit to Support EDQ, add the JDK path to the local setenv.sh file.

  2. (Recommended) Configure Tomcat to start as a service.

  3. Create an operating system user who will run Tomcat. This user must own the EDQ installation and configuration directories. This account is used to administer your EDQ domain and to log into the EDQ application.

Installing a Database to Support EDQ

This section contains information that is specific to the installation and configuration of the database that will contain the EDQ repository.

  • If using Oracle WebLogic Server as the EDQ application server, you must install Oracle Database.

  • If using Apache Tomcat as the application server, the supported database for production is Oracle Database. PostgreSQL database is supported only for development or test purposes.

To view the supported database versions, see

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Note:

You will create three schemas and three users in this database when configuring EDQ in Configuring Enterprise Data Quality with Oracle WebLogic Server or Configuring Enterprise Data Quality with Apache Tomcat (depending on the application server you chose).

Installing an Oracle Database to Support EDQ

You can download a supported Oracle Database product and installation instructions from the Oracle Database website at

http://www.oracle.com

Configuring Oracle Database to Support EDQ

The following configuration elements are either required or recommended when installing or configuring an Oracle database for use with EDQ.

Required:

  • Select the Create and configure a database installation option.

  • Configure the database to use a Unicode character set to ensure that EDQ is able to capture and process data in the widest range of character sets. For more information, see Supporting Multilingual Databases with Unicode in Oracle Database Globalization Support Guide.

  • EDQ requires a database administrator (DBA) user account in the database. This database account is used to access the database during the installation and configuration processes to create database accounts and objects that are specific to EDQ.

Recommended:

  • Oracle recommends making the following configuration selections when specifying the Oracle memory structure and tablespace configuration to support EDQ:

    • 4GB Program Global Area (PGA)

    • 4GB System Global Area (SGA)

    • 20GB undo tablespace

    • 20GB temp tablespace

    • 120GB tablespace (4 x 30GB files) for Results database (EDQRESULTS schema)

    • 30GB (1 x 30GB file) for Config database (EDQCONFIG schema)

  • You may need to increase the values for the SESSIONS and PROCESSES parameters. The suggested values are as follows, but these parameters may need to be adjusted later for optimal performance:

    SESSIONS=500

    PROCESSES=500

    For more information about setting these values appropriately, contact your database administrator.