Configuring Enterprise Data Quality with Apache Tomcat

6 Configuring Enterprise Data Quality with Apache Tomcat

This chapter describes how to configure EDQ and the database to operate with a Tomcat Application Server and perform the necessary additional configuration steps.

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

Before performing the procedures in this section, you must first read and satisfy the steps in:

Creating the EDQ Database Objects

EDQ requires two database accounts and two schemas. The first schema contains configuration data and the second contains results 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

This procedure configures an Oracle database as the repository for EDQ.

Create two database accounts named edqconfig and edqresults - or other names of your choosing. When selecting names, consider that one schema will be the configuration schema and the other will be the results schema.
Grant the following privileges to each of these accounts:
- CREATE SESSION (normally granted by CONNECT)
- CREATE INDEXTYPE (normally granted by RESOURCE)
- CREATE SEQUENCE (normally granted by RESOURCE)
- CREATE TABLE (normally granted by RESOURCE)
- CREATE TYPE (normally granted by RESOURCE)
- CREATE INDEX
- DROP TABLE
- DROP INDEX
- UNLIMITED TABLESPACE (recommended to allow the auto-extension of tablespace)
Additionally, for the configuration schema only, these grants are required:
```
GRANT CTXAPP TO user;
GRANT CREATE ANY JOB TO user;
```

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.

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 6-1 to configure EDQ:

Table 6-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. Do not use the JNDI Connection option. Enter the user name and password for the configuration schema. Select the option for the type of database. 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 `SID` not the service name. If you want to use a pluggable database, which requires a service name, you must use a raw JDBC URL or JNDI source.) 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. Do not use the JNDI Connection option. Enter the user name and password for the results schema. Select the option for the type of database. 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 `SID` not the service name. If you want to use a pluggable database, which requires a service name, you must use a raw JDBC URL or JNDI source.) 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.

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.

Deploying the EDQ Application on a Tomcat Application Server

The EDQ application must be manually deployed on Tomcat Application Servers.

Stop the application server.
Deploy the edq.war file on your application server. Or, if you are using Tomcat 10.1 or later, use jakartaee/edq.war

See the Tomcat Web Application Deployment web page at

http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html
To link EDQ to the base and local configuration directories that you created in Creating Directories for Use With Tomcat Application Server, you can do one of the following:
- On any of the EDQ-supported platforms, you can use a Java property named -Dedq.config.path that specifies the paths to those directories. The syntax is as follows, where path_to_base_config is the path to the base configuration directory and path_to_local_config is the path to the local configuration directory.
  
  Linux and UNIX (colon separates the paths):
```
-Dedq.config.path=path_to_base_config:path_to_local_config
```
  Windows (semi-colon separates the paths):
```
-Dedq.config.path=path_to_base_config;path_to_local_config
```
- On Windows, you can append an environment variable named EDQ_CONFIG_PATH to your JAVA_OPTS environment variable, as shown in the following, where path_to_base_config is the path to the base configuration directory and path_to_local_config is the path to the local configuration directory.
  
  Alternatively, you can set the EDQ_CONFIG_PATH environment variable.
```
EDQ_CONFIG_PATH="path_to_base_config;path_to_local_config"
```
For more information about setting Java parameters, see the Apache Tomcat Documentation website at

http://tomcat.apache.org/
Restart your application server service and ensure that edq.war is successfully deployed.