Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide, Release 11g R1 (11.1.1.6)

Release 11g R1 (11.1.1.6)

E29137-05

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Installation Overview

- 1.1 Overview

- 1.2 Oracle DataLens Server Types

- 1.2.1 Oracle DataLens Administration Server

- 1.2.2 Oracle DataLens Transform Servers

- 1.2.3 Oracle DataLens Server Topology

- 1.3 Installable Products

- 1.4 Installation Roadmap

2 Preparing for Installation

- 2.1 Installer Type

- 2.2 Product Distribution

- 2.2.1 Downloading the Software From the Oracle Software Delivery Cloud

- 2.3 Installation Prerequisites

- 2.3.1 Hardware and Software Requirements

- 2.3.2 Establishing the Required User Accounts

- 2.3.2.1 EDQP User

- 2.3.2.2 WebLogic User

- 2.3.2.3 Database Administration User

- 2.3.3 Installing the Java Development Kit

- 2.3.4 Downloading the WebLogic Server Installer From Oracle E-Delivery

- 2.3.5 Determining the Type of Database Your Oracle DataLens Administration Server Will Use

- 2.4 Selecting Directories for Installation

- 2.4.1 Choosing a Middleware Home Directory

- 2.4.2 Choosing Product Installation Directories

- 2.5 Choosing the Type of Installation

3 Running the Installation Program in Console Mode

- 3.1 Starting the Installation Program in Console Mode

- 3.1.1 Starting Installation Programs in Console Mode on Linux and UNIX

- 3.1.2 Starting the Installation Program in Console Mode on Windows

- 3.2 Installing EDQP in Console Mode

- 3.3 Verifying the Installation

- 3.4 Performing Post-Installation Steps

- 3.5 Uninstalling Your Software in Console Mode

4 Changing the Default Oracle DataLens Server Database

- 4.1 Preparing to Change the Default Oracle DataLens Server Derby Database

- 4.2 Changing the Derby Database to an Oracle DataBase or PostgreSQL Database

- 4.2.1 Creating the Oracle Database PDQRespository Schema

- 4.2.2 Creating the PostgreSQL Database PDQRespository Schema

- 4.3 Configuring the EDQP WebLogic Server Domain to Use the PDQRespository Data Source

- 4.4 Autodeploying Data Lenses to the New Database

A Oracle DataLens Server Graphical Installation

- A.1 Graphical Mode Installation

- A.1.1 Starting the Installation Program in Graphical Mode on Linux and UNIX

- A.1.2 Starting the Installation Program in Graphical Mode on Windows

- A.1.3 Installation Screen Responses

- A.1.4 Installation Screens

- A.1.4.1 Welcome

- A.1.4.2 My Oracle Support Update

- A.1.4.3 Prerequisite Checks

- A.1.4.4 Installation Location

- A.1.4.5 Installation Summary

- A.1.4.6 Installation Progress

- A.1.4.7 Installation Complete

- A.2 Post-Installation Configuration

- A.2.1 Starting the Post-Installation Configuration Program on Linux and UNIX

- A.2.2 Starting the Post-Installation Configuration Program in Graphical Mode on Windows

- A.2.3 Post-Installation Configuration Screen Responses

- A.2.4 Post-Installation Configuration Screens

- A.2.4.1 Configuration Wizard Welcome

- A.2.4.2 Select Domain Source

- A.2.4.3 Specify Domain Name and Location

- A.2.4.4 Configure Administrator User Name and Password

- A.2.4.5 Configure Server Start Mode and JDK

- A.2.4.6 Select Optional Configuration

- A.2.4.7 Configure the Administration Server

- A.2.4.8 Configuration Summary

- A.2.4.9 Creating Domain

- A.2.5 Modifying Environment Variables

- A.2.6 Start Your WebLogic Server

- A.2.7 Configuring the EDQP WebLogic Server Domain to Use the PDQRespository Data Source

B Known Issues

- B.1 Oracle DataLens Server Conflicts with QuickTime

- B.2 Oracle DataLens Server Port Number

- B.3 Privilege Problems

- B.4 WebLogic Server Installation Issues

C Configuring JDBC Database Drivers

Oracle® Enterprise Data Quality for Product Data

Oracle DataLens Server Installation Guide

Release 11g R1 (11.1.1.6)

E29137-05

May 2013

Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide, Release 11g R1 (11.1.1.6)

E29137-05

Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Lorna Vallad

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

The purpose of the Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide is to describe the installation procedure for Oracle DataLens Servers on Linux, UNIX, and Windows platforms.

Audience

This document is intended for system administrators or application developers who are installing an Oracle DataLens Server. It is assumed that readers have a basic understanding of the DataLens technology and have a general understanding of Linux, UNIX, and Windows platforms.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the documentation set:

- The Oracle Enterprise Data Quality for Product Data Hardware and Software Specification details the systems software and hardware specifications necessary for the Enterprise DQ for Product software.

- The Oracle Enterprise Data Quality for Product Data Release Notes describes the features of each release of the product

- The Oracle Enterprise Data Quality for Product Data Getting Started Guide provides information about how to get started with EDQP and use the Application Launch Pad to start client applications.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide provides detailed Oracle DataLens Server installation instructions.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide provides information about managing an Oracle DataLens Server.

- The Oracle Enterprise Data Quality for Product Data Glossary provides definitions to commonly used Enterprise DQ for Product technology terms.

See the latest version of this and all documents in the Oracle Enterprise Data Quality for Product Data Documentation Web site at

http://docs.oracle.com/cd/E35636_01/index.htm

The following documents may also be useful:

- Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1(10.3.6)
http://docs.oracle.com/cd/E23943_01/doc.1111/e14142/toc.htm

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Installation Overview

This chapter lists the products that you can install with Oracle Enterprise Data Quality for Product Data (EDQP) Oracle DataLens Server installation program. It also includes the Oracle DataLens Server installation roadmap.

- Section 1.1, "Overview"

- Section 1.2, "Oracle DataLens Server Types"

- Section 1.3, "Installable Products"

- Section 1.4, "Installation Roadmap"

1.1 Overview

The EDQP Oracle DataLens Server can be configured to run with multiple servers:

- Oracle DataLens Administration Server

- Oracle DataLens Transform Server

The administration of all servers in a multi-server configuration is controlled with the Oracle DataLens Administration Server. The purpose of the Administration Server is to manage the various administrative tasks of the servers for the Server Groups (referred to as Transform Servers) and can itself serve as its own Transform Server when installed alone in a single node configuration. By spreading the data processing load across multiple servers the Oracle DataLens Server system provides scalability and configuration control over the various functional areas involved in developing, testing, and ultimately executing Oracle data lens jobs.

The type of Oracle DataLens Server Group that a Transform Server belongs to controls the individual server functionality. A Server Group may contain one or many physical servers. There are three types of Server Groups:

- Development Server Group

- Production Server Group

- Quality Assurance Server Group

The Server Groups contain individual Oracle DataLens Transform Servers on physical machines that can load balance among servers within the group. The data lenses and DataLens Service Applications (DSAs) are deployed from one group to the next beginning with the development group, then migrating to the Quality Assurance Group for testing before arriving in the Production Group for deployment to production. This multiple group migration function facilitates an enterprise business process where multiple functional areas work on data lens objects in stages before releasing them to production.

1.2 Oracle DataLens Server Types

The following sections describe the types of Oracle DataLens Servers.

1.2.1 Oracle DataLens Administration Server

An Oracle DataLens Administration Server is used to:

- create and maintain users, and roles and responsibilities,

- security,

- configure servers, connections, and Web services,

- manage jobs, and

- manage the creation, maintenance, and testing of data lenses, and DSAs.

Application Studio and Knowledge Studio users connect to this server for archiving and versioning, locking for update, and sharing data lenses and DSAs with other users. Only one Oracle DataLens Administration Server is allowed per deployment.

1.2.2 Oracle DataLens Transform Servers

An Oracle DataLens Transform Server is used for running jobs and for deploying data lenses and DSAs in a production environment. They are also used for development and testing. Transform Servers do not have administrative privileges.

1.2.3 Oracle DataLens Server Topology

The Oracle DataLens Server topology consists of two components: the Administration Server and one or more Transform Servers that reside in one or more Server Groups.

1.3 Installable Products

You can install the following products using the Oracle DataLens Server installer on the supported Linux, UNIX, and Windows operating systems:

- Oracle DataLens Server, both Administration Server and Tranform Server.

- Oracle WebLogic Server, a complete application server that implements Java Enterprise Edition 5 (JEE 5) technologies, Web services, and other leading Internet standards to provide a reliable framework for highly available, scalable, and secure applications and services. It includes administration tools and add-on technologies, such as the Administration Console, Web Server plug-ins, Java Database Connectivity (JDBC) drivers, and is a complete installation.

To get started with the installation, refer to Section 1.4, "Installation Roadmap."

1.4 Installation Roadmap

Table 1-1 describes the high-level tasks that are required to install the WebLogic Server and Oracle DataLens Servers.

Table 1-1 EDQP Product Installation Procedure Tasks

Task

Description

Documentation

Step 1 - Obtain the appropriate installation file for your platform

The software is downloaded from the Oracle Software Delivery Cloud Web site. The installer you use depends on your platform.

