Instructions for launching, configuring and using the Oracle Enterprise Data

Quality on WebLogic image on Oracle Cloud Infrastructure

Launch

Perform these steps to create an instance of EDQ running on OCI from this image.

1. Having found this image on the OCI Marketplace, click on Get App
2. Select the OCI region where you want to install EDQ, and click on Launch Image
3. Log in to your OCI account
4. Click on the Launch Instance button
5. Select the latest version of the image from the drop-down list
6. Select the compartment where you wish to install Oracle Enterprise Data Quality
7. Review and accept the Oracle Terms of Use
8. Click on Launch Instance

OCI Configuration

On the Create Compute Instance page, specify the following:

1. Under Name your instance, enter your choice of name. For example, edq1
2. Under Select an availability domain for your instance, choose an availability
domain, ensuring that it is the availability domain where the Database Cloud Service
(DBCS) instance or Autonomous Database that you will use for the EDQ repository
database is installed.
3. Under Choose an operating system or image source, you will see the name of the
OCI Console Marketplace image: Oracle Enterprise Data Quality on WebLogic
4. Under Choose instance type, select Virtual Machine.
5. Under Choose instance shape, you will see a default shape, such as
the VM.Standard2.1 shape. If you want to specify another shape, click on Change
Shape. Note that we recommend a shape with at least 2 OCPUs to use EDQ.
6. Under Configure Networking:
a. From the Virtual cloud network compartment drop-down list, select the
compartment where your VCN has been set up.
b. From the Virtual cloud network drop-down list, choose your VCN.
c. Under Subnet compartment, specify the compartment containing the subnet
that you wish to use.
d. Under Subnet, specify the subnet you wish to use (this does not normally need
to be changed from the default once the Subnet compartment is selected)

Note: If the VM is associated with a public subnet and you want to assign a public IP
address, click on the Show Advanced Options link, choose the Networking tab, and then
check (tick) the Assign public IP address box.
 7. Under Add SSH Keys, choose one of the following options:
a. Select the Generate SSH Key Pair option if you do not yet have a public and
private key pair that you wish to use for the instance and you want to generate
and save new keys.
b. Select the Choose Public Key Files option and then click Choose Files to specify
the file containing your SSH public key if you generated one previously.
c. Select the Paste Public Keys radio button and paste the SSH public key content in
the text field provided, using the content of the public key generated previously.
d. Select No SSH Keys (not recommended)

8. Under Configure Boot Volume, accept the default volume size.

Note: The EDQ installation occupies a small amount of this volume. However, the
EDQ file landing area is also on this volume. If you know you will require a very large
file landing area, you may wish to extend the default size.

9. Click the Create button at the bottom of screen.

After the instance has been created (provisioned), it will appear in the instance list. To view
full details about it, including IP addresses, click the instance name in the list.

Connecting to EDQ

When the instance is fully provisioned and running, you can connect to it from a browser at
the address https://myinstancename/setup to complete the configuration.

Here, myinstancename refers to the DNS hostname or IP address, if connecting to the

instance externally. If connecting to the instance from within the Virtual Cloud Network
(VCN), you can use the Internal FQDN (fully qualified domain name), which is displayed on
the OCI Console once the instance has been provisioned. For such internal connections, you
can copy and paste this into your browser window and append /setup to get to the EDQ
configuration page.

Once you have successfully configured EDQ, you can access the EDQ Launchpad at either
http://myinstancename/edq or https://myinstancename/edq.

System Administrators can also connect to the instance using SSH. See the following OCI
documentation for more information on how to do this:

https://docs.cloud.oracle.com/iaas/Content/GSG/Tasks/testingconnection.htm

EDQ Configuration

Using your browser, navigate to https://myinstancename/setup.

At initial setup, this page configures EDQ’s access to its repository database and specifies
details of the WebLogic domain that will be created. For the repository database, EDQ can
use either a standalone database instance (an instance of the Oracle Database Cloud Service
or DBCS), or an Autonomous Database (either Oracle Autonomous Data Warehouse Cloud,
or Oracle Autonomous Transaction Processing). In both cases, this database must be
available in the same OCI tenancy as this EDQ instance.

Important Note If you want to use an Autonomous Database for the EDQ repository, you
must first set up a dynamic group and policy in OCI to allow OCI Compute instances to
retrieve details of autonomous databases and download wallets for access.

