2 Installing the Required External Software Components
This chapter includes the following sections:
Note:
These components must be installed prior to installing EDQ.
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.
Use the following table to identify the appropriate JDK to install on the platform where you are installing EDQ.
Platform | JDK to Use |
---|---|
AIX |
IBM JDK. This is the only supported JDK on AIX. |
HP-UX |
HP JDK |
Solaris |
Oracle JDK |
Linux |
Oracle JDK |
Windows |
Oracle JDK |
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
Note:
On Solaris systems, you must install both the 32-bit and 64-bit JDKs in order to run Java applications.
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. For example, the JDK_HOME
may be like one of the following:
Linux and UNIX:
/opt/jdk1.8
Windows:
C:\Program Files\Java\jdk1.8
Note:
If your JDK_HOME
directory contains spaces, as in the default installation directory of C:\Program Files\Java\jdk1.8
, you must set your JAVA_HOME
environment variable to the Windows short name for the directory, as follows: C:\Progra~1\Java\jdk1.8
.
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 PostgreSQL Database, and you can install EDQ as a standalone application. PostgreSQL is not supported for production use.
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
After you install Tomcat, perform the following tasks:
-
Configure Tomcat to use the Java Development Kit (JDK) that you installed in Installing a Java Development Kit to Support EDQ You can do one of the following:
-
Set the path to the JDK executable in the
/etc/sysconfig/tomcat7.conf
file. For example:JAVA_HOME="/opt/java/jdk1.7.0_45"
-
Add the JDK path to the local
setenv.sh
file.
-
-
(Recommended) Configure Tomcat to start as a service.
-
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. For more information about the EDQ directories, see EDQ Directory Requirements
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
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
andPROCESSES
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.
Installing a PostgreSQL Database to Support EDQ
You can download the PostgreSQL product and installation instructions from the official PostgreSQL website at
Note:
If PostgreSQL was distributed with your operating system, verify that the release is one of EDQ supported releases by going to the certification matrix at
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Configuring PostgreSQL Database to Support EDQ
The following configuration elements are either required or recommended when installing or configuring a PostgreSQL database for use with EDQ.
Required:
-
Allow 403 maximum connections by editing the
postgresql.conf
file in the PostgreSQLdata
directory (for example,var/lib/pgsql/data/postgresql.conf
). -
Configure the PostgreSQL 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, click the Documentation link on the PostgreSQL website at
-
To use a PostgreSQL Database with EDQ, you must enable database listening. See Checking Local Database Connections
-
On Linux systems, you must configure PostgreSQL to use password authentication. See Enabling Password Authentication on Linux Systems
Recommended:
If you are installing on Windows, Oracle recommends that you use the graphical installer that you can download from the PostgreSQL website at
Each operating system on the Download page provides a link to the graphical installer.
Checking Local Database Connections
This section describes how to ensure that the PostgreSQL database local connections are properly configured to ensure database listening is on and that passwords are accepted for authentication.
Enabling Password Authentication on Linux Systems
On Linux systems, you must configure PostgreSQL to use password authentication by editing the pg_hba.conf
file in the data
subdirectory of the PostgreSQL installation directory (for example, /var/lib/pgsql/data/pg_hba.conf
). Locate the ident sameuser
entries, and then change them to a value of md5
.