For information about how to download the software, see Section 2.2, "Product Distribution."

Step 2 - Complete the installation planning requirements

Ensure that your system environment meets the requirements for the installation. Also, determine your Oracle Middleware home directory, product installation home directories, and Oracle DataLens Administration Server database type.

For installation requirements, see Section 2.3, "Installation Prerequisites."

For information about installation home directories, see Section 2.4, "Selecting Directories for Installation."

Step 3 - Install the Oracle Java Development Kit (JDK)

Download and install the correct JDK for your operating system and system processor.

For instructions, see "Installing the Java Development Kit".

Step 4 - Determine if the WebLogic Server is installed.

Examine your system and verify whether or not you have installed the WebLogic Server product. If you don't have the WebLogic Server already installed, the EDQP installation scripts can install and configure the WebLogic Server and necessary domain.

For information about the WebLogic Server installation, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

To install WebLogic Server with the EDQP installer, you must download the WebLogic Server product from the Oracle Software Delivery Cloud Web site. See Section 2.3.4, "Downloading the WebLogic Server Installer From Oracle E-Delivery".

Step5 - Determine the appropriate installation mode for your situation

There are two installation modes: console mode or graphical mode. Oracle recommends that you use the console installation.

For information about installation modes, see Section 2.5, "Choosing the Type of Installation."

Step 6 - Determine the type of server to install

There are two types of installation Administration Server or Tranform Server. The type of installation depends on the type of Oracle DataLens Server you want to install.

For information about the installation types, see Section 1.3, "Installable Products."

Step 7 - Install the software

Run the installation program in the desired installation mode. In each installation mode, you have the option to create a detailed installation log.

For installation instructions, see the following chapter that is appropriate for the installation mode you want to use:

- Section 3, "Running the Installation Program in Console Mode."
Oracle recommends that you use the console installation

- Section A, "Oracle DataLens Server Graphical Installation."

2 Preparing for Installation

This chapter describes how to prepare to install your Oracle DataLens Servers, as well as raises topics that the you should consider and be familiar with before installation begins, including the following:

- Section 2.1, "Installer Type"

- Section 2.2, "Product Distribution"

- Section 2.3, "Installation Prerequisites"

- Section 2.4, "Selecting Directories for Installation"

- Section 2.5, "Choosing the Type of Installation"

2.1 Installer Type

The following types of Oracle DataLens Server installers are available:

- Generic Package installer—This type of installer is a .zip file. It does not include the Oracle Java Platform, Standard Edition Development Kit (JDK). You can use this type of installer to install the product on any supported platform on which Java is already installed. Additionally, it includes each of the supported operating system-specific installers that are either the dlsinstall_linux.sh or dlsinstall_solaris.sh files or the dlsinstall_windows.bat file, depending on your platform.

For information on how to obtain the appropriate installer for your platform, see Section 2.2, "Product Distribution."

2.2 Product Distribution

The Oracle DataLens Server installers are distributed in the following ways:

- Download from the Oracle Software Delivery Cloud web site at http://edelivery.oracle.com/. Only the Generic Package installer is available from this site; Upgrade installers are not available here. These files are downloaded as ZIP files. For information about how to download from this site, see Section 2.2.1, "Downloading the Software From the Oracle Software Delivery Cloud."

2.2.1 Downloading the Software From the Oracle Software Delivery Cloud

To download the installer from the Oracle Software Delivery Cloud web site:

1. Enter the Oracle Software Delivery Cloud URL into a web browser:
http://edelivery.oracle.com/

2. Sign into the site.

3. If prompted, choose your language and click Continue.

4. Complete the Export License Agreement as instructed on the site, and then click Continue.

5. On the Media Pack Search page, select E-Business Suite from the Select a Product Pack drop-down list.

6. From the Platform list, select your operating system.

7. Click Go.

8. Select the Oracle Enterprise Data Quality for Product Data 11 Media Pack option and click Continue.

9. Click the Download button.

10. Browse to the directory where you want to save the file. Click Save to start the file download. A compressed ZIP file is downloaded.

11. Extract the ZIP file to the following directory:
On Linux and UNIX: /opt/edqp_install

On Windows: C:\edqp_install

The installation directory now contains the edqp directory. The installers are in the edqp/Disk1 directory. You have all of the files necessary to install Enterprise DQ for Product though additional software is may be required as described in the following section.

2.3 Installation Prerequisites

The following sections describe the installation prerequisites:

- Section 2.3.1, "Hardware and Software Requirements"

- Section 2.3.2, "Establishing the Required User Accounts"

- Section 2.3.3, "Installing the Java Development Kit"

- Section 2.3.4, "Downloading the WebLogic Server Installer From Oracle E-Delivery"

- Section 2.3.5, "Determining the Type of Database Your Oracle DataLens Administration Server Will Use"

2.3.1 Hardware and Software Requirements

You must ensure that the following Oracle DataLens Server hardware and software requirements are observed. These requirements represent the certified and supported server configurations.

Verify that you have met the minimum server requirements using the Oracle Enterprise Data Quality for Product Data Hardware and Software Specification found at the Oracle Enterprise Data Quality for Product Data Documentation web site:

http://download.oracle.com/docs/cd/E20593_01/index.htm

That document contains all necessary specifications including example server configurations. Oracle DataLens Servers have been certified with these hardware and software requirements. For list of certified platforms and versions for Enterprise DQ for Product prior to installation, see Oracle Enterprise Data Quality for Product Data Certification Matrix at

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Locate Oracle Enterprise Data Quality in the Product Area column and then click the System Requirements and Supported Platforms for Oracle Enterprise Data Quality for Product Data 11gR1 (11.1.1.x) Certification Matrix (xls) link.

2.3.2 Establishing the Required User Accounts

Three different types of user accounts are required to install and maintain EDQP. You must establish the user accounts described in the following sections.

Note:
All administration user accounts created must be unique to ensure a secure environment.

2.3.2.1 EDQP User

A unique administrator user account (dlsadmin for example) is used for all of the servers in the EDQP Server Topology. You then use this administrative user throughout your Oracle DataLens Server Topology to install or maintain these servers.

Contact your system administrator for assistance in creating a new or identifying an existing administrator user account (dlsadmin or other) on the servers that you want to use in the EDQP Server Topology. The administrator user must also adhere to the WebLogic Server security requirements. See Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server 11g Release 1 (10.3.6) and Oracle Fusion Middleware Securing a Production Environment for Oracle WebLogic Server 11g.

Additionally, this administrator user must have full permissions (read, write and execute) to the directories that will contain the EDQP installation files, target installation directory, and all database directories.

Always use this administrator user when logging into any of the Oracle DataLens Servers to perform installation, upgrades, or maintenance. This is applicable to all operating systems. Each full installation results in a separate WebLogic Server instance. When installing an Oracle DataLens Administration Server and a Transform Server, separate WebLogic Server instances are created for each and the login credentials are not shared across the two servers. Logging into a Transform Server or WebLogic Server requires the Administration Server user name and password.

Note:
When installing EDQP (or WebLogic) on a UNIX or Linux operating system, do not use the root user as your administrator user account.

2.3.2.2 WebLogic User

A WebLogic administrator user account is necessary to install WebLogic and create the EDQP domain during installation. This is the user account you will then use to administer the domain in the WebLogic Administration Console.

You can use the default WebLogic administrator user (dlsadmin), create a new user, or specify an existing WebLogic administrator user during the installation.

If you are not installing WebLogic as part of your EDQP installation, then you must ensure that you specify the WebLogic administrator user that was used to install the WebLogic instance you want to use with EDQP.

2.3.2.3 Database Administration User

You can create a new database administrator user account or use an existing one that has the privileges to access to the database and ability to create schemas and run the database product. This is applicable to any supported database that you want to use with EDQP.

2.3.3 Installing the Java Development Kit

You must install a supported JDK since both the EDQP and WebLogic Server products rely on it. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications.

Install an EDQP supported JDK (see Section 2.3.1, "Hardware and Software Requirements") by downloading and installing it using the instructions provided at

http://www.oracle.com/technetwork/java/javase/downloads/index.html

On Windows systems, ensure that you do not install the JDK into a directory that contains spaces, which is the default. For example, you could install the JDK into C:\Programs\Java\jdk1.7.0_13.

On Solaris systems, you must install both the 32-bit and 64-bit JDKs in order to run java applications. Install these JDKs by following the instructions at the Oracle Java SE documentation website at

http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html

2.3.4 Downloading the WebLogic Server Installer From Oracle E-Delivery

It is necessary to download the WebLogic Server installer and save it to the same directory that contains the EDQP console mode installer, as described in Section 2.5, "Choosing the Type of Installation." You can automatically install the Weblogic Server and configure the necessary domain using the EDQP console mode installer (recommended) or you can install it.

To download the installer from the Oracle Technology Network:

1. Enter the Oracle Technology Network WebLogic Server Installers URL in a web browser:
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html

2. Click OTN License Agreement and read the license agreement.

3. Select the Accept License option. You must accept the license agreement before you can download the installer.

4. Scroll down to the Oracle WebLogic Server Previous Releases section of the page, expand the Oracle WebLogic Server 10.3.6 files by clicking the plus sign adjacent to See all files.

