5 Configuring Enterprise Data Quality with Apache Tomcat
Note:
These instructions apply to Apache Tomcat environments only. If you are using Oracle WebLogic Server, you must follow the directions in Configuring Enterprise Data Quality with Oracle WebLogic Server
This chapter includes the following sections:
- Prerequisites for these Procedures
- Creating the EDQ Database Objects
- Configuring Tomcat Application Server
- Creating Directories for Use With Tomcat Application Server
- Configuring EDQ to work with Tomcat Application Server
- Verifying EDQ Functional Packs
- Deploying the EDQ Application on a Tomcat Application Server
Prerequisites for these Procedures
Before performing the procedures in this section, you must first read and satisfy the steps in:
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Creating the EDQ Database Objects
EDQ requires three database accounts and three schemas. The first schema contains configuration data, the second contains results data, and the third contains staging data. These objects must be created in the database that you installed as the EDQ repository in Installing the Required External Software Components
- Creating an EDQ Repository in an Oracle Database
- Creating an EDQ Repository in an Apache Derby Database
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Creating an EDQ Repository in an Oracle Database
This procedure configures an Oracle database as the repository for EDQ.
Parent topic: Creating the EDQ Database Objects
Creating an EDQ Repository in an Apache Derby Database
EDQ 12.2.1.4.3 and later on Apache Tomcat support the use of an embedded Apache Derby database for the configuration and results schemas.
This procedure configures an Apache Derby embedded database as the repository for EDQ.
-
Use the migration.jar tool that is shipped with EDQ to create and initialize an Apache Derby database. Run the tool using the following command:
java -jar migration.jar init 'derby:(/path_to_db;create=true)'
The value you enter in path_to_db should refer to a non-existent directory. This is the location where the database files will be created. After the files are created you can copy them for use with EDQ.
- Edit
director.properties
file and use these properties to configure EDQ to use the Derby database:dataSource.driverClassName = org.apache.derby.jdbc.EmbeddedDriver dataSource.url = jdbc:derby:/path_to_db dataSource.username = APP dataSource.password = app resultsDataSource.driverClassName = org.apache.derby.jdbc.EmbeddedDriver resultsDataSource.url = jdbc:derby:/path_to_db resultsDataSource.username = APP resultsDataSource.password = app
Here, path_to_db is the absolute location of the directory containing the database files that you created in Step 1.
If you are using EDQ 12.2.1.4.3, you need to add the following additional settings:
indexing.maxthreads = 1 workunitexecutor.commitSize = 1
Here,- indexing.maxthreads prevents multiple indexes for a table being created in separate threads. In EDQ 12.2.1.4.4 and later this setting is not needed because the indexing logic has been updated.
- workunitexecutor.commitSize prevents multiple transactions on a single table happening in multiple threads. In EDQ 12.2.1.4.4 and later this value is set automatically.
Note that the setup process for the Oracle Enterprise Data Quality on Tomcat 12.2.1.4.3 and later Marketplace images has been updated to include Apache Derby as a schema configuration option. If selected, no further configuration is required.
Parent topic: Creating the EDQ Database Objects
Configuring Tomcat Application Server
Note:
If you are upgrading from Oracle Enterprise Data Quality (EDQ) 12.2.1.4.0 or
earlier to 12.2.1.4.1 or later versions, edit the
catalina.properties
file to remove the reference to Oracle
Application Development Framework (ADF) jars, and delete the ADF jars.
Optionally, you can also remove lib.adf
directory from
their respective shared library path.
If you are performing a fresh install of EDQ 12.2.1.4.1 or later versions, you need not set up ADF jars. However, if you are performing a fresh install of EDQ 12.2.1.4.0, follow the steps to set up ADF jars.
Create the necessary Oracle Application Development Framework (ADF) shared library:
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Creating Directories for Use With Tomcat Application Server
Create two empty directories to contain your EDQ configuration files. For example:
On Linux and UNIX operating systems:
/opt/edqconfig/oedqhome
/opt/edqconfig/oedqlocalhome
On the Windows operating system:
C:\edqconfig\oedqhome
C:\edqconfig\oedqlocalhome
The first directory (oedqhome
) is the base configuration directory and will contain the configuration files that should not be changed post-installation. The second directory (oedqlocalhome
) is the local configuration directory and will contain any custom settings that you create. Ensure that your application server user has read and write access to the two directories you create. For more information about these directories, see EDQ Directory Requirements
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Configuring EDQ to work with Tomcat Application Server
Follow these steps to run the EDQ Configuration Application (configapp
) to configure EDQ to work with Apache Tomcat and to populate the repository schemas with the required EDQ objects.
Note:
These instructions assume you have created the required database schemas as directed in Installing the Required External Software Components
To start the EDQ Configuration Application, follow these steps:
-
Log in to the system as your EDQ installation user.
-
Go to your
FMW_HOME
/edq/oracle.edq
directory. -
Start the Configuration Application by entering the following command:
java -jar configapp.jar
The EDQ Configuration Application is displayed.
Use Table 5-1 to configure EDQ:
Table 5-1 Running the EDQ Configuration Application
Screen | Action to Perform |
---|---|
EDQ Configuration Application Completion |
Click Begin to proceed with the configuration. You may cancel the installation at any time by clicking Cancel. |
Configuration Directory |
Specify the two empty directories that you created in Creating Directories for Use With Tomcat Application Server to contain your EDQ configuration files. Click Next to continue. |
Functional Packs |
Select the functional packs you want and are licensed to use. Click Next to continue. |
Configure the Configuration Schema |
From the Selection Type list, select the correct option for the configuration schema that you created in Creating the EDQ Database Objects.
Enter the user name and password for the configuration schema. Select the option for the type of database, either Oracle or Postgres. Enter the host name of the system that contains the database, its port number, and the database unique id. ( For Oracle the unique id is the Ensure that you configured the connection to the database correctly by clicking Test. Click Next to continue. |
Configure the Results Schema |
From the Selection Type list, select the correct option for the results schema that you created in Creating the EDQ Database Objects.
Enter the user name and password for the results schema. Select the option for the type of database, either Oracle or Postgres. Enter the host name of the system that contains the database, its port number, and the database unique id. ( For Oracle the unique id is the Ensure that you have configured the connection to the database correctly by clicking Test. Click Next to continue. |
Selected Options |
Review the summary of your selections. Use Back to modify any of your selections. Click Finish to complete the configuration and continue. |
EDQ Configuration Application Completion |
Click Done to exit the installation program. |
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Verifying EDQ Functional Packs
You can verify which EDQ functional packs have been installed by using the EDQ Configuration Application as described in Configuring EDQ to work with Tomcat Application Server Additionally, you should be aware of the following:
-
All Functional Packs are needed if you want to use the full capabilities of the EDQ Customer Data Services Pack on your EDQ server, such as for integration with Siebel Customer Relationship Management or Universal Customer Master.
-
All Functional Packs are needed if you want to install Oracle Watchlist Screening on your EDQ server.
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat
Deploying the EDQ Application on a Tomcat Application Server
The EDQ application must be manually deployed on Tomcat Application Servers.
Parent topic: Configuring Enterprise Data Quality with Apache Tomcat