For detailed steps on how to do this, see Appendix A of this document.

To complete the configuration, click on the Configure button.

1. In the Database Details section, choose your Database Type; either Autonomous
Database, or Standalone Database Instance.

2. If you selected Autonomous Database, select the Autonomous Database instance

that you want to use from the list of available instances.

Note: If no autonomous databases appear in the list, ensure you have followed the
procedure in Appendix A to enable EDQ to access autonomous databases in your
tenancy, and that you have a suitable autonomous database in your tenancy.

3. If you selected Standalone Database Instance, enter the Host name, Port, and
Service name of the of the Database Cloud Service instance you will be using to host
the EDQ repository database schemas.

4. There are three options for RCU usage, as below. Select the option according to your
requirements. Most new installations will use the first option.

a. Run RCU to create schemas

This (the default option) instructs the configuration page to run the RCU on the
specified database to create all the schemas required to run a new instance of EDQ
on WebLogic. Note that schemas will be created with fairly small, but auto-
extendable, tablespaces in order to ensure that RCU runs quickly. You may wish to
extend the tablespace for EDQRESULTS subsequently.

Note: With this option specified, when running against an Autonomous Database,
the RCU will use the DATA tablespace for the EDQ schemas. When running against a
standalone database instance, it will use the USERS tablespace.

b. Use existing RCU schemas

 This option allows the use of newly created schemas that have already been set up
by running RCU on the specified database before launching this image. This may be
useful for installers who wish to set their own tablespace and other RCU options.

c. Use existing RCU EDQ schemas

This option provides a way to use an existing valid EDQ 12.2.1.3.0 or later repository
database. With this option, the full set of schemas that RCU normally creates,
including the three EDQ schemas (EDQCONFIG, EDQRESULTS, and EDQSTAGING)
must exist on the specified database and must be valid for EDQ 12.2.1.3.0. This
option drops and recreates all the schemas except for the three EDQ schemas and
the STB schema (used as the schema registry). Use this option if you have replicated
the EDQ schemas from an on-premise installation or if you have such schemas from
using a previous image.

Note: The EDQ schemas must have been created by RCU, so schemas that have
been used by an EDQ Tomcat installation will not be valid.

5. Enter the credentials to your database.

a. If you selected an Autonomous Database, enter the password for the ADMIN
user.
b. If you selected a Standalone Database Instance, enter the SYSDBA User name
and Password for a database user with SYS credentials

6. Enter the Schema Prefix that you want to use (or are currently using, if you are using
existing schemas under the RCU usage option)
7. Tick the Drop existing schemas with the same prefix option if you have used this
prefix before (for example for a Test instance) but want to drop these schemas and
set them up again. Note that there is no harm in ticking this option if the schemas do
not exist.
8. Enter and confirm the Schema password that you want to use (or enter the correct
schema password, if you are using existing schemas)
9. In the Domain Details section, enter and confirm a Weblogic admin password to use
to log in to the WebLogic console and to EDQ as the initial administrator user
(weblogic)
10. Finally, choose whether to deploy either of the two additional WebLogic features,
Enterprise Manager, and/or Oracle Web Services Manager (OWSM). Note that the
use of OWSM may require an additional license.
11. Click on Validate to check that the provided details are correct.
12. Once the validation check succeeds, click on Apply to proceed.
Example EDQ Database Configuration screens:

Figure 1 - Example configuration using Autonomous Database

 Figure 2 - Example configuration using Standalone Database

13. Once the configuration is complete, a Configuration Successful message will be