5. Locate the Oracle WebLogic Server 11gR1 (10.3.6) + Coherence - Package Installer and click the File1 link under the Generic file.
The generic installer file, wls1036_generic.jar, must be downloaded because it contains the installers for all supported operating systems.

6. If prompted, sign into the Oracle Technology Network.

7. Browse to the EDQP install directory and click Save to start the file download:
On Linux and UNIX: /opt/edqp_install/edqp/Disk1

On Windows: C:\edqp_install\edqp\Disk1

This is the default location for wls1036_generic.jar file for the EDQP installers so that it can be used to install the WebLogic Server. You can download the file into a different directory and specify this directory during the installation.

Note:
Installing in console allows you to choose to automatically install WebLogic Sever and the domain necessary for EDQP to operate; to use the graphical mode installation, you must install and configure WebLogic and the EDQP domain.

2.3.5 Determining the Type of Database Your Oracle DataLens Administration Server Will Use

The Derby database that is installed with your Oracle DataLens Administration Server contains all of the operational information for the server, such as jobs, users, tasks, DSAs, data lenses, FTP and database connections, and other configuration information. Derby is supported only in a development environment; Derby is not supported for production.

If you plan to install the EDQP server in a production environment, you should change the Derby database to another supported database (see Section 2.3.1, "Hardware and Software Requirements"), such as an Oracle Database to create a production environment with optimal system performance and maximum system security of your Oracle DataLens Administration Server. Oracle recommends that you make this change immediately after installation if the server is going to be used in a production environment. If you do not change the database immediately after installation, you will need to reestablish all configuration settings and assets (data lenses and DSAs) in the new database on your Oracle DataLens Administration Server. You will then need to redeploy all assets to all Oracle DataLens Transform Servers in your topology.

In addition, any database that want to interact with your Oracle DataLens Administration Server must have a JDBC database driver configured on the server so that you can create a database connection. Oracle provides WebLogic-branded versions of DataDirect drivers for DB2 and MySQL Server though they are not configured for use in the classpath. For information about configuring databases besides Derby and Oracle Database, see Appendix B, "Known Issues."

2.4 Selecting Directories for Installation

During the installation process, you must specify locations for the following home directories:

- Oracle JDK

- Oracle Fusion Middleware

- WebLogic Server

The following illustration shows the default Middleware home and the Middleware products directory structure post-installation. In this case, both EDQP and WebLogic Server are installed.

Additional directories and files are also located in the Middleware home directory, as described in Table 2-1. The user_projects directory is not present until the first WebLogic domain is created.

2.4.1 Choosing a Middleware Home Directory

When the WebLogic Server is being installed, you are prompted to specify a Middleware home directory. This directory serves as a repository for common files that are used by multiple Fusion Middleware products installed on the same machine. For this reason, the Middleware home directory can be considered a central support directory for all the Fusion Middleware products installed on your system.

The files in the Middleware home directory are essential to ensuring that WebLogic Server operates correctly on your system. They facilitate checking of cross-product dependencies during installation.

When you are installing EDQP, you are prompted to choose an existing Middleware home directory or specify a path to create a new Middleware home directory. If you choose to create a new directory, the installation program automatically creates it for you.

The Middleware home directory is referenced as MW_HOME in Fusion Middleware documentation and this guide.

Middleware Home Considerations

Consider the following information when creating the Middleware home directory and installing Fusion Middleware products:

- Do not include spaces in the name of your Middleware home directory. If the name of this directory contains spaces, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of a WebLogic Server product in a single Middleware home directory. If you need to maintain separate versions of WebLogic Server on the same machine, each version must be in its own Middleware home directory.
For example, you can install only one instance of the current version of WebLogic Server in a Middleware home directory, but you can have an earlier version of WebLogic Server in a separate Middleware home directory.

- If the home directory is not empty and it does not contain registry.xml, or if any of the product installation directories are not empty, one of the following messages is displayed:

- For home directory selection task—Middleware home directory is not empty. Proceed with installation?

- For product installation directory selection task—One or more installation directories are not empty. Proceed with installation?

Functions of the Home Directory

The directories in the Middleware home directory vary depending on the installer that you are using and the products you selected for installation.

For example, the EDQP installer creates the directories and files listed in the following table.

Table 2-1 Directory Description for Middleware Home

Directory or file

Description

edqp_template1

This is the EDQP home directory.

logs

This directory contains a history file, which has information about installation and uninstallation for the Middleware home directory.

modules

This directory contains the modules installed in the home directory.

oracle_common

This directory contains directories common to all Fusion Middle ware products, such as OUI.

patch_wls1036

The WebLogic Server 10.3.6 patch directory containing the patch necessary to EDQP.

user_projects

Once you create WebLogic domains and applications, this directory is created to store them. This directory contains applications and domains sub-directories. The applications directory contains a sub-directory for each application you create, and the domains directory contains a sub-directory for each domain you create.

utils

This directory contains utilities that are used to support the installation of all products installed in this home directory. For more information on installing patches and patch sets, see Oracle Smart Update Installing Patches and Maintenance Packs.

wlserver_10.3

The WebLogic Server home directory.

.home

This file contains the information about the Middleware home directory.

ocm.rsp

This response file contains information about the Oracle Configuration Manager (OCM) installation.

registry.xml

This registry file contains a persistent record of all WebLogic products installed on the target system. This registry contains product-related information, such as version number, patch set level, patch level, and location of the product installation directories. It also contains the name of the installed JDK(s) and the Java home.

Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed WebLogic products, or result in installation problems when future products or maintenance upgrades are installed.

registry.dat

This is an encrypted version of the registry.xml file.

domain-registry.xml

This registry file contains the location of all domains currently registered with this WebLogic Server installation. Whenever you add a new domain, it is registered in this file.

2.4.2 Choosing Product Installation Directories

During the installation, you will be prompted to enter the home directories for the following products:

- EDQP
The EDQP home directory contains all the components necessary to the product, including the Developers Toolkit that includes APIs and Command Line Interface, the Endeca Connector, and the Oracle Fusion and R12 Product Information Management (PIM) installation files. The default installation directory for EDQP is:

On Linux and UNIX: /opt/Oracle/Middleware/edqp_template1

On Windows: C:\Oracle\Middleware\edqp_template1

This directory path is referenced as the EDQP_HOME directory in this document.

- WebLogic Server
The default installation directory for WebLogic Server 10.3.6 is:

On Linux and UNIX: /opt/Oracle/Middleware/wls_server_10.3

On Windows: C:\Oracle\Middleware\wls_server_10.3

This directory path is referenced as the WL_HOME directory in this document.

- JDK
You must locate the directory into which you installed the JDK/JRE. For example, the directories may be:

On Linux and UNIX: /opt/jdk1.6.0_30

On Windows: C:\Program Files\Java\jdk1.6.0_30

2.5 Choosing the Type of Installation

You can run the installation program in the following modes:

- Console mode
Console mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system. For information about using this method, see Chapter 3, "Running the Installation Program in Console Mode."

When performing a console mode installation, the installation program provides two types of installations:

- In a full installation, all EDQP components are installed including the WebLogic Server. Each full installation results in a separate WebLogic Server instance. When installing an Oracle DataLens Administration Server and a Transform Server, separate WebLogic Server instances are created for each and the login credentials are not shared across the two servers.

- In a dls (datalens server) installation, only the EDQP components are installed. You must have WebLogic Server installed and operating so that the EDQP domain can be configured.

Note:
Console mode installation is recommend for all installations.

- Graphical mode
Graphical-mode installation is an interactive, GUI-based method for installing your software and requires additional manual configuration thus it is not the recommended installation mode. It can be run on all supported platforms. For installation procedures, see "Oracle DataLens Server Graphical Installation".

In either mode, a sample domain is preconfigured to use the Derby database are created only for the installed components. Derby is supported only in a development environment. Derby is not supported for production

3 Running the Installation Program in Console Mode

This chapter describes how to run the EDQP installer in console mode in different operating system environments.

This chapter contains the following sections:

- Section 3.1, "Starting the Installation Program in Console Mode"

- Section 3.2, "Installing EDQP in Console Mode"

- Section 3.3, "Verifying the Installation"

- Section 3.4, "Performing Post-Installation Steps"

- Section 3.5, "Uninstalling Your Software in Console Mode"

3.1 Starting the Installation Program in Console Mode

This section describes how to start the installation program in console mode in different environments. It contains the following sections:

- Section 3.1.1, "Starting Installation Programs in Console Mode on Linux and UNIX"

- Section 3.1.2, "Starting the Installation Program in Console Mode on Windows"

3.1.1 Starting Installation Programs in Console Mode on Linux and UNIX

Note:
When installing EDQP on a UNIX or Linux operating system, do not run the installation program as the root user.

To start the installation program in console mode on a Linux or UNIX system using a .sh installation file, follow these steps:

1. Log in to the target system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Go to the installation directory, /opt/edqp_install/edqp/Disk1.

Note:
Ensure that all files in the directory have executable permissions for the user you logged in with before continuing.

3. Start the installation by entering the following command:
./file_name.sh

