This chapter describes how to create the EDQ database repository, create an Oracle WebLogic Server domain for EDQ, start WebLogic Server, and configure WebLogic Server to provide EDQ web service.
Note:
These instructions apply to Oracle WebLogic Server environments only. If you are using Apache Tomcat, you must follow the directions in Section 5, "Configuring Enterprise Data Quality with Apache Tomcat."
This chapter includes the following sections:
Before performing the procedures in this section, you must first read and satisfy the steps in:
EDQ makes use of some database schemas. These schemas are the configuration schema (EDQCONFIG) and the results schema (EDQRESULTS). You create them with the Oracle Repository Creation Utility (RCU).
The person who runs RCU must be able to log into the database with DBA privileges. If you cannot run with DBA privileges, RCU can create a script for a DBA to run later.
Note:
Do not use RCU to upgrade EDQ; use the instructions in Section 8, "Upgrading Enterprise Data Quality On WebLogic Servers."
Make certain the repository database is running.
Run the command shell or console of the operating system.
Start RCU from the FMW_HOME/oracle_common/bin directory, where FMW_HOME is the Oracle Fusion Middleware installation directory.
On Linux:
./rcu
On Windows:
rcu.bat
Complete the RCU configuration screens by following the instructions in Table 4-1.
Table 4-1 Running the RCU Program
| Screen | Action to Perform |
|---|---|
|
Welcome |
Click Next to proceed with the installation. You may cancel the installation at any time by clicking Exit. |
|
Create Repository |
Click Next to continue. This uses the default Create Repository and System Load and Product Load options. This requires the person running RCU to have DBA privileges. |
|
Database Connection Details |
Select Oracle Database from the Database Type list. Specify the host name where your Oracle database is running. Enter the port number for your database. The default port number for Oracle Database is 1521. Specify the service name for the database. Typically, the service name is the same as the global database name. For example, Enter the user name for your database. The default user name is Enter the password for your database user. Select SYSDBA from the Role: list. This is automatically selected when the user is Click Next to continue. |
|
Checking Global Prerequisites |
When the prerequisites checking progress has reached completion, click OK to continue. |
|
Select Components |
Select Create new prefix and enter a prefix name for the database schemas you are creating. For example, Select the Oracle AS Repository Components check box. The Oracle EDQ check boxes that create the EDQ configuration and results schemas in the database repository are then automatically selected. Click Next to continue. |
|
Checking Component Prerequisites |
When the prerequisites checking progress has reached completion, click OK to continue. |
|
Schema Passwords |
Ensure that Use same passwords for all schemas is selected. Enter the password that you want to use for all of the EDQ database schemas in both password fields, then click Next to continue. |
|
Map Tablespaces |
The default EDQ tablespaces that will be created by RCU are displayed by component. You can change the tablespaces by clicking Manage Tablespaces and then modifying the information. Oracle recommends using one user tablespace for the Click Next to continue. |
|
Map Tablespaces |
Click OK to create any non-existent tablespaces in your schema, then click OK when the operation completes. |
|
Summary |
Review the database details, then click Create to continue. A status screen is displayed that shows the progress of creating the repository components. |
|
Completion Summary |
Click Close to exit the RCU program. |
These instructions use the Configuration Wizard to create a Basic WebLogic Server domain for EDQ, with the following:
One Administration Server and one managed server (no additional managed servers or clusters).
One (non-RAC) data source for the EDQ configuration schema and one data source for the results schema. You can convert the datasources to RAC data sources with the Configuration Wizard, or you can do so later through the WebLogic Server Administration Console.
A Node Manager configuration that is predefined within the EDQ domain as edq/nodemanager. You cannot edit the Node Manager home in this configuration. You can change this configuration during this procedure, if desired.
Note:
Oracle recommends the use of managed servers that are administered by Oracle WebLogic Node Manager. You can configure Managed Servers, Clusters, and other advanced features through the Configuration Wizard, but it may be more practical to do so by using the WebLogic Server Administration Console after the initial configuration process. For more information, see Section 4.5, "Running Multiple EDQ Servers in the Same Domain."
To start the Domain Configuration wizard, follow these steps. You will run the configuration wizard in graphical mode.
Log in to the system as the EDQ installation user that you created in Section 1.4.5, "Operating System User."
Go to FMW_HOME/oracle_common/common/bin directory, where FMW_HOME is the Fusion Middleware installation directory.
Start the wizard by entering the following command:
On Linux or UNIX operating systems:
./config.sh
On Microsoft Windows operating systems:
config.cmd
The WebLogic Server Configuration Wizard is displayed.
Table 4-2 describes the screens in the configuration wizard. Certain screens are displayed only in certain situations depending on your selections. For help with any screen, click the Help button.
Table 4-2 Configuration Screens for Creating a New EDQ WebLogic Server Domain
| Screen | Action to Perform |
|---|---|
|
Configuration Type |
Select Create a new domain. In the Domain Location box, enter the path to the new domain (for example, Click Next to continue. |
|
Templates |
Select Oracle Enterprise Data Quality – 12.1.3 (edq). Keep all default selections. Click Next to continue. |
|
Application Location |
Specify the directory in which the applications of the EDQ domain are to be stored. Click Next to continue. |
|
Administrator Account |
Specify the user name and password for the EDQ domain's administrator account. This account is used to administer the domain and to log into the EDQ application. Click Next to continue. |
|
Domain Mode and JDK |
Domain Mode: Select the startup operation mode for your domain from the following options:
JDK: From the Available JDKs list, select the JDK that you installed in Section 2.2, "Installing a Java Development Kit to Support EDQ." Click Next to continue. |
|
JDBC Data Sources |
Default values are shown for the JDBC data sources for the EDQ configuration schema ( Click Next to continue. |
|
JDBC Data Sources Test |
Click Test Selected Connections to ensure that the configuration tool can connect to the data sources. To test connections, the targeted database must be running. To skip the test, deselect the check boxes. Click Next to continue. |
|
Database Configuration Type |
Ensure that RCU Data is selected. This populates the connection information you supplied when you ran the Repository Creation Utility (see Section 4.2, "Running the RCU Program"). If you must change any of these fields, ensure that you use the schema prefix ( When done, click Get RCU Configuration to connect to the Oracle Database and bind the EDQ schemas. Click Next to continue. |
|
JDBC Component Schema |
Accept the defaults to include the EDQ configuration and results schemas, and then click Next. |
|
JDBC Test |
All schemas are selected and automatically tested. Return to the previous screen to alter the connection configuration if necessary. Click Next to continue. |
|
Configuration Summary |
Review the configuration for your domain by selecting a view and then selecting individual items in the list for that view. If the domain is configured as you want it, click Create to create the domain. If you need to make changes to the configuration, click Back to return to the appropriate screen for the settings you want to change. |
|
Configuration Progress |
Shows the progress of the domain creation. When the process completes, click Next. |
|
Configuration Success |
Review the domain creation results. Click Finish to exit the Configuration Wizard. |
You must start your Administration Server, Managed Servers, and clusters to complete the installation. For information about starting managed servers using Node Manager and Administration Servers, see ”Starting and Stopping Oracle WebLogic Server Instances” in Oracle Fusion Middleware Administering Server Startup and Shutdown for Oracle WebLogic Server.
See also Section 6, "Setting Server Parameters to Support Enterprise Data Quality" for important information about setting server parameters for startup.
To support high availability scenarios, Oracle recommends that you configure a cluster of multiple EDQ servers to share the incoming load (for example, from a large number of simultaneous web service requests), and to provide continuous service in the event of failure of an individual server. This section provides some basic guidance about how to configure EDQ to support such a model using Oracle WebLogic Server.
Multiple EDQ managed servers can be configured to run in the same WebLogic Server domain either in a cluster or not, provided that each server has the following items that are separate and dedicated:
EDQCONFIG and EDQRESULTS schemas: Separate schemas can be created for different EDQ instances by re-running the Repository Creation Utility (RCU) and using different prefixes for the schema names (for example, DEV2 and so on).
JDBC data sources: You must create corresponding JDBC data sources for each of the schemas, each with different JNDI names. The WebLogic Server Configuration Wizard only creates the JDBC data sources for the first server. The remaining data sources must be created manually using the WebLogic Server Administration Console.
Configuration directories (base and local): The WebLogic Server Configuration Wizard creates the configuration directories for the first EDQ server, but you must copy the local configuration directory (oedq.local.home) from the first server to the other servers. The base configuration directory (oedq.home) can be shared across all managed servers. For more information about these directories, see Section 1.4.2, "EDQ Directory Requirements."
director.properties files: The director.properties file in each subsequent EDQ server's new configuration directory must be edited to point to the new JNDI names of the new data sources you created. You must also assign different management, FTP, and SSHD ports, because these ports are not defined in the managed server settings.
server listening port. Each server must listen on a different port.
The Java Required Files (JRF) Template must be applied to any managed servers that were created using the WebLogic Server Administration Console. This is equivalent to the library targeting performed automatically by the WebLogic Server Configuration Wizard.
The final step are:
Use the WebLogic Server Administration Console to modify the managed server settings for the additional EDQ servers.
Update the edq.config.path by configuring the server startup Arguments option in the Server Start tab to point to the relevant new configuration directories.
Once multiple EDQ servers have been configured, you can leave them un-clustered and accessed directly using their respective Launchpad URLs to the relevant port, or you can configure them as part of a cluster using standard WebLogic Server practices. You can configure a separate front-end load balancer to handle incoming web service requests through a single cluster URL.
Note:
Do not attempt to access the EDQ Launchpad using a load balanced cluster URL because it will be unclear which EDQ server is actually being accessed. Instead, log in to one of the servers directly using its dedicated port, and use the EDQ or WebLogic Server Console to connect to all servers in the cluster.