displayed. Click on Close to close this message.
14. A message will be displayed that the EDQ Admin Server is running. Click on the link
provided (Click here to login) to go to the WebLogic Console
(http://fullyqualifieddomainname/console), where you have full control of the
domain. Bookmark this link for future access to the console.

Starting EDQ

1. In the WebLogic console, click on Environment – Servers to see the list of servers in
the domain (the AdminServer, which will be running, and edq_server1 which will be
listed as Stopped).
2. Click on the Control tab, select edq_server1 and click on the Start button to start
EDQ:
 3. Once the server has started, go to http://myinstancename/edq or
https://myinstancename/edq to display the EDQ Launchpad. Bookmark this link for
future access to EDQ.

On first logging in to any EDQ user application or to the Launchpad, you should log in as the
user name weblogic with the password you specified on the configuration page.

Note that this account is essential in order to be able to use EDQ. Additional users and their
privileges can be set up in the WebLogic console, or you can configure WebLogic to connect
to an Oracle Identity Cloud Service or other identity provider. Instructions for this are
documented separately.

For further information on using EDQ, please consult the EDQ documentation site:
https://docs.oracle.com/en/middleware/enterprise-data-quality/12.2.1.4/index.html

Ports

This image opens the following ports by default:

 80, to enable HTTP access

 443, to enable HTTPS access
 2222, to enable EDQ's SFTP interface to enable the upload and download of files to
EDQ's configuration or file landing areas using an SFTP client
  8090, to enable access to EDQ’s JMX interface, for monitoring of EDQ and to use the
command line interface should this be required. Note that the Java RMI port is also
set to 8090.

No other ports need to be open to use the full functionality of EDQ.

Additional Settings used by the image

The image provisioning process detects the amount of physical memory available on the
chosen compute shape and sets the maximum heap memory available to EDQ to 75% of this
– for example on a shape with 64GB of memory, the max heap is set to 48GB.

Installation Locations

Please note the following installation locations used by this image. These are relevant for
system administrators, in case they need to change any aspects of the installation:

Area Location on server

Oracle Home /opt/fmw/wls/edq
(home of the
EDQ
installation
for patching
etc.)
OPatch /opt/fmw/wls/OPatch
Home
WebLogic /opt/fmw/domains/edq
domain
EDQ local /opt/fmw/domains/edq/config/fmwconfig/edq/oedq.local.home
home
EDQ /opt/fmw/domains/edq/config/fmwconfig/edq/oedq.local.home/director.properties
configuration
file

Patching

This image contains a standard installation of EDQ 12.2.1.4.1 – that is, EDQ 12.2.1.4.0 and
bundle patch 32134845 - on WebLogic Server 12.2.1.4.0, using a separate Database Cloud
Service instance or an Autonomous Database as the EDQ repository database.

Any eligible patches that you require can be downloaded and applied using the standard
OPatch mechanism after logging into the instance using SSH.

You need to run OPatch as the user fmw, so an example command (to check the inventory)
is:
$ sudo –u fmw /opt/fmw/wls/OPatch/opatch lsinventory
Appendix A – Configuring OCI Policies to enable EDQ to use an Autonomous Database
as its Repository

The setup page that enables EDQ to connect to an Autonomous Database to use as its repository
uses REST APIs to see the list of available databases and to download the wallets used to connect to
them. For this to work, it is necessary to configure a policy that enables the OCI compute images to
access these APIs.

This is based on the OCI documentation here:

https://docs.cloud.oracle.com/iaas/Content/Identity/Tasks/callingservicesfrominstances.htm

The following steps are required:

1. In the OCI Console, navigate to Identity > Dynamic Groups

2. Create a Dynamic Group and give it a name, for example edq_group

3. Create a Matching Rule that matches any instance in the compartment where you will be
installing EDQ, such as:

ANY {instance.compartment.id = ‘OCID of compartment where you will be installing EDQ’}

Note: This can be built using the Rule Builder, with the Attribute ‘Match instances in Compartment
ID:’ and the Value set to the OCID of the compartment. To get the OCID of your compartment,
navigate to Identity > Compartments and copy the OCID of the compartment you want to give
access. Then paste it into the Rule Builder above.

4. In the OCI Console, navigate to Identity > Policies

5. Create a Policy (or you can extend an existing Policy if you have one). If you are creating a
policy, give it a name such as ‘edq’ and a description such as ‘Policy for API calls from EDQ
servers’. Select the default Policy Versioning option (Keep Policy Current).

6. Add the following two policy statements:

Allow dynamic-group [name of dynamic group] to inspect autonomous-databases in

compartment [name of compartment]

Allow dynamic-group [name of dynamic group] to manage autonomous-databases in

compartment [name of compartment] where request.operation =
‘GenerateAutonomousDatabaseWallet’

For example, if your dynamic group is named ‘edq_group’ and your compartment is named ‘edq’,
the two statements would read as follows:

Allow dynamic-group edq_group to inspect autonomous-databases in compartment edq

 Allow dynamic-group edq_group to manage autonomous-databases in compartment edq
where request.operation = ‘GenerateAutonomousDatabaseWallet’

Note: This policy allows servers in a compartment to access autonomous databases in the same
compartment. If you need your OCI EDQ server(s) to be able to access Autonomous Databases in
other compartments, you will need to define appropriate additional policies to enable this, including
a policy statement defined at the root level that allows the dynamic group to inspect compartments
in the tenancy, i.e.:

Allow dynamic-group [name of dynamic group] to inspect compartments in tenancy

Once such compartments can be inspected, the statements allowing access to the autonomous
databases in these compartments will work.
Appendix B - Connecting EDQ to Autonomous Databases as Data Stores

EDQ offers two different ways of connecting to Autonomous Databases as Data Stores.

For full information, see the documentation here:

https://docs.oracle.com/en/middleware/fusion-middleware/enterprise-data-
quality/12.2.1.4/edqoh/data-stores.html

To use the option to connect using an uploaded wallet:

1. Obtain Autonomous Database Wallet Credentials

Connecting to ADW or ATP requires the wallet credentials. To obtain the wallet:

a. Access your ADW or ATP Instance via the Service Console

 Click on DB Connection
 Click Download Client Credentials

 Enter a password for the wallet and select Download.

o Note that the password must be at least 8 characters long and contain alphabetic
characters with numbers or special characters. Save this password.
o This will download a zip file with credentials required for EDQ and other tools to
connect to the ADB

 Save this file and the password for any connectivity to ADB (SQL Developer / EDQ etc.)

2. Upload the Wallet Credentials to your EDQ server

a. Unzip the zip file locally

b. If the connection from the EDQ server to the ADB requires the use of a proxy server,
for example because your EDQ server is on a Virtual Cloud Network (VCN) and your
ADB is not, edit the extracted tnsnames.ora file to add proxy server details, by
adding (https_proxy=proxyhost) (https_proxy_port=portnumber)
within each tnsnames entry.
 For full information on this see the documentation here:
https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-
cloud/user/connect-preparing.html#GUID-EFAFA00E-54CC-47C7-8C71-
E7868279EF3B

For example:

c. Connect to EDQ using an SFTP client such as Filezilla, using Port 2222 and an EDQ
administrator user name and password (such as user name dnadmin and the
password you changed to when you first logged in to EDQ)
d. Create a subfolder of the landing area for your connection, e.g. adb
e. Upload the following files from the extracted zip to the subfolder you just created:
 tnsnames.ora
 cwallet.sso

3. Add a Data Store in Director to connect to the Autonomous Database

a. Log into Director from the EDQ Launchpad

b. Either in a new project, or within an existing project, right-click on Data Stores, and
select New Data Store…
c. Under Data is accessed from, select Server
d. Under Category, select Database
e. Under Type, select Oracle Autonomous Database (ADW or ATP) with uploaded
wallet
f. Click Next
g. Enter the Service Name of your ADW or ATP instance, and the name of your
subfolder in the EDQ landing area of your tnsnames.ora and cwallet.sso files
 Note: If you did not create a subfolder and uploaded the files directly to the landing
area you can leave this folder blank.

h. Enter a valid User name and Password for the ADW or ATP instance.
i. Enter a Schema, or leave this blank if you wish to use the default schema for the user

For example:

j. Click on the Test… button

k. If successful, the message You successfully connected to the specified Data Store
will be displayed. Click OK.

You can now use the Data Store both for reading data from your ATP or ADW
instance and for exporting data to it.
Appendix C – Attaching a New SSL Certificate, and httpd settings

On the EDQ OCI Marketplace images, SSL is provided by Apache httpd. This is configured
with a dummy certificate by default.

To install a new certificate, replace this and the key following the Apache httpd
documentation here: https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html

The relevant configuration file on the instance will be

at /etc/httpd/conf.d/ssl.conf.

Note also that httpd is configured by default with a 15 minute connection timeout – the
ProxyTimeout setting in the configuration file /etc/httpd/conf.d/edq.conf. If
required, this can be altered, for example to 3600 to allow an hour.

After changing any httpd settings, restart httpd:

$ sudo systemctl restart httpd.service