file_name.sh is the name of your installation program; for Linux it is dlsinstall_linux.sh, for Solaris it is dlsinstall_solaris.sh.

***************************************************************************
*
Welcome to the Oracle Enterprise Data Quality for Products 11.1.1.6 Installation
.
Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
***************************************************************************
*
Please Enter the location of the JDK directory: (/opt/jdk1.6.0_30)

The installation program begins to install the software. Proceed to Section 3.2, "Installing EDQP in Console Mode," to continue.

3.1.2 Starting the Installation Program in Console Mode on Windows

To start the installation program in console mode on a Windows platform, follow these steps:

1. Log in to the target Windows system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Locate the MS-DOS Command Prompt (cmd.exe), right-click on it, and then select Run as administrator.

3. Go to the installation directory C:\edqp_install\edqp\Disk1.

4. Start the installation by entering the following command:
dlsinstall_windows.bat.

***************************************************************************
*
Welcome to the Oracle Enterprise Data Quality for Products 11.1.1.6 Installation
.
Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
***************************************************************************
*
Please Enter the location of the JDK directory: (C:\Program Files\Java\jdk1.6.0_30)

The installation program begins to install the software. Proceed to Section 3.2, "Installing EDQP in Console Mode," to continue.

3.2 Installing EDQP in Console Mode

After starting the installation program, follow these steps to complete the installation:

1. At the JDK directory prompt, press Enter to use the displayed default JDK directory location or enter the directory you installed your JDK in.

Will this be a full installation ( including the WebLogic Server)? [Y/N]: (Y)

2. Enter Y if you want to install EDQP and WebLogic Server or N to install EDQP only. You should only answer N if you have already installed WebLogic Server.
On Linux and UNIX:

Please enter the path to the Weblogic installation jar file: ( /opt/edqp_install/edqp/Disk1/wls1036_generic.jar)

On Windows:

Please enter the path to the Weblogic installation jar file: ( Please enter the path to the WLS installation Jar file:  (C:\edqp_install\edqp\Disk1\wls1036_generic.jar)

3. Press Enter to use the displayed default installation directory location or enter the full path of the directory you copied the wls1036_generic.jar file into (for example, /scratch/installs/wls1036_generic.jar.)
The default installation directories that this file may be in are:

On Linux and UNIX: /opt/edqp_install/edqp/Disk1

On Windows: C:\edqp_install\edqp\Disk1

See Section 2.3.4, "Downloading the WebLogic Server Installer From Oracle E-Delivery".

On Linux and UNIX:

Please enter the location for the new WLS Middleware home directory: (/opt/Oracle/Middleware)

On Windows:

Please enter the location for the new WLS Middleware home directory: (C:\Oracle\Middleware)

4. Enter the Middleware home directory that will serve as the central support directory for all Fusion Middleware products (including WebLogic Server) installed on the target system. See Section 2.4, "Selecting Directories for Installation".
If you specify a directory that does not exist, the installation program creates it for you.

Please enter the name of the new WLS Administrator: (dlsadmin)

5. Press Enter to use the recommended WebLogic domain administrator name, dlsadmin, or enter a name and press Enter. See Section 2.3.2, "Establishing the Required User Accounts".

Please enter a password for the new WLS Administrator (dlsadmin1)

6. Press Enter to use the recommended WebLogic domain administrator password, dlsadmin1, or enter a password and press Enter. The password must be at least eight characters.

Will this be an EDQP Admin Server or EDQP Transform Server Installation?[A/T] (A)

7. Specify the type of server you want to install, an A for Administration Server or T for a Transform Server, and press Enter.
The following additional steps occur when you are installing a Transform Server:

This Transform server should be added to a server group in the server topology before continuing with the install.
Continue with the installation? [Y/N]: (Y)

1. Ensure that you have added the Transform Server you want to install to a server group so that communication between it and an Administration Server can be established during installation. See Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.

2. Enter Y and press Enter to continue the installation.

The EDQP Transform Server needs to communicate with the datasource on the EDQP Admin Server.
Please enter the hostname of the Admin Server: (myexample.com)

3. Enter the fully qualified host name or the IP of the Oracle DataLens Administration Server that this Transform Server will communicate with.

Please enter the port number to use for the new WLS domain:  (2229)

8. Press Enter to use the default port, 2229, or enter the port number for your Oracle DataLens Server to listen and press Enter. The port must be between 1024 and 65536.
On Linux and UNIX:

The Max Heap space should be set to a max of 80% of the physical memory
Please enter the maxheap size (in Mb):

On Windows:

The Max Heap space should be set to a max of 80% of the physical memory (6494)
Please enter the maxheap size (in Mb):  (2048)
The Max Heap space should be set to a max of 80% of the physical memory (12720)
Enter the desired memory allocation or to allocate the recommended 80% enter
the calculated amount. The installation will not proceed if the memory
allocation is greater than 80% (in Mb):  (2048)

For maximum performance of both the Oracle DataLens Server and the WebLogic server, you should calculate what 80% of your total physical server memory is so that it can be correctly set. When installing on Windows, this value is calculated, as in the preceding example, and should be used; no memory calculations are made on Linux or UNIX.

9. Enter the server memory calculation and press Enter or on Windows simply press Enter.
The installation begins and runs as a background process. On all platforms you must allow the installation session to continue to completion.

Note:
It is normal for the installation program to pause for a long time, especially toward the end. The installation program is still working while this occurs.

After the installation completes, the following message is displayed:

On Linux and UNIX:

You are returned to your operating system prompt once the installation completes.

On Windows:

Run the following script to start the domain.C:\Oracle\Middleware\user_projects\domains\dls_domain\bin\startWebLogic.cmd

Finished the Oracle Enterprise Data Quality for Products 11.1.1.6 Installation.(Enter to Exit)

10. Press Enter to exit the installer.

11. Start your WebLogic Server EDQP domain (the default is dls_domain) using one of the following where dls_domain is the name of your EDQP domain:
On Linux and UNIX:

cd /MW_HOME/user_projects/domains/dls_domain/bin/

nohup ./startWeblogic.sh &

On Windows:

cd \MW_HOME\user_projects\domains\dls_domain\bin\

startWeblogic.cmd

3.3 Verifying the Installation

This section describes how to verify your Oracle DataLens Server installation and is applicable to all operating systems.

Verify that the server is up and running correctly:

1. Open one of the supported web browsers for your environment.

2. Enter the following URL:
http://hostname:port/datalens

where hostname is the DNS name or IP address of the Administration Server and port is the listen port on which the Administration Server is listening for requests (port 2229 by default).

If you configured the Administration Server to use Secure Socket Layer (SSL) you must add s after http as follows:

https://hostname:port/datalens

3. When the login page appears, enter a user name and the password. This is the user name and password you specified during the installation process.
The Oracle DataLens Server web pages are displayed and default to the Welcome tab.

If your browser displays, ”The page cannot be displayed”, then the problem could be one of the following:

- The WebLogic domain has not been started.

- The Oracle DataLens Server repository was removed or corrupted.

4. Click the Administration tab.

5. Ensure that the Oracle DataLens Server configuration parameters on the Oracle DataLens Administration Server home page are correct. The JSP Server indicates the version of WebLogic Server that is installed.

6. (Optional) From the Admin Dashboard panel, click Admin Log and review the Administration Server log file to verify that the server started with no errors.
If no server startup errors have been recorded, then the Oracle DataLens Administration Server installation was successful. For more information about the Oracle DataLens Administration web page, see the Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.

Note:
Any known installation issues are detailed in "Known Issues".

3.4 Performing Post-Installation Steps

This section describes the post-installation steps necessary to completing your EDQP installation.

To avoid any issues with long running processing jobs or checking in large packages, the following post-installation steps must be performed to modify the WebLogic Server environment settings.

1. Ensure that your WebLogic Server is running on your Oracle DataLens Administration Server.

2. Open a supported web browser and enter the following URL:
http://hostname:port/console

where hostname is the DNS name or IP address of the Oracle DataLens Administration Server and port is the listen port on which the server is listening for requests (port 2229 by default).

If you configured the Oracle DataLens Administration Server to use Secure Socket Layer (SSL) you must add s after http as follows:

https://hostname:port/console

3. When the login page appears, enter the user name and the password you used to start the server, and then click Login.
Your WebLogic Administration Console log in web page is displayed.

4. In the Domain Structure panel for your EDQP domain (dls_domain is the default), click Deployments.

5. In the Deployments table, click the oracle-edqp link, and then click the Configuration tab.

6. Enter 3600 in the Session Timeout (in seconds) field, and then click Save.

7. Click OK to save this change to the deployment plane.

8. If you are running EDQP in an integrated Fusion PIM environment with EDQP hosted in a Fusion WebLogic Server domain continue to step12; do not perform these post-installation steps. The domain thread timeout parameters are optimized by the Fusion PIM installation and configuration.
For all other environments, in the Domain Structure panel for your EDQP domain (dls_domain is the default), expand Environment then click Servers.

9. Click the AdminServer(admin) Server Name link to open the settings for the EDQP domain.

10. Select the Tuning tab. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/tuning/TuningExecuteThreads.html

11. Enter 3600 in the Stuck Thread Max Time field, and then click Save.

12. Stop your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

13. Start your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

14. (Optional) Log out of your WebLogic Administration Console.

15. Ensure that you have configured a network shared disk space that all of your Oracle DataLens Servers, both Administration and Transform, can access. Your input text data files to the data quality process should be stored in this shared disk space and be referenced by all servers. You should configure your DSAs to store results files in this same space.

3.5 Uninstalling Your Software in Console Mode

The following sections describe how to uninstall your software or individual components on Linux, Windows, and UNIX systems.

The uninstall program does not remove the home directory associated with the installation, the JDK, or any user-created WebLogic domains. Only the components that were installed by the installation program are removed.

Use the following procedure to uninstall the complete product installation using the command-line interface:

1. Shut down any servers that are running, both Oracle DataLens Servers and WebLogic Servers.

2. Start the uninstall program as described in Table 3-1.

Table 3-1 Starting the Uninstall Program in Console Mode

Platform

Procedure

Linux and UNIX

1. Go to the following directory:
EDQP_HOME/oui/bin/

where EDQP_HOME represents the home directory in which you installed Enterprise DQ for Product.

2. At the prompt, enter the following command:

./runInstaller -deinstall

3. Remove the .MW_HOME/user_projects/domains/dls_domain
where MW_HOME represents the Middleware home directory in which you installed WebLogic Server.

Windows

1. Open a command window and go to the following directory:
EDQP_HOME\oui\bin

where EDQP_HOME represents the home directory in which you installed Enterprise DQ for Product.

2. Enter the following command at the prompt:

setup.exe -deinstall

3. Restart your system to clean the registry and delete the EDQP_HOME\ directory.

4. Delete the .MW_HOME\user_projects\domains\dls_domain
where MW_HOME represents the Middleware home directory in which you installed WebLogic Server.

4 Changing the Default Oracle DataLens Server Database

This chapter describes how to prepare for and change the default configuration database that holds EDQP metadata in the supported operating system environments.

The Derby database that is installed with your Oracle DataLens Administration Server contains all of the operational information for the server, such as jobs, users, tasks, DSAs, data lenses, FTP and database connections, and other configuration information. Derby is supported only in a development environment; Derby is not supported for production.

If you plan to install the EDQP server in a production environment, you should change the Derby database to another supported database (see Section 2.3.1, "Hardware and Software Requirements"), such as an Oracle Database to create a production environment with optimal system performance and maximum system security of your Oracle DataLens Administration Server. Oracle recommends that you make this change immediately after installation if the server is going to be used in a production environment.

If you do not change the database immediately after installation, you will need to reestablish all configuration settings and assets (data lenses and DSAs) in the new database on your Oracle DataLens Administration Server. You will then need to redeploy all assets to all Oracle DataLens Transform Servers in your topology.

You must compete the following sections of this chapter to totally change the Derby database to another supported database:

- Section 4.1, "Preparing to Change the Default Oracle DataLens Server Derby Database"

- Section 4.2, "Changing the Derby Database to an Oracle DataBase or PostgreSQL Database"

- Section 4.3, "Configuring the EDQP WebLogic Server Domain to Use the PDQRespository Data Source"

- Section 4.4, "Autodeploying Data Lenses to the New Database"

4.1 Preparing to Change the Default Oracle DataLens Server Derby Database

You must ensure that the following requirements are observed:

- Ensure that one of the following supported database products is installed on your Oracle DataLens Administration Server.

Oracle Database

You can obtain Oracle Database from the Oracle Technology Network at

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

PostgreSQL Database

You can obtain PostgreSQL Version 9.2.x from the PostgreSQL website at

http://www.postgresql.org/

You must obtain the associated JAR file, postgresql-9.2-1002.jdbc4.jar, from the PostgreSQL JDBC Driver website at

http://jdbc.postgresql.org/download.html

Install and configure this driver as described in "Configuring JDBC Database Drivers."

Note:
Previous versions of PostgreSQL are not supported including the associated JAR files.

- Source your installed database environment for your administrator user.

- Ensure that your database is configured to use UTF-8 encoding if you want to store non-Latin characters.

Caution:
If your database is not configured as UTF-8, then some characters may not be rendered correctly due to encoding differences.

4.2 Changing the Derby Database to an Oracle DataBase or PostgreSQL Database

Use one of the following sections to change your Oracle DataLens Administration Server Derby Database to an Oracle Database or PostgreSQL Database on any of the supported operating systems:

Note:
In the sample console text and directory path names provided in this section, Linux/UNIX conventions (such as forward slashes in path names) are used, for example, /MW_HOME. When entering path names on a Windows system, be sure to use Windows conventions. For example, use backslashes in path names, such as C:\MW_HOME.

Note:
The following database schema creations only require that a DBA use a specific database administration user with sufficient privileges and run the associated data definition language (DDL) provided by EDQP to create the new schema on the targeted production database. The following sections are examples of how to create the schema on an existing database that resides on your Oracle DataLens Administration Server.

4.2.1 Creating the Oracle Database PDQRespository Schema

1. Login to your Oracle database server using the Oracle user account. Consult your database administrator if you need assistance adding and modifying user accounts.
For Windows systems, open a command window with cmd.exe.

2. Enter sqlplus /nolog to start SQL*Plus.

3. Enter the following commands at the SQL> prompt to create the dlsadmin user and grant the necessary privileges:
SQL> CONNECT / AS SYSDBA

SQL> CREATE USER dlsadmin INDENTIFIED BY dlsadmin1;

SQL> ALTER USER dlsadmin QUOTA UNLIMITED ON USERS;

SQL> GRANT CONNECT, CREATE TABLE, CREATE SEQUENCE TO dlsadmin;

SQL> EXIT;

4. Change directories to the /MW_HOME/user_projects/domains/dls_domain/opdq/data/repository/ddl_scripts directory.

5. Enter sqlplus dlsadmin/dlsadmin1 to log into SQL*Plus.

Note:
Messages similar to the following appear when the dlsadmin user cannot connect to SQL*Plus:

Error accessing PRODUCT_USER_PROFILE
Warning:  Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM

Enter the following commands to correct this issue:

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> @$ORACLE_HOME/sqlplus/admin/PUPBLD.SQL

SQL> EXIT;

sqlplus dlsadmin/dlsadmin1

6. Enter the following commands at the SQL> prompt:
@repository_oracle_ddl.sql

exit;

4.2.2 Creating the PostgreSQL Database PDQRespository Schema

1. Login to your PostgreSQL database server using the database superuser (postgres) account. Consult your database administrator if you need assistance adding and modifying user accounts.

2. Start PostgreSQL using one of the following:
On Linux and UNIX, enter /var/lib/postgres -D pgsql/data & to start PostgreSQL.

On Windows servers, start the PostgreSQL SQL Shell (psql) by clicking Start, selecting All Programs, then selecting PostgreSQL 9.x, and then select SQL Shell (psql). Enter the server, database, and database superuser credentials.

3. Edit the pg_hba.conf file, located in the data directory of your PostgreSQL installation, to ensure that the database you will create can connect on the network:
On Linux and UNIX, ensure that the method is set to password and the host scsdata scs line is updated with your IP address and subnet mask as in the following:

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# "local" is for Unix domain socket connections only
local all all password
# IPv4 local connections:
host all all 127.0.0.1/32 password

#Line is added so that it gets connected to admin server;
host scsdata scs <network_ip_address/subnet_mask> trust

# IPv6 local connections:
host all all ::1/128 password

On Windows, ensure that the method is set to md5 and the host scsdata scs line is updated with your IP address and subnet mask as in the following:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5

#Line is added so that it gets connected to admin server;
host    scsdata          scs   <network_ip_address/subnet_mask> trust

# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

4. On Linux and UNIX, edit the postgresql.conf and ensure that the host and connection information matches your edits in the pg_hba.conf file in the previous step.

5. Restart PostgreSQL:
On Linux and UNIX, enter /etc/init.d/postgresql restart.

On Windows, enter C:\Windows\system32\cscript.exe //NoLogo "C:\Program Files\PostgreSQL\9.2\scripts\serverctl.vbs" reload wait.

6. Enter the following commands at the postgres=> prompt to create the scs user and grant the necessary privileges for the appropriate database:
postgres=> CREATE USER SCS WITH PASSWORD '1REALM1';

postgres=> CREATE DATABASE SCSDATA OWNER=SCS;

postgres=> GRANT ALL PRIVILEGES ON DATABASE SCSDATA TO SCS;

postgres=> \q

7. Restart PostgreSQL specifying use of the scsdata database:
On Linux and UNIX, enter psql -d scsdata -U scs –W.

On Windows, start the PostgreSQL SQL Shell (psql) by clicking Start, selecting All Programs, then selecting PostgreSQL 9.x, and then select SQL Shell (psql). Enter the server, scsdata as the database, scs as the user, and 1REALM1 for the password.

8. Enter one of the following commands at the scsdata=> prompt to create the required objects:
On Linux and UNIX:

scsdata=> \i /MW_HOME/user_projects/domains/dls_domain/opdq/data/repository/ddl_scripts/repository_postgres_ddl.sql

On Windows:

scsdata-> #\i '\\ML_HOME\\user_projects\\domains\\dls_domain\\opdq\\data\\repository\\ddl_scripts\\repository_postgres_ddl.sql'

Note:
Ensure that your ML_HOME directory path includes double backslashes as in the rest of the command. For example, C:\\oracle\\middleware.

9. Verify that you can list the tables in the database, which verifies that the server and database can be accessed:
scsdata=> \dt

scsdata=> \q

10. Edit the following file:
On Linux and UNIX, edit the /WL_HOME/common/bin/commEnv.sh file and add ${CLASSPATHSEP}${WL_HOME}/server/lib/postgresql-9.1-902.jdbc4.jar to the end of the WEBLOGIC_CLASSPATH variable.

On Windows, edit the /WL_HOME\common\bin\commEnv.cmd file and add ;%WL_HOME%\server\lib\postgresql-9.2-1002.jdbc4.jar to the end of the WEBLOGIC_CLASSPATH variable.

For more information about configuring the database driver, see "Configuring JDBC Database Drivers."

11. Restart your WebLogic Server to implement these changes. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

4.3 Configuring the EDQP WebLogic Server Domain to Use the PDQRespository Data Source

The PDQRespository data source must be configured for each server in your EDQP topology so you must run the following steps for each of your Oracle DataLens Servers.

1. Ensure that your WebLogic Server is running on your Oracle DataLens Administration Server.

2. Open a supported web browser and enter the following URL:
http://hostname:port/console

where hostname is the DNS name or IP address of the Oracle DataLens Administration Server and port is the listen port on which the server is listening for requests (port 2229 by default).

If you configured the Oracle DataLens Administration Server to use Secure Socket Layer (SSL) you must add s after http as follows:

https://hostname:port/console

3. When the login page appears, enter the user name and the password you used to start the server, and then click Login.

4. Delete the PDQRepository JDBC data source. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/jdbc_datasources/DeleteDataSources.html

5. A new PDQRepository data source that configures the new database connectivity is necessary. Adding a new JDBC Generic data source is simple using the corresponding multi-page process.
Review this process before beginning in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/jdbc_datasources/CreateDataSources.html

Complete the Create a New JDBC Data Source pages as follows:

No.

Screen

Perform the Following Action

1

JDBC Data Source Properties

Enter PDQRepository in the Name and JNDI name fields.
For an Oracle Database—Select Oracle from the Database Type list.

For a PostgreSQL Database—Select PostgreSQL from the Database Type list.

Click Next.

2

JDBC Data Source Properties

For an Oracle Database—Select Oracle's Driver (Thin XA) for Instance connections; Versions:9.0.1 and later from the Database Driver list.
For a PostgreSQL Database—Select PostgreSQL's Driver (Type 4)Versions;Any from the Database Driver list.

Click Next.

3

Transaction Properties

Click Next.

4

Connection Properties

For an Oracle Database:
Enter the name of the Oracle Database instance (SID) where the dlsadmin user account was created in the Database Name: field.

Enter the host name of your Oracle Database Server in the Host Name: field.

Enter port number of your Oracle Database in the Port: field.

Enter dlsadmin in the Database User Name field.

Enter and confirm dlsadmin1 in the password fields.

Click Next.

For a PostgreSQL Database:

Enter the scsdata in the Database Name: field.

Enter the host name of your PostgreSQL Database Server in the Host Name: field.

Enter port number of your PostgreSQL Database in the Port: field.

Enter scs in the Database User Name field.

Enter and confirm 1REALM1 in the password fields.

Click Next.

5

Test Database Connection

Click Test Configuration to ensure that your database connection operates correctly. Make any necessary changes until the connection is successful.
Click Next.

6

Select Targets

Select the AdminServer check box to deploy the new data source on that server.
Click Finish.

6. Navigate to the new PDQRepository data source. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/NavigateToJdbcSystemResource.html

7. Select the Row Prefetch Enabled check box, and click Save.

8. Stop your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

9. Modify the setDomainEnv file on your Oracle DataLens Administration Server only to set the Derby database parameter to false:

Note:
This step is not applicable to Oracle DataLens Transform Servers because the Derby database parameter is set to false during installation.

Platform

Actions

Linux and UNIX

1. Edit the /MW_HOME/user_projects/domains/dls_domain/bin/setDomainEnv.sh file.

2. Search for the first instance of DERBY_FLAG as follows:

DERBY_FLAG="true"
export DERBY_FLAG

enableHotswapFlag=""
export enableHotswapFlag

PRODUCTION_MODE=""
export PRODUCTION_MOD

There are several instances of this flag in the file and you must ensure that you modify only this one.

3. Change "true" to "false":

DERBY_FLAG="false"

4. Save and close the file.

Windows

1. Edit the \MW_HOME\user_projects\domains\dls_domain\bin\setDomainEnv.cmd file.

2. Search for the first instance of DERBY_FLAG.

set DERBY_FLAG=true

set enableHotswapFlag=

set PRODUCTION_MODE=

There are several instances of this flag in the file and you must ensure that you modify only this one.

3. Change true to false (without quotes)

set DERBY_FLAG=false

4. Save and close the file.

10. Rename the /EDQP_HOME/config/ServerProfiles.xml.bak file to /EDQP_HOME/config/ServerProfiles.xml.

11. Start your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

4.4 Autodeploying Data Lenses to the New Database

The EDQP Smart Glossaries delivered with EDQP are automatically deployed (autodeployed) to the standard Derby database so when you change to a new database you must autodeploy these assets for use in that database.

To autodeploy the EDQP Smart Glossaries:

1. On your Oracle DataLens Administration Server system, log in using the administrator user you established when installing the server in preparation to copy the necessary files.

Note:
This step does not refer to the Oracle DataLens Administration Server web page.

2. Copy the MW_HOME\edqp_template1\autodeploy\lens directory that you extracted from the product package to the WebLogic dls_domain directory on your Oracle DataLens Administration Server. By default, these directories are:
On Linux and UNIX: MW_HOME/user_projects/domains/dls_domain/opdq/autodeploy/lens

On Windows: MW_HOME\user_projects\domains\dls_domain\opdq\autodeploy\lens

See Section 2.4, "Selecting Directories for Installation".

This autodeploys the EDQP Smart Glossaries to your Oracle DataLens Server. The Oracle DataLens Administration Server polls the autodeploy directory every 10 minutes and attempts to autodeploy the data lens template files that are placed in the respective folders under the autodeploy parent folder.

3. Log out of the Oracle DataLens Administration Server system.

4. Wait 10 minutes to ensure that the server templates have been autodeployed.

5. Log into the Oracle DataLens Server Administration web page.
For more information about these web pages, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.

6. Verify that the DSAs and data lens contained in the MW_HOME\edqp_template1\autodeploy\ directory have been autodeployed.

A Oracle DataLens Server Graphical Installation

This chapter describes how to start the installation program in graphical mode in the supported environments and all of the required manually post-configuration steps. It also describes the sequence of screens that appear in the installation and post-configuration processes.

This chapter contains the following sections:

- Section A.1, "Graphical Mode Installation"

- Section A.2, "Post-Installation Configuration"

Note:
Your 64-bit JDK must be installed in a directory that does not contain spaces otherwise the OUI install script will fail. See Section 2.3.3, "Installing the Java Development Kit."

Note:
In order to run the installation program in graphical mode, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for Linux and UNIX systems do. Your display must support 256 colors and the DISPLAY variable must be set.

A.1 Graphical Mode Installation

This section contains the following:

- Section A.1.1, "Starting the Installation Program in Graphical Mode on Linux and UNIX"

- Section A.1.2, "Starting the Installation Program in Graphical Mode on Windows"

- Section A.1.3, "Installation Screen Responses"

- Section A.1.4, "Installation Screens"

A.1.1 Starting the Installation Program in Graphical Mode on Linux and UNIX

To start the installation program in graphical mode on Linux and UNIX platforms, follow these steps:

1. Log in to the target Linux or UNIX system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Ensure that the supported WebLogic Server is installed.If you chose a Custom installation rather than Typical, you must ensure that you select the Evaluation Database option. See Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/wls.htm

3. You must install the following WebLogic Server patch, using Oracle Smart Update, to ensure the proper operation:

- Patch 9923849: SU Patch [7BWI]: Enable JPA2.0 support on Weblogic server. (9923849_1036_Generic.zip) found at My Oracle Support Patches and Updates Web site at
https://support.oracle.com/epmos/faces/PatchResultsNDetails?_adf.ctrl-state=d6g7a11q2_4&releaseId=8191036000&requestId=14192858&patchId=9923849&languageId=0&platformId=2000&_afrLoop=1075004471937562

The patch For details about how to use Oracle Smart Update, see Oracle Smart Update Installing Patches and Maintenance Packs Release 3.2.1.

4. Change directories to the directory that contains the installation program.

5. Start the installation by entering the following commands:
chmod a+x runInstaller

./runInstaller -jreLoc JDK_directory

where JDK_directory is the absolute path to your Oracle JDK installation.

The installation program begins to install the software.

Go to Section A.1.3, "Installation Screen Responses" to complete of each installation program screen.

A.1.2 Starting the Installation Program in Graphical Mode on Windows

To start the installation program in graphical mode on Windows, follow these steps:

1. Log in to the target Windows system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Ensure that the supported WebLogic Server is installed.If you chose a Custom installation rather than Typical, you must ensure that you select the Evaluation Database option. See Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server11g Release 1 (10.3.6).

3. You must install the following WebLogic Server patch, using Oracle Smart Update, to ensure the proper operation:

- Patch 9923849: SU Patch [7BWI]: Enable JPA2.0 support on Weblogic server. (9923849_1036_Generic.zip) found at My Oracle Support Patches and Updates Web site at
https://support.oracle.com/epmos/faces/PatchResultsNDetails?_adf.ctrl-state=d6g7a11q2_4&releaseId=8191036000&requestId=14192858&patchId=9923849&languageId=0&platformId=2000&_afrLoop=1075004471937562

The patch For details about how to use Oracle Smart Update, see Oracle Smart Update Installing Patches and Maintenance Packs Release 3.2.1.

4. Locate the MS-DOS Command Prompt (cmd.exe), right-click on it, and then select Run as administrator.

5. Go to the installation directory C:\edqp_install\edqp\Disk1.

6. Enter setup.exe -jreLoc JDK_directory
where JDK_directory is the absolute path to your Oracle JDK installation.

The installation program begins to install the software.

Go to Section A.1.3, "Installation Screen Responses" to complete of each installation program screen.

A.1.3 Installation Screen Responses

The installation program displays a series of screens, in the order listed in Table A-1. Some screens are displayed only in certain situations, as noted in the table.

If you need additional help with any of the installation screens, see Appendix A, "Installation Screens," or click the link in the Screen column of the following table.

Table A-1 Running the Installation Program in Graphical Mode

No.

Screen

When Does This Screen Appear?

Perform the Following Action

1

Welcome

Always

Click Next to proceed with the installation.

You may cancel the installation at any time by clicking Exit.

2

My Oracle Support Update

Always

Specify whether you want to register the product installation with My Oracle Support. By registering, Oracle Support notifies you immediately of any security updates that are specific to your installation.

If you chose not to register, an Are You Sure? dialog box appears. Click Yes to continue.

Click Next to continue.

3

Prerequisite Checks

Always

Click Next to continue.

4

Installation Location

Always

Specify the Middleware home directory that will serve as the central support directory for all Fusion Middleware products installed on the target system, including EDQP and WebLogic Server.

Specify the home directory for theEDQP where the product will be installed and used.

Click Next to continue.

5

Installation Summary

Always

Click Next to continue.

6

Installation Progress

Always

When the installation program progress has reached 100%, click Next to continue.

7

Installation Complete

Always

Click Finish to exit the installation program.

A.1.4 Installation Screens

This appendix contains screenshots and descriptions for all of the EDQP installation screens.

A.1.4.1 Welcome

The Welcome screen is displayed each time you start the installer.

A.1.4.2 My Oracle Support Update

Specify whether you want to register the Oracle WebLogic Server installation with My Oracle Support. By registering, Oracle Support notifies you immediately of any security updates that are specific to your installation.

If you want to register your installation, enter your My Oracle Support email address and your My Oracle Support password.

If you want to decline registration, deselect the I wish to receive security updates via My Oracle Support check box. An Are You Sure? dialog box appears. Click Yes to continue.

Notes:
If you are using a Generic installer (JAR file) to install WebLogic Server, and $JAVA_HOME points to a JDK that is later than JDK 1.60_05, you cannot deselect the I wish to receive security updates via My Oracle Support check box. In this case, if you do not want to install security updates:

1. Leave the Email and Support Password fields blank, and click Next. An Email Address Not Specified dialog box appears.

2. Click Yes. An Are You Sure? dialog box appears.

3. Click Yes to continue with the installation.

If a Connection Failed dialog box appears when you bypass security updates, select the I wish to remain uninformed of security updates check box and click Continue to continue the installation.

If you have not registered with Oracle Support, go to the My Oracle Support web site, https://support.oracle.com/CSP/ui/flash.html, and register to obtain a My Oracle Support account.

For more information about the benefits of registering your installation with My Oracle Support, see Oracle Configuration Manager Installation and Administration Guide.

A.1.4.3 Prerequisite Checks

This screen displays a tree view of the operating system and physical memory checks and the status for each.

A.1.4.4 Installation Location

Specify the Middleware home directory that all Fusion Middleware products are installed on the target system; EDQP and WebLogic Server will be installed in this directory. You must already have a Middleware home directory on your system. See Section 2.4, "Selecting Directories for Installation".

A.1.4.5 Installation Summary

This screen displays a list of directory details, disk space (required and available), and the product components to be installed.

A.1.4.6 Installation Progress

This screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete.

A.1.4.7 Installation Complete

This screen shows the results of the completed installation. You can click Save to save the displayed details to a text file.

A.2 Post-Installation Configuration

This section contains the following:

- Section A.2.1, "Starting the Post-Installation Configuration Program on Linux and UNIX"

- Section A.2.2, "Starting the Post-Installation Configuration Program in Graphical Mode on Windows"

- Section A.2.3, "Post-Installation Configuration Screen Responses"

- Section A.2.4, "Post-Installation Configuration Screens"

- Section A.2.5, "Modifying Environment Variables"

A.2.1 Starting the Post-Installation Configuration Program on Linux and UNIX

To start the post-installation WebLogic domain configuration program in graphical mode on Linux and UNIX platforms, follow these steps:

1. Log in to the target Linux or UNIX system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Change directories to MW_HOME/epdq_templates1/common/bin, which contains the configuration program.

3. Start the configuration by entering the following commands:
chmod a+x config.sh

./config.sh

The configuration program begins.

A.2.2 Starting the Post-Installation Configuration Program in Graphical Mode on Windows

To start the post-installation WebLogic domain configuration program in graphical mode on Windows, follow these steps.

1. Log in to the target Windows system as your administrator user. See Section 2.3.2, "Establishing the Required User Accounts".

2. Open a command window and go to the MW_HOME\epdq_templates1\common\bin directory, which contains the configuration program.

3. Enter config.cmd
The configuration program begins.

See Section A.2.3, "Post-Installation Configuration Screen Responses," for a description of each configuration program screen.

A.2.3 Post-Installation Configuration Screen Responses

The post-installation configuration program displays a series of screens, in the order listed in Table A-2. Some screens are displayed only in certain situations, as noted in the table.

If you need additional help with any of the installation screens, see Appendix A, "Post-Installation Configuration Screens," or click the link in the Screen column of the following table.

Table A-2 Running the Configuration Program in Graphical Mode

No.

Screen

When Does This Screen Appear?

Perform the Following Action

1

Configuration Wizard Welcome

Always

Click Next to proceed with the configuration and accept the Create a new WebLogic domain default.

You may cancel the installation at any time by clicking Exit.

2

Select Domain Source

Always

Select the correct EDQP Domain generation option for the type of server you are installing, Oracle Product Data Quality Administration Server Template -11.1.1.0 or Oracle Product Data Quality Admin_Transform Server TEMPLATE -11.1.1.0.

The Oracle Product Data Quality Transform Server TEMPLATE -11.1.1.0 template should be selected only when you are installing a Transform Server on a managed server.

The Oracle JRF - 11.1.1.0 [oracle_common] check box is automatically selected.

Click Next to continue.

3

Specify Domain Name and Location

Always

Enter dls_domain in the Domain Name field.

Enter MW_HOME/user_projects/domains.

Click Next to continue.

4

Configure Administrator User Name and Password

Always

Enter your WebLogic administration user name and password credentials.

Click Next to continue.

5

Configure Server Start Mode and JDK

Always

Ensure the Development Mode option is selected for your domain startup operation mode.

Select the 64-bit JDK that you want to use from the Available JDKs list. Oracle recommends that you use the latest 64-bit JDK.

Click Next to continue.

6

Select Optional Configuration

Always

Select the Administration Server check box.

Click Next to continue.

7

Configure the Administration Server

Always

Change the listen port if necessary to the port your Oracle DataLens Administration Server is running on. Oracle recommends that you use port 2229, which is the default port for Oracle DataLens Servers.

Click Next to continue.

8

Configuration Summary

Always

Click Create to create the domain and continue.

9

Creating Domain

Always

Click Done to exit the installation program.

A.2.4 Post-Installation Configuration Screens

This appendix contains screenshots and descriptions for all of the post- installation WebLogic domain configuration screens.

A.2.4.1 Configuration Wizard Welcome

The Welcome screen is displayed each time you start the configuration wizard.

A.2.4.2 Select Domain Source

Select the correct EDQP Domain generation option for the type of server you are installing, Oracle Product Data Quality Administration Server Template -11.1.1.0 or Oracle Product Data Quality Admin_Transform Server TEMPLATE -11.1.1.0.

The Oracle Product Data Quality Transform Server TEMPLATE -11.1.1.0 template should be selected only when you are installing a Transform Server on a managed server.

A.2.4.3 Specify Domain Name and Location

Specify your domain name and location. Oracle recommends that you use dls_domain as your domain name.

A.2.4.4 Configure Administrator User Name and Password

Specify your WebLogic administration user credentials.

A.2.4.5 Configure Server Start Mode and JDK

Select the Development Mode for your domain startup operation mode and JDK. Oracle recommends that you use the most current 64-bit JDK.

A.2.4.6 Select Optional Configuration

Select Administration Server for your server configuration type.

A.2.4.7 Configure the Administration Server

Specify your Oracle DataLens Server information. Oracle recommends that you use port 2229 for your server.

A.2.4.8 Configuration Summary

This screen displays a summary of your domain configuration selections.

A.2.4.9 Creating Domain

This screen shows you the progress of your domain creation until it completes at 100%.

A.2.5 Modifying Environment Variables

Modify the environment variables set on your Oracle DataLens Server as follows:

Table A-3 Modifying Environment Variables

Platform

Actions

Linux and UNIX

1. Edit the MW_HOME/user_projects/domains/dls_domain/bin/setDomainEnv.sh file.

2. Find the line set DERBY_FLAG="false" and set it to true as follows:

set DERBY_FLAG="true"
OPDQ_HOME="$MW_HOME/user_projects/domains/base_domain/opdq"
export OPDQ_HOME

3. Save and close the file.

4. Edit the MW_HOME/wlserver_10.3/common/derby/bin/startNetworkServer.sh file.

5. Add the following lines:

DERBY_OPTS=”-Dderby.system.home=$OPDQ_HOME/data/repository/internal  -Dderby.drda.host=0.0.0.0”
export DERBY_OPTS

6. Save and close the file.

Windows

1. Edit the MW_HOME\user_projects\domains\dls_domain\bin\setDomainEnv.cmd file.

2. Find the line set DERBY_FLAG=false and replace it with the following lines:

set DERBY_FLAG=true
set OPDQ_HOME=C:\Oracle\Middleware\user_projects\domains\dls_domain\opdq
set WEBLOGIC_CLASSPATH=%WEBLOGIC_CLASSPATH%;%WL_HOME%\server\lib\ojdbc6.jar;%WL_HOME%\server\lib\mysql-connector-java-commercial-5.1.17-bin.jar

3. Change the Java memory settings by searching for Xmx and changing the 64BIT settings to 2048, 4096, or 80% of the servers physical memory. The following lines are changed to 2048:

set XMS_SUN_64BIT=256
set XMS_SUN_32BIT=256 set XMX_SUN_64BIT=2048
set XMX_SUN_32BIT=512
set XMS_JROCKIT_64BIT=256
set XMS_JROCKIT_32BIT=256 set XMX_JROCKIT_64BIT=2048
set XMX_JROCKIT_32BIT=512
if "%JAVA_VENDOR%"=="Sun" ( set WLS_MEM_ARGS_64BIT=-Xms256m -Xmx2048m
set WLS_MEM_ARGS_32BIT=-Xms256m -Xmx512m
) else ( set WLS_MEM_ARGS_64BIT=-Xms512m -Xmx2048m
set WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
)

4. Save and close the file.

5. Edit the MW_HOME\wlserver_10.3\common\derby\bin\startNetworkServer.bat file.

6. Add the following line:

Set DERBY_OPTS=-Dderby.system.home=%OPDQ_HOME%\data\repository\internal  -Dderby.drda.host=0.0.0.0

7. Save and close the file.

A.2.6 Start Your WebLogic Server

You must start your WebLogic server to complete the installation.

Platform

Run the Command

Linux and UNIX

./MW_HOME/user_projects/domains/dls_domain/bin/startWebLogic.sh

Windows

\MW_HOME\user_projects\domains\dls_domain\bin\startWebLogic.cmd

A.2.7 Configuring the EDQP WebLogic Server Domain to Use the PDQRespository Data Source

The PDQRespository data source must be configured for each server in your EDQP topology so you must run the following steps for each of your Oracle DataLens Servers.

1. Ensure that your WebLogic Server is running on your Oracle DataLens Administration Server.

2. Open a supported web browser and enter the following URL:
http://hostname:port/console

where hostname is the DNS name or IP address of the Oracle DataLens Administration Server and port is the listen port on which the server is listening for requests (port 2229 by default).

If you configured the Oracle DataLens Administration Server to use Secure Socket Layer (SSL) you must add s after http as follows:

https://hostname:port/console

3. When the login page appears, enter the user name and the password you used to start the server, and then click Login.

4. Delete the PDQRepository JDBC data source. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/jdbc_datasources/DeleteDataSources.html

5. A new PDQRepository data source that configures the new database connectivity is necessary. Adding a new JDBC Generic data source is simple using the corresponding multi-page process.
Review this process before beginning in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/jdbc_datasources/CreateDataSources.html

Complete the Create a New JDBC Data Source pages as follows:

No.

Screen

Perform the Following Action

1

JDBC Data Source Properties

Enter PDQRepository in the Name and JNDI name fields.
Select Derby from the Database Type list.

Click Next.

2

JDBC Data Source Properties

Select Derby's Driver(Type 4 XA) Versions: Any from the Database Driver list.
Click Next.

3

Transaction Properties

Click Next.

4

Connection Properties

Enter scsdata in the Database Name: field.
Enter the host name of your Oracle Database Server in the Host Name: field.

Enter 1527 in the Port: field.

Enter scs in the Database User Name field.

Enter and confirm 1realm1 in the password fields.

Click Next.

5

Test Database Connection

Click Test Configuration to ensure that your database connection operates correctly. Make any necessary changes until the connection is successful.
Click Next.

6

Select Targets

Select the AdminServer check box to deploy the new data source on that server.
Click Finish.

6. Navigate to the new PDQRepository data source. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jdbc/NavigateToJdbcSystemResource.html

7. Select the Row Prefetch Enabled check box, and click Save.

8. Stop your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

9. Start your WebLogic Server. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1 (10.3.6) at
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/startstop/StartAndStopServers.html

B Known Issues

This appendix describes known issues with the Oracle DataLens Servers installation and configuration.

B.1 Oracle DataLens Server Conflicts with QuickTime

If your Oracle DataLens Server does not start, it could be because there is a conflict with QuickTime CLASSPATH Environment Variable. You can work around this issue by deleting the CLASSPATH environment variable created by the QuickTime installation, which has no effect on the ability of QuickTime to run.

Delete the QuickTime CLASSPATH variable entry using the following steps:

1. From the Start menu, right-click Computer, select Properties, and then select Advanced Settings.

2. Click Environment Variables.

3. In the System variables section, locate and select the following entry:
CLASSPATH 'C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip'

4. Click Delete.

5. Click OK twice to close all dialogs.

B.2 Oracle DataLens Server Port Number

The Oracle DataLens Server uses port 2229 by default. On a standard installation with a dedicated server, this should not pose any problems. If there is a problem with this port, then the port number can be changed.

If there is a clash with the default port number (2229), then change to port 8089 or another unused port number. You can do this by stopping your WebLogic Server and then editing the ServerProfiles.xml file located in the EDQP_HOME installation directory.

B.3 Privilege Problems

On Linux and UNIX, verify that the entire EDQP directory structure (by default, this is /opt/Oracle/Middleware/opdq/...) is owned by the administration user you use to administer your Oracle DataLens Server. For more information, see "Establishing the Required User Accounts".

On Windows, the share rights and folder rights must be set so that the administration user you use to administer your Oracle DataLens Server can access the repository share.

B.4 WebLogic Server Installation Issues

When installing WebLogic Server, it is possible that the installation may not complete correctly so installing using the console mode fails because the directory exists. You must uninstall the WebLogic Server product, and then manually remove any remaining directories in the WL_HOME directory.

C Configuring JDBC Database Drivers

This appendix describes how to configure additional JDBC database drivers for use on your Oracle DataLens Administration Servers to facilitate interaction between your server and your EDQP supported database. Oracle provides WebLogic-branded versions of DataDirect drivers for DB2 and MySQL Server though they are not configured for use in the classpath. For more information about using WebLogic-branded DataDirect drivers that are included in the WebLogic Server installation and other JDBC database drivers, see Oracle Fusion Middleware Programming JDBC for Oracle WebLogic Server 11g Release 1 (10.3.6) at

http://docs.oracle.com/cd/E23943_01/web.1111/e13726/dd.htm

Note:
You must configure your database driver for use before attempting to establish a database connection on your Oracle DataLens Administration Servers.

Use the following steps to install your JDBC database driver:

1. Download the appropriate JDBC driver for your database or use the WebLogic-branded DataDirect driver.

2. Copy the JDBC driver to the WL_HOME\server\lib\ directory on your Oracle DataLens Administration Server.

3. Edit the following EDQP environment file to configure the driver for use:
On Linux and UNIX:

WL_HOME\common\bin\commEnv.sh

On Windows:

WL_HOME\common\bin\commEnv.cmd

4. Add the new JDBC driver to the classpath, WEBLOGIC_CLASSPATH, as in the following example that configures the Oracle database, My SQL, DB2, and PostgreS QL drivers:

set WEBLOGIC_CLASSPATH=%WEBLOGIC_CLASSPATH%;%WL_HOME%\server\lib\ojdbc6.jar;
%WL_HOME%\server\lib\mysql-connector-java-commercial-5.1.17-bin.jar;%WL_HOME%\server\lib\wldb2.jar;%WL_HOME%\server\lib\postgresql-9.2-1002.jdbc4.jar

5. Save and close the file.

Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved.