Oracle Tax Analytics

Installation Guide

Oracle Corporation

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

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 software or related documentation 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 which 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.

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 Oracle Tax Analytics Installation Guide describes the requirements and steps necessary to install Oracle Tax Analytics.

Audience

Oracle Tax Analytics Installation Guide is intended for system administrators installing Oracle Tax Analytics. To use this document you should have:

- Experience installing and configuring application servers and other software

- Administrative privileges on the host where you are installing the software

Documentation and Related Resources

Oracle Tax Analytics Documentation Set

The Oracle Tax Analytics documentation set includes the following documents:

- Oracle Tax Analytics Release Notes

- Oracle Tax Analytics Quick Install Guide

- Oracle Tax Analytics Installation Guide

- Oracle Tax Analytics Implementation Guide

- Oracle Tax Analytics Reference Guide

Oracle Technology Network

Visit the Oracle Technology Network (OTN) to access demos, whitepapers, Oracle By Example (OBE) tutorials, updated Oracle documentation, and other collateral.

Registering on OTN

You must register online before using OTN, Registration is free and can be done at www.oracle.com/technetwork/index.html

Oracle Documentation on OTN

The Oracle Documentation site on OTN provides access to Oracle documentation. After you have a user name and password for OTN, you can go directly to the documentation section of the OTN Web site at www.oracle.com/technetwork/indexes/documentation/index.html

Oracle Support

Oracle customers have access to electronic support through My Oracle Support.

Document Conventions

The following text conventions are used in this document:

Table 1. Documentation Conventions

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.

Oracle Tax Analytics Installation Overview

Oracle Tax Analytics in Brief

Oracle Tax Analytics is a pre-built Enterprise Data Warehouse solution that addresses the operational and predictive analytical needs of public sector revenue management authorities.

includes the following pre-built content:

- A comprehensive Oracle Tax Data Model – to jump start building a data warehouse solution

- Pre-built Intra-ETL

- Pre-built Metadata Repository

- Pre-built Web Catalog

Component

Description

Oracle Tax Data Model (OTDM)

This pre-built data model is based on the Oracle Data Warehouse Reference Architecture and includes:

- a pre-built normalized foundation layer

- pre-built star schemas

- pre-built data mining areas/sandpits for specific analysis.

For more information about the Oracle Tax Data Model, see the OTA Reference Guide.

Intra E-LT

Automatic data movement across the different layers of the Oracle Tax Data Model utilizing Oracle Data Integrator 11g

Metadata Repository

This OBIEE RPD is the business metatdata content that include:

- Multi-layered Abstraction

- Prebuilt Metrics/Dimensions

- Prebuilt hierarchy drills and cross dimensional drills

- Prebuilt Aggregate navigation

Web Catalog

This OBIEE web catalog includes pre-built Reports/Dashboards

Oracle Tax Analytics Licensed Products

Oracle Tax Analytics consists of three separately licensable products that provide a modular approach to implementing data warehouse and business intelligence solution and meet each agency’s unique information needs.

- Oracle Tax Accounting Analytics

- Oracle Tax Collections Analytics

- Oracle Tax Registration Analytics

Oracle Tax Analytics Architecture Overview

High-level analytical queries, like those commonly used in Oracle Business Intelligence, scan and analyze large volumes of data using complex formulas. This process can take a long time when querying a transactional database and will impact overall system performance.

For this reason, the Oracle Tax Analytics solution is constructed based on Oracle data warehouse reference architecture, which uses both normalized and dimensional modeling techniques to process generic data and to allow for fast access to information required for decision making.

- Architecture Components

Architecture Components

Oracle Tax Analytics architecture consists of an Oracle Database, Oracle Data Integrator, and Oracle Business Intelligence Enterprise Edition. The following diagram illustrates a typical Oracle Tax Analytics physical architecture.

Database

The Database component contains the following:

- Oracle Tax Data Model, which includes a normalized and dimensional schemas.

- Data Mining schema.

Oracle Data Integrator Installation

- The Client tier contains the Oracle Data Integrator Java client tools such as Topology Manager, Designer, Operator and Security Manager. The client may also have an http client for accessing the ODI Console and a lightweight designer Web application for ODI.

- The Server tier contains the following:

- Oracle Data Integrator Repositories. The repositories contain the metadata required for the data movement within the data warehouse.

- Oracle Data Integrator Agent: The agent executes the E-LT jobs that are submitted from the ODI java client or ODI console application.

- The Database tier contains the ODI Repositories and Oracle Tax Analytics schema

Oracle Business Intelligence Enterprise Edition Installation

- The Client tier contains supported internet browser, which is used to access Analysis, Interactive Dashboards, etc.

- The Server tier contains the following:

- Business Intelligence presentation services

- Business Intelligence Server

- Business Intelligence Java Host

- etc

When you deploy Oracle Tax Analytics, you can use the following documentation and tools to manage your metadata:

Oracle Business Intelligence Enterprise Edition Repository Documentation

Using the Oracle BI Administration Tool, you can generate repository documentation that lists the mapping from the presentation columns to the corresponding logical and physical columns. You might use this information for gap-analysis, or to create a record of your repository that you can use to compare with other repositories.

To generate repository documentation into a text or comma-separated file, log into Oracle BI Administration Tool and choose Tools > Utilities > Repository Documentation .

For more information about generating repository documentation, see the Oracle Business Intelligence Server Administration Guide.

Oracle Business Intelligence Enterprise Edition Presentation Services Catalog

Using the Catalog Manager, you can view the names of the pre-built dashboards and requests in the Presentation Services Catalog. To view the Presentation Catalog, open the Start menu and select Catalog Manager from All Programs > Oracle Business Intelligence .

Hardware and Software Requirements

This section provides information about hardware and software requirements for Oracle Tax Analytics.

Before you install Oracle Tax Analytics, you must verify that all hardware and software requirements are met.

Note: Also see the Oracle Tax Analytics Release Notes. For the most current version of the Oracle Tax Analytics Quick Install Guide, see Oracle patch number 14637277.

Supported Platforms

For latest supported platforms, please refer to the Oracle Tax Analytics Quick Install Guide.

Hardware Requirements

For latest Hardware Requirements, please refer to the Oracle Tax Analytics Quick Install Guide.

Software Requirements

The minimum software requirements for Oracle Tax Analytics are as follows:

- Operating System: For details of supported platforms, see the Supported Platforms section of the Oracle Tax Analytics Quick Install Guide.

- Oracle Database 11g Release 2 Enterprise Edition (11.2.0.2). See Oracle Database Requirements, below.

- Oracle Business Intelligence Enterprise Edition 11.1.1.6.0. See Oracle Business Intelligence Enterprise Edition, below.

- Oracle Data Integrator Enterprise Edition 11g (11.1.1.6.0). See Oracle Data Integrator Enterprise Edition, below.

- Java Runtime Environment (JRE 1.6 or above). See Java Runtime Environment, below.

Oracle Database Requirements

Oracle Tax Analytics requires Oracle Database 11g Release 2 Enterprise Edition (11.2.0.2).

Note: When you install the Database, ensure that the database character set is Unicode (AL32UTF8) to support multi-language installations.

Installation of the Oracle Tax Analytics component requires the following optional components to the Database:

- Oracle Partitioning: Though the product can be installed without partitioning, it is highly recommended to use partition to maximize scalability, performance, availability, manageability and minimize storage cost

- Oracle Data Mining: The product comes with a sample schema and reports developed using Oracle Data Mining. This is required only when installing the sample data mining model.

Note: To verify that you have Oracle Data Mining installed, follow the instructions outlined in Confirming that Oracle Data Mining Options are Installed.

Oracle Business Intelligence Suite Enterprise Edition

You must have the Oracle Business Intelligence Enterprise Edition installed before you can view and use the Oracle Tax Analytics reports.

Note:

Oracle Business Intelligence Suite Enterprise Edition 11.1.1.6.0 can be downloaded from the Oracle Business Intelligence 11g downloads link on Oracle Technology Network at:

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

Installation instructions are included in the documentation.

Oracle Data Integrator Enterprise Edition

You must have Oracle Data Integrator Enterprise Edition software installed before start using the application. The intra E-LT to load the data from the Foundation (3NF) layer into the Access and Performance (A&P) layer are developed using ODI. To be able to execute and load the data into A&P layer, ODI must be installed and configured. When you install the ODI software, select the option to skip repository configuration under "Repository Configuration" page. The repositories will be populated by the Oracle Tax Analytics installer during install. Also specify OTDM_AGENT_1 and the port number of your choice (e.g., 20000) for Agent Name and Agent Port, respectively, in the Specify Agent Details page.

Oracle Data Integrator Enterprise Edition 11g (11.1.1.6.0) can be downloaded from Oracle Technology Network at:

- http://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html

Installation instructions are included in the documentation.

Note: The Oracle Tax Analytics installer also requires Oracle Data Integrator SDK to create the Master and Work Repositories. You must have Oracle Data Integrator installed with SDK on the machine where installer will be executed. To include the SDK when you install the ODI software, select the ODI SDK option under Developer Installation .

Java Runtime Environment (JRE 1.6 or above)

You must have Java Runtime Environment 1.6 or above installed before running the Oracle Tax Analytics installer. The installer can be executed either from Windows or Unix OS. JRE 1.6 or above can be downloaded at:

- http://java.com/en/download/index.jsp

Note: JRE is required only on the machine where the installer will be executed.

Introduction to Oracle Tax Analytics Installation

Installation Components

Oracle Tax Analytics mandatory and optional components.

Oracle Data Integrator Repositories

The installer is packaged with Oracle Tax Analytics ODI repositories, containing the metadata required for automatic data movement across the different layers of the Oracle Tax Data Model utilizing Oracle Data Integrator 11g.

Oracle Tax Data Model Schema

The installer is packaged with scripts to install Oracle Tax Analytics Foundation and Access & Performance (OTDM) schema objects and the configuration data.

Note: The source data is populated in to the Foundation layer, then the dimension and facts are populated using the intra-E-LT delivered with the product For detailed information about all created objects in the OTDM, see the Oracle Tax Analytics Reference Guide.

System Data

Oracle Business Intelligence Enterprise Edition Content

Oracle Tax Analytics installation package contains the reports and web catalog that need to be deployed into your Oracle Business Intelligence Enterprise Edition environment. For more information on installing this reports and web catalog, refer to the Installing OBIEE Components. The following files that define and create the reports:

- otdm.rpd

- otdmwebcat.zip

- writeback.xml

Sample Data Mining Model (optional)

The installer is packaged with scripts to install Sample Data Mining (OTDM_MINING) schema for. This schema contains all the mining components of Oracle Tax Analytics except the data mining results tables.

Sample Data (optional)

Sample data for OTDM and OTDM_MINING schemas is provided and can be downloaded using Patch 14659298.

Oracle Tax Analytics Installer Directory Structure

The Oracle Tax Analytics installation image provides the described directory structure and content.

The installation image contains the following directories:

- bin: contains the scripts to launch the installer. There are two scripts provided in this directory for Unix and Windows platforms.

- Files:

- setup.sh: Install script for Unix

- setup.bat: Install script for Windows

- config: contains the installation configuration file. This file needs to be updated with your environment specific information which will be used by the installer to perform the installation.

- Files:

- Install.properties: Installation properties file

- lib: Libraries required for the installer

- log: contains installation log files created by the installer

- obiee: contains the report files and web catalog to be deployed into Oracle Business Enterprise Edition environment.

- Files:

- OTDM.zip: OBIEE Web Catalog

- OTDM.rpd: OBIEE reports

- Writeback.xml: Used for OBIEE write back feature

- odi: contains the OTA master and work repository export files

- Subdirectories:

- master: contains MasterRepository.zip

- work: contains WorkRepository.zip

- schemas: contains the physical schema creation scripts and system data installation scripts.

- Subdirectories:

- OTDM: main directory contains scripts to install OTDM schema.

- OTDM/config: schema configuration files required for the installer

- OTDM/scripts: relational schema installation scripts

- OTDM/data: Scripts to install system data required for the application

Overview of the Installation Process

This section describes a high level overview of the Oracle Tax Analytics installation tasks.

1. Read Oracle Tax Analytics Release Notes to identify any last minute changes.

2. Verify that your system is one of the supported platforms and that it satisfies the hardware and software requirements as described in . Also refer to Oracle Tax Analytics Quick Install Guide for detailed information.

3. Identify and perform any necessary pre-installation tasks, as described in Pre-Installation Tasks.

4. Install the Oracle Tax Analytics components as described in Installer Execution.

5. Identify and perform any necessary post-installation tasks, as described in Post-Installation Tasks.

6. Install the additional components that you need to create an Oracle Tax Analytics Environment to run the reports, as described in Installing OBIEE Components.

7. Configure Oracle Data Integrator Agent to run the intra E-LTs as described in Oracle Tax Analytics-Oracle Data Integrator Component Setup.

Installing Oracle Tax Analytics

Pre-Installation Tasks

Prior to installing Oracle Tax Analytics, ensure that the environment is properly configured.

1. Ensure that the software required for Oracle Tax Analytics is installed, as described in "Ensuring that Required Software is Installed."

2. Set the maximum processes initialization parameter, as described in "Changing the Default Value for the Maximum Processes Initialization Parameter."

3. If you are using the Database Vault Option, disable the option, as described in "Disabling the Data Vault Option on the Database."

4. Create recommended tablespaces for Oracle Tax Analytics.

5. Create required database users and grant required privilege to the users.

6. Update install.properties file with your environment specific values.

- Ensuring that Required Software is Installed

- Changing the Default Value for the Maximum Processes Initialization Parameter

- Disabling the Data Vault Option on the Database

- Create Recommended Tablespaces for Oracle Tax Analytics

Oracle Tax Analytics consists of multiple database schemas. It is recommended that you create one tablespace for each type of schema object.

- Create and Grant Required Privileges to Users

Describes Oracle Tax Analytics users, their default user tablespaces, and their required database privileges.

- Updating installer.properties

Ensuring that Required Software is Installed

As discussed in "Software Requirements," you must have certain software installed before you can successfully install the Oracle Tax Analytics components.

Take the following steps to ensure that, the required software is installed: Before you install Oracle Tax Analytics:

- Confirming that Oracle Data Mining Option is Installed

To check that the Oracle Data Mining Option is installed, log in to the database as SYS user and enter the following SQL query: SELECT VALUE FROM V$OPTION WHERE PARAMETER ='Data Mining'; . If this query returns TRUE, then the option is installed.

Changing the Default Value for the Maximum Processes Initialization Parameter

The default value used for database parameter called PROCESSES may not be sufficient for larger implementations, increase the value for this parameter if required.

How to determine the current value for the PROCESSES parameter

To determine the current value for the maximum processes parameter, log in to database with DBA account, and then execute the following SQL statement:

show parameter processes;

How to change the value for the maximum processes

To change the value for the maximum processes, issue the following statements. Depending on your database options, the value specified for processes should be set to a minimum value greater than or equal to 250.

alter system set processes=250 scope=spfile;

shutdown immediate

startup

Disabling the Data Vault Option on the Database

Database Vault-enabled databases may prevent the Oracle Tax Analytics installer from running DDLs in the target schema. For an Oracle Database with the Vault option on, take the following steps to disable the Vault option before you install Oracle Tax Analytics.

To find out if the Oracle Database is Vault-enabled, do the following:

SELECT * FROM V$OPTION WHERE PARAMETER = 'Oracle Database Vault';

If this command returns true, then the Vault option is enabled.

Disabling the Vault Option

To disable the Vault option, do the following:

- On UNIX systems, ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set.

- Log in to SQL*Plus as user SYS with the SYSOPER privilege.

- Shut down the Database.

- From the command line, stop the Database Control console process and the listener. For example:
sqlplus sys as sysoper

Enter password: password

SQL> SHUTDOWN IMMEDIATE

SQL> EXIT

$ emctl stop dbconsole

$ lsnrctl stop listener_name

Once you have installed Oracle Tax Analytics, re-enable the Vault, as described in "Re-Enabling the Vault Option on the Database."

Create Recommended Tablespaces for Oracle Tax Analytics

Oracle Tax Analytics consists of multiple database schemas. It is recommended that you create one tablespace for each type of schema object.

The following table lists the recommended tablespaces. If the recommendation is followed, you must create these tablespaces before starting the installation.

Tablespace Name

Description

OTDM_01

The tablespace where Foundation and A&P layer schema objects are stored

OTDM_REPOMTR_01

The tablespace where Oracle Data Integrator Master Repository objects are stored

OTDM_REPOWRK_01

The tablespace where Oracle Data Integrator Work Repository objects are stored

OTDM_ODI_STAGE_01

The tablespace where interim objects created by Oracle Data Integrator, when executing E-LT, are  stored

OTDM_MINING_01

The tablespace where Sample Data Mining objects are stored

Sample scripts to create the above tablespaces:

- Create Tablespace OTDM_01 Datafile '/u01/oracle/oradata/OTDM_01.dbf' size 1024m autoextend on next 128m maxsize unlimited;

- Create Tablespace OTDM_REPOMTR_01 Datafile '/u01/oracle/oradata/ OTDM_REPOMTR_01.dbf' size 1024m autoextend on next 128m maxsize unlimited;

- Create Tablespace OTDM_REPOWRK_01 Datafile '/u01/oracle/oradata/ OTDM_REPOWRK_01.dbf' size 1024m autoextend on next 128m maxsize unlimited;

- Create Tablespace OTDM_ODI_STAGE_01Datafile '/u01/oracle/oradata/ OTDM_ODI_STAGE_01.dbf' size 1024m autoextend on next 128m maxsize unlimited;

- Create Tablespace OTDM_MINING_01 Datafile '/u01/oracle/oradata/OTDM_MINING_01.dbf' size 1024m autoextend on next 128m maxsize unlimited;

Create and Grant Required Privileges to Users

Describes Oracle Tax Analytics users, their default user tablespaces, and their required database privileges.

The following table lists the Oracle Tax Analytics database users and the corresponding tablespaces and privileges.

Database User ID

Description

Password

Tablespace

Privileges

OTDM

Foundation and A&P layer

OTDM

OTDM_01

CREATE TABLE

CREATE SESSION

CREATE PROCEDURE

CREATE SEQUENCE

CREATE MATERIALIZED

VIEW CREATE VIEW

UNLIMITED TABLESPACE

OTDM_REPOMTR

ODI Master Repository

OTDM_REPOMTR

OTDM_REPOMTR_01

CONNET RESOURCE

UNLIMITED  TABLESPACE

OTDM_REPOWRK

ODI Work Repository

OTDM_REPOWRK

OTDM_REPOWRK_01

CONNET RESOURCE

UNLIMITED TABLESPACE

OTDM_ODI_STAGE

ODI Work Schema

OTDM_ODI_STAGE

OTDM_ODI_STAGE_01

CREATE TABLE

CREATE SESSION

CREATE PROCEDURE

CREATE SEQUENCE

CREATE MATERIALIZED VIEW

CREATE VIEW

DROP ANY DIRECTORY

CREATE ANY DIRECTORY

ANALYZE ANY

UNLIMITED TABLESPACE

UPDATE ANY TABLE

ALTER ANY TABLE

SELECT ANY TABLE

SELECT ANY SEQUENCE

INSERT ANY TABLE

CREATE ANY MATERIALIZED VIEW

ALTER ANY MATERIALIZED VIEW

DROP ANY MATERIALIZED VIEW

COMMENT ANY TABLE

CREATE ANY TABLE

CREATE SYNONYM

DROP ANY TABLE

UNLIMITED TABLESPACE

CREATE ANY INDEX

DROP ANY INDEX

OTDM_MINING

Sample Data mining user

OTDM_MINING

OTDM_MINING_01

QUOTA UNLIMITED ON OTDM_MINING_01

CREATE TABLE

CREATE SESSION

CREATE PROCEDURE

CREATE SEQUENCE

CREATE MATERIALIZED VIEW

CREATE VIEW

CREATE MINING MODEL

EXECUTE ON CTXSYS.CTX_DDL

ALTER ANY MINING MODEL

SELECT ANY MINING MODEL

Sample scripts to create the above users:

- Create Master Repository User

- CREATE USER OTDM_REPOMTR IDENTIFIED BY OTDM_REPOMTR DEFAULT TABLESPACE OTDM_REPOMTR_01 TEMPORARY TABLESPACE TEMP;

- GRANT CONNECT, RESOURCE, UNLIMITED TABLESPACE TO OTDM_REPOMTR;

- Create Work Repository User

- CREATE USER OTDM_REPOWRK IDENTIFIED BY OTDM_REPOWRK DEFAULT TABLESPACE OTDM_REPOWRK_01 TEMPORARY TABLESPACE TEMP;

- GRANT CONNECT, RESOURCE, UNLIMITED TABLESPACE TO OTDM_REPOWRK;

- Create OTDM USER

- CREATE USER OTDM IDENTIFIED BY OTDM DEFAULT TABLESPACE OTDM_01 TEMPORARY TABLESPACE TEMP;

- GRANT CONNECT, RESOURCE, CREATE TABLE,CREATE SESSION,CREATE PROCEDURE,CREATE SEQUENCE,CREATE MATERIALIZED VIEW,CREATE VIEW,UNLIMITED TABLESPACE TO OTDM

- Create ODI Staging USER

- CREATE USER OTDM_ODI_STAGE IDENTIFIED BY OTDM_ODI_STAGE DEFAULT TABLESPACE TDM_ODI_STAGE_01 TEMPORARY TABLESPACE TEMP;

- GRANT CREATE TABLE, CREATE SESSION, CREATE PROCEDURE, CREATE SEQUENCE, CREATE MATERIALIZED VIEW, CREATE VIEW, DROP ANY DIRECTORY, CREATE ANY DIRECTORY,ANALYZE ANY, UNLIMITED TABLESPACE, UPDATE ANY TABLE, ALTER ANY TABLE, SELECT ANY TABLE, SELECT ANY SEQUENCE, INSERT ANY TABLE, CREATE ANY MATERIALIZED VIEW,ALTER ANY MATERIALIZED VIEW, DROP ANY MATERIALIZED VIEW, COMMENT ANY TABLE,CREATE ANY TABLE, CREATE SYNONYM, DROP ANY TABLE, CREATE ANY INDEX, DROP ANY INDEX TO OTDM_ODI_STAGE

- Create Data Mining USER

- CREATE USER OTDM_MINING IDENTIFIED BY OTDM_MINING DEFAULT TABLESPACE OTDM_MINING_01 TEMPORARY TABLESPACE TEMP;

- GRANT CREATE TABLE, CREATE SESSION, CREATE PROCEDURE,CREATE SEQUENCE,CREATE MATERIALIZED VIEW, CREATE VIEW, CREATE MINING MODEL, EXECUTE ON CTXSYS.CTX_DDL,ALTER ANY MINING MODEL,SELECT ANY MINING MODEL TO OTDM_MINING;

Updating installer.properties

There are number of configuration parameters stored in the installer.properties file. Before running the installer, this file needs to be updated with your environment specific values. If it is required to create more than one environment, it is recommended to clone this file and keep a separate copy for each one of the environments. Since OTDM and OTDM_MINING schema objects will be installed in two different schemas, make sure you update this file with correct user id and password before installing the schema.

The various configuration parameters are explained below.

DBURL

The JDBC URL for the Oracle Tax Data Model and Sample Datamining database. The JDBC URL must follow the format given below jdbc:oracle:thin:@<db host name>:<port>:<SID> Example: jdbc:oracle:thin:@dbserver.us.oracle.com:1521:OTDM

USER

The Oracle Tax Data Model or Sample Datamining database user. Make sure this value is updated depending on the type of schema being installed . For more information, refer to the Create Required Users.

PASSWORD

The Oracle Tax Data Model or Sample Datamining database user’s password. Make sure this value is updated depending on the type of schema being installed.

Note: The password value must be entered in plain text format. If you do not wish to update this parameter in plain text, then leave this value empty. The installer will prompt for the password during install time.

SCHEMA

The Oracle Tax Data Model or Sample Datamining Schema Name. Make sure this value is updated depending on the type of schema being installed.

MRID

The ODI master repository internal ID. It is recommended to use unique id for each of the environment at your site.

Important: The ODI Repository IDs 1 to 500 and 999 are reserved for Product Development and should not be used. Please choose an ID in the range of 501 to 998. For more information about repository IDs, refer to the Oracle Data Integrator Documentation.

MWID

The ODI work repository internal ID. It is recommended to use unique id for each the environment at your site.

Important: Important: The ODI Repository IDs 1 to 500 and 999 are reserved for Product Development and should not be used. Please choose an ID in the range of 501 to 998. For more information about repository IDs, refer to the Oracle Data Integrator Documentation.

MRDBURL

The JDBC URL for the ODI MASTER Repository database. The JDBC URL must follow the format given below jdbc:oracle:thin:@<db host name>:<port>:<SID>

Example: jdbc:oracle:thin:@dbserver.us.oracle.com:1521:REPOMTR

MRUSER

The master repository database user. For more information, refer to Create Required Users.

MRPASSWORD

The master repository user’s password.

Note: The password value must be entered in plain text format. If you do not wish to update this parameter in plain text, then leave this value empty. The installer will prompt for the password during install time

.

MWDBURL

The JDBC URL for the database ODI Work repository database. The JDBC URL must follow the format given below jdbc:oracle:thin:@<db host name>:<port>:<SID>

Example: jdbc:oracle:thin:@dbserver.us.oracle.com:1521:REPOWRK

Important: The MASTER and WORK repositories must be created in the same database.

MWUSER

The work repository user name. For more information, refer to the Create Required Users.

MWPASSWORD

The work repository user’s password. Note: The password value must be entered in plain text format. If you do not wish to update this parameter in plain text, then leave this value empty. The installer will prompt for the password during install time.

MWREPOSITORY

The WORK repository name. This parameter is not modifiable at this time. Required Value: OTDM_WORK_REPOSITORY

MODISTGUSER

The Oracle Data Integrator staging user name. This parameter is not modifiable. Required value is OTDM_ODI_STAGE. For more information, refer to the Create Required Users.

MODISTGPASSWORD

The Oracle Data Integrator staging user’s password. Note: The password value must be entered in plain text format. If you do not wish to update this parameter in plain text, then leave this value empty. The installer will prompt for the password during install time.

MODIUSER

Oracle Data Integrator administrator user name. This user will have administrator access to the ODI repositories

MODIPASSWORD

Oracle Data Integrator administrator user’s password.

Note: The password value must be entered in plain text format. If you do not wish to update this parameter in plain text, then leave this value empty. The installer will prompt for the password during install time.

MAGENT_SERVER

The Oracle Data Integrator Agent server name or IP address. Refer to Oracle Tax Analytics-Oracle Data Integrator Component Setup information on setting up an ODI agent.

Example: agentserver.us.oracle.com

MAGENT_PORT

The Oracle Data Integrator Agent port. Refer to Oracle Tax Analytics-Oracle Data Integrator Component Setup information on setting up an ODI agent.

Example: 20000

Installer Execution

This section explains how to create and configure Oracle Tax Analytics Schemas and the Oracle Data Integrator Repositories using the Oracle Tax Analytics Installer.

Before You Begin

- The Oracle Tax Analytics installer requires JRE 1.6 or above and Oracle Data Integrator 11.1.1.6.0 with SDK.

- The installer must be executed from the server or desktop where these software are installed. To install ODI SDK, choose the "SDK" option under "Developer Installation" when installing Oracle Data Integrator software.

- The database and the users for the ODI repositories, Oracle Tax Data Model and Sample Datamining schema must exist before running the installer.

- Creating and Configuring Environment Variables

- Launching the Installer

- Installing Oracle Tax Analytics ODI Repositories

- Installing Oracle Tax Data Model Schema

Creating and Configuring Environment Variables

Set the following environment variables before running the installer:

- Windows

- set JAVA_HOME=<directory where JRE is installed>

- set ODI_HOME=<directory where ODI is installed>/Oracle_ODI1

- Linux or Unix

- export JAVA_HOME=<directory where JRE is installed>

- export ODI_HOME=<directory where ODI is installed>\Oracle_ODI1

Note: Linux and Unix commands depend on the shell you are using; the commands above are for the Bash shell.

Launching the Installer

When you unzip the Oracle Tax Analytics install package, files are extracted into the following directory structure:

To launch the installer, run the setup.bat (for Windows) or setup.sh (for Linux or Unix) from <install_dir>/OTA/bin directory.

- Installer Options

The Oracle Tax Analytics Installer can be executed with various options.

Installer Options

The Oracle Tax Analytics Installer can be executed with various options.

Depending upon the component installed, one or more command line options will be used when executing the setup script.

Option

Description

-h

Displays various command line options available with a short description.

-v

Displays version information of the installer.

-s

This option is used to specify the configuration file name, where the environment specific values are stored. This file is expected to be present in "config" directory.

Note: This option is used only when installing Oracle Tax Data Model schema, Sample Datamining schema, or when installing Oracle Data Integrator Master and Work Repositories.

-t

This option is used to specify the configuration file name, where the environment specific values are stored. This file is expected to be present in “config” directory.

Note: This option is used only when installing Oracle Tax Analytics Schemas or when installing Oracle Data Integrator Master and Work Repositories

-createRepository

This option is used to create Oracle Data Integrator Master and Work repositories using delivered repository export files. This option will also configure the data server and the agent.

Example:

./setup.sh –createRepository –t install.properties

-installSchema <arg>

This option will create the Oracle Tax Data Model or sample Datamining schema objects The argument value passed to this option is OTDM for Oracle Tax Data Mode and MINING for Sample DataMining Schema.

Example:

./setup.sh –installSchema OTDM –t install.properties

./setup.sh –installSchema MINING –t install.properties

-installData <arg>

This option is used to install Oracle Tax Data Model or Sample Datamining system data. The install package is delivered with DML scripts to install system data for both OracleTax Data Model and Datamining schemas. This option will execute these scripts to install the system data. The argument value passed for this option is OTDM or MINING.

Example:

./setup.sh –installData OTDM –t install.properties

./setup.sh –installData MINING –t install.properties

-exportMasterRepository <arg>

This option is used to export the master repository into a zip file. The argument value used for this option is the output directory where the export file needs to be created. If no argument is passed, the export file is created in the directory <install Dir>/odi/master/MasterRepository.zip.

Example:

./setup.sh –exportMasterRepository /backups/odi/master/

–s install.properties

-exportWorkRepository <arg>

This option is used to export the work repository into a zip file. The argument value used for this option is the output directory where the export file needs to be created. If no argument is passed, the export is created in the directory <install Dir>/odi/work/WorkRepository.zip.

Example:

./setup.sh –exportWorkRepository /backups/odi/work/ –s

install.properties

Installing Oracle Tax Analytics ODI Repositories

Creating Oracle Data Integrator Master Repository

Oracle Data Integrator Master Repository is installed using "createRepository" option. Before running the installer update the install.properties file with JDBC and user information for ODI master repository. Also update the Oracle Tax Data Model schema name, ODI staging user information, the agent server and the port. This information will be used to update the ODI topology after creating the master repository.

To run the installer on Windows execute setup.bat or on Linux and Unix execute setup.sh script from <install_dir>/OTA/bin with the "createRepositry" option

The following parameters are required to create the master repository. You must have these parameters updated with your environment specific values before running the installer.

- MRID – Master Repository Internal ID, should be unique for each environment

- MWID – Work Repository Internal ID, should be unique for each environment

- DBURL= Oracle Tax Data Model Database connection information

- USER= Oracle Tax Data Model Database user

- PASSWORD= Oracle Tax Data Model user password

- SCHEMA= Oracle Tax Data Model Database Schema

- MRDBURL – Master Repository Database JDBC connection information

- MRUSER – Master Repository Database User ID

- MRPASSWORD – Master Repository Database User Passwrod

- MWDBURL – Work Repository Database JDBC connection information

- MWUSER – Work Repository Database User ID

- MWPASSWORD – Work Repository Database User Password

- MWREPOSITORY – Work Reposiotry Name (Required value:OTDM_WORK_REPOSITORY)

- MODISTGUSER – ODI Staging Database User ID

- MODISTGPASSWORD – ODI Staging Database User Password

- MODIUSER – ODI Administrator User ID

- MODIPASSWORD – ODI Administrator User Password

The following example creates the master repostiory. In this example, the configuration values from install.properties are used to create the repository .

cd <install directory>/OTA/bin ./setup.sh -createRepository -t install.properties

Importing Oracle Data Integrator Work Repository

Oracle Data Integrator Work Repository is imported using "importWorkRepository" option. Before running the installer update the install.properties file with JDBC and user information for master and work repositories. The master repository must be created using the installer, before importing the work repository.

To run the installer on Windows execute setup.bat and on Linux or Unix execute setup.sh script from <install_dir>/OTA/bin with the importWorkRepository option.

Before importing the work repository, update the following values in the install.properties file

- MRDBURL – Master Repository Database JDBC connection information

- MRUSER – Master Repository Database User ID

- MRPASSWORD – Master Repository Database User Password

- MWDBURL – Work Repository Database JDBC connection information

- MWUSER – Work Repository Database User ID

- MWPASSWORD – Work Repository Database User Password

- MWREPOSITORY – Work Repository Name (Required value:OTDM_WORK_REPOSITORY)

- MODIUSER – ODI Administrator User ID

- MODIPASSWORD – ODI Administrator User Password

The following example imports work repository from the work repository zip file delivered with the installer. In this example, the configuration information from install.properties are used to import the work repository.

cd <install directory>/OTA/bin ./setup.sh -importWorkRepository -t install.properties

Installing Oracle Tax Data Model Schema

Installing Schema

Oracle Tax Data Model Schema is created using the "installSchema" option. Before running the installer update the install.properties file with the database JDBC, user and password information.

To run the installer on Windows execute setup.bat and on Linux or Unix execute setup.sh script from <install_dir>/OTA/bin with the installSchema option with argument OTDM. Before running the installer, update the following configuration values in the install.properties file.

- DBURL = Oracle Tax Data Model Database connection information

- USER = Oracle Tax Data Model Database user

- PASSWORD = Oracle Tax Data Model user password

- SCHEMA = Oracle Tax Data Model Database Schem

Note: The USER and SCHEMA values must be the name of the Oracle Tax Data Model database user.

The following example creates the Oracle Tax Data Model schema. In this example, the configuration information from install.properties is used to create the schema.

cd <install directory>/OTA/bin

./setup.sh -installSchema OTDM -t install.properties

Installing System Data

The installer is delivered with system data required for Oracle Tax Analytics application to function. The data must be installed in Oracle Tax Data Model schema before using the application. The system data is installed using "installData" option.

To run the installer on Windows execute setup.bat and on Linux or Unix execute setup.sh script from <install_dir>/OTA/bin with the installData option with argument OTDM.

Note: Before running the installer, update the configuration values in the install.properties file, as described above.

.

The following example populates configuration data in Oracle Tax Data Model schema. In this example, the configuration information from install.properties is used to populate the configuration data required in Oracle Tax Data Model schema.

cd <install directory>/OTA/bin

./setup.sh -installData OTDM -t install.properties

Post Installation Steps

This section describes post installation configuration steps.

- Re-Enabling the Database Vault Option

- Ensuring That Oracle Tax Data Model Schema Objects Are Valid

- Verifying the Value of PGA_AGGREGATE_TARGET

- Refresh GET_WAREHOUSE SCHEMA_NAME Variable

- Generating Oracle Data Integrator Scenarios

Procedure to generate Oracle Data Integrator scenarios, which are used to control E-LT processes.

Re-Enabling the Database Vault Option

If you (optionally) disabled the Database Vault Option prior to installation (as described in Disabling the Data Vault Option on the Database), re-enable the option by taking the following steps:

1. Shutdown the Database, Database Control console process, and listener.
For example on Unix, ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set. Log in to SQL*Plus as user SYS with the SYSOPER privilege and shut down the database. Then from the command line, stop the Database Control console process and listener.

For example:

sqlplus sys as sysoper

Enter password: password

SQL> SHUTDOWN IMMEDIATE

SQL> EXIT

$ emctl stop dbconsole

$ lsnrctl stop listener_name

For Oracle RAC installations, shut down each database instance as follows:

$ srvctl stop database -d db_name

2. Enable the Oracle Database Vault option.
cd $ORACLE_HOME/rdbms/lib

make -f ins_rdbms.mk dv_on

make -f ins_rdbms.mk ioracle

3. Startup the Database, Database Control console process, and listener.
For example, on UNIX, Log in to SQL*Plus as user SYS with the SYSOPER privilege and restart the database. Then from the command line, restart the Database Control console process and listener.

For example:

sqlplus sys as sysoper

Enter password: password

SQL> STARTUP

SQL> EXIT

$ emctl start dbconsole

$ lsnrctl start listener_name

Ensuring That Oracle Tax Data Model Schema Objects Are Valid

To ensure that all Oracle Tax Data Model objects are valid, log in to the database with a DBA id and password and recompile all objects in OTDM and OTDM_MINING by issuing the following SQL statements:

1. exec utl_recomp.recomp_serial('OTDM');

2. exec utl_recomp.recomp_serial('OTDM_MINING');

Verifying the Value of PGA_AGGREGATE_TARGET

For good performance, you need to ensure that the PGA_AGGREGATE_TARGET is set to the proper value which depends on the physical RAM of your Database Server. You also need to ensure that the WORKAREA_SIZE_POLICY parameter is set to AUTO.

Note: For information on tuning the PGA_AGGREGATE_TARGET initialization parameter, see Oracle Database Performance Tuning Guide.

Important: Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO.

Refresh GET_WAREHOUSE SCHEMA_NAME Variable

The GET_WAREHOUSE_SCHEMA_NAME variable is used to store the Oracle Tax Analytics schema name. This variable must be refreshed before running the ETLs. Perform following steps to refresh the this variable.

1. Login into Oracle Data Integrator Designer

2. Choose the Project View

3. Expand the Variables tree

4. Right-click GET_WAREHOUSE_SCHEMA_NAME and select Refresh

Generating Oracle Data Integrator Scenarios

Procedure to generate Oracle Data Integrator scenarios, which are used to control E-LT processes.

Oracle Data Integrator scenarios are generated using the Scenario generation dialog in Oracle Data Integrator Designer.

1. In ODI Designer, log in as SUPERVISOR, and display the Projects view.

2. Right-click the project name and select Generate All Scenarios.

3. In the Scenario generation dialog, select the following options:

1. Generation mode: Re-generate

2. Objects to Generate: Packages, Interfaces, Procedures, Variables

3. Marker Filter: Group and Marker set to <None>

4. Click OK An Information dialog will display when the scenario has been generated. Click OK to dismiss.
Note: Click OK for all the scenario variables dialog windows displayed when generating scenarios.

Installing OBIEE Components

This chapter describes how to install Oracle Business Intelligence Enterprise Edition components that comes with the installation package.

Before deploying the Oracle Business Intelligence Enterprise Edition components of Oracle Tax Analytics, you must install Oracle Business Intelligence Enterprise Edition by following the instructions given in the Oracle Business Intelligence Enterprise Edition Installation Guide.

Note: To check that Oracle Business Intelligence Enterprise Edition is installed, follow the instructions in Confirming that Oracle Business Intelligence Enterprise Edition is Installed.

- Deploying Oracle Tax Analytics Components to Oracle Business Intelligence Enterprise Edition

Oracle Tax Analytics installer is packaged with an Oracle Business Intelligence Enterprise Edition metadata repository file (RPD), Web Catalog, and the writeback.xml file. These components are deployed to Oracle Business Intelligence Enterprise Edition in the described procedures.

- Adding OBIEE Users

- Refreshing User GUID

- Adding TNSNAMES.ora Entry

Deploying Oracle Tax Analytics Components to Oracle Business Intelligence Enterprise Edition

Oracle Tax Analytics installer is packaged with an Oracle Business Intelligence Enterprise Edition metadata repository file (RPD), Web Catalog, and the writeback.xml file. These components are deployed to Oracle Business Intelligence Enterprise Edition in the described procedures.

The OBIEE directory, under <install_dir>\OTA\, contains components to be deployed to your Oracle Business Intelligence Enterprise Edition environment.

1. Deploy the Web Catalog and RPD File

Perform the following steps to deploy the Oracle Tax Analytics Web Catalog and RPD file

1. Unzip web catalog from <install_dir>\OTA\OBIEE\OTDM.zip file into your OBIEE environment.

You typically unzip into the <OBIEE HOME>/instances/<instance Name>/bifoundation/ OracleBIPresentationServicesComponent/coreapplication_obips1/catalog directory in your OBIEE environment.

The web catalog will be installed in a directory called OTDM.

2. Use your browser to open the Oracle WebLogic Enterprise Manager portal (http://SERVERNAME:7001/em)

3. Login with the WebLogic admin id and password.

4. Go to Business Intelligence > coreapplication > Deployment > Repository

5. Deploy the Oracle Tax Analytics repository file named OTDM.rpd from <install_dir>/OTA/OBIEE.

Also update the BI Presentation Catalog directory name.

Note: Before deploying the RPD into your OBIEE environment, update the database name, user id, and password using Oracle Business Intelligence Administration tool. The default RPD password is Admin123.

2. Deploy the writeback.xml File

Deploy <install_dir>/OTA/OBIEE/writeback.xml file into your OBIEE environment. You typically copy into the <OBIEE HOME>/instances/<instance Name>/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/analyticsRes/customMessages directory in your OBIEE environment.
Note: If the customMessages directory does not exist, create the directory before copying the file into your environment.

Adding OBIEE Users

Add OBIEE Users with the Oracle WebLogic Server Administration Console.

1. Open the WebLogic Server Administration Console http://SERVERNAME:7001/console/login/LoginForm.jsp

2. Login with your WebLogic admin id and password.

3. Navigate to your security realm to create users.

4. Create an OBIEE user.

1. Create a user named obieeuser and set password.

2. In the Groups tab, assign the obieeuser to the BIAuthor and BIConsumers groups.

5. Create an OBIEE admin user.

1. Create an admin user and set password.

2. In the Groups tab, assign the admin user to the BIAuthor, BIConsumers, and BIAdministrators groups.

Refreshing User GUID

Oracle Business Intelligence users are recognized by their global unique identifiers (GUIDs), not by their names. To make sure these IDs are match with the Oracle BI repository and Oracle BI Presentation Catalog, these GUIDs must be refreshed by following the section named “Refreshing user GUIDs” in the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

Adding TNSNAMES.ora Entry

Add a definition for Oracle Tax Data Model database for the Oracle Tax Analytics repository OTDM.rpd) to use when connecting to the database.

Add the definition to the file <OBIEE install directory>/Oracle_BI1/network/admin/tnsnames.ora

OTDM =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = hostname.domain)(PORT = port-number))

(CONNECT_DATA =(SERVER = DEDICATED)

(SERVICE_NAME = SID) # Change your SID, Hostname, and Listener PortNumber

)

)

Note: Be careful to split these commands properly when you add them to the file; for example, do not add them as one long concatenated line of code.

Oracle Tax Analytics-Oracle Data Integrator Component Setup

Installing Oracle Data Integrator Software

Before configuring the Oracle Data Integrator agent to run the E-LTs, Oracle Data Integrator software must be installed on the server that is designated as an agent server for your environment. Depending upon your requirement, may choose to install standalone agent or J2EE agent with Oracle Data Integrator Console. For more information on installing Oracle Data Integrator software, please refer to Oracle Data Integrator documentation:

http://www.oracle.com/technetwork/middleware/data-integrator/documentation/index.html

Configuring the Oracle Data Integrator Parameter File

Once the Oracle Data Integrator software is installed, you need to update the Oracle Data Integrator agent parameter file with your environment specific values by performing the following steps.

1. On the Oracle Data Integrator machine, open the odiparams.bat or odiparams.sh file in a text editor.

The odiparams.bat or odiparams.sh file is located in the <Install_Dir>\oracledi\agent\bin\ directory. For example, <Install_Dir>\Oracle_ODI1\oracledi\agent\bin.

2. Update the ODI_MASTER_URL parameter.

ODI_MASTER_URL=<JDBC URL>

Set ODI_MASTER_URL="jdbc:oracle:thin:@//<host>:<port>/<sid>"

Replace <host>, <port>, and <sid> with your database specific values.

3. Update the ODI_MASTER_USER parameter.

ODI_MASTER_USER=<Master Repository DB User ID>

ODI_MASTER_ENCODED_PASS=<Master Repository DB User Password>

Note: Password can be encoded using encode.sh/encode.bat script. Refer to Oracle Data Integrator documentation on how to encode the password using this script

4. Update the ODI_SUPERVISOR user ID and password parameters.

ODI_SUPERVISOR=<ODI Supervisor User ID>

ODI_SUPERVISOR_ENCODED_PASS=<ODI Supervisor User Password>

5. Update the ODI_USER Parameters

ODI_USER=

<ODI User ID>

ODI_ENCODED_PASS=<ODI User Password>

6. Update the ODI_SECU_WORK_REP parameter.

ODI_SECU_WORK_REP=OTDM_WORK_REPOSITORY

7. Save the file.

Updating OTDM_AGENT_1 using ODI Topology Manager

This section explains how to update the OTDM_AGENT_1 agent in Topology Manager. The installer configures an agent called “OTDM_AGENT_1” in the Master Repository using the server and port number information from install.properties file. Follow the procedure below, if you want to change the agent configuration.

1. Start Topology Manager, display the Physical Architecture tab, and expand the Agents node.

2. Double-click the OTDM_AGENT_1 node to display the Agent details window.

3. Display the Definition tab, and update the appropriate information, as described in the table below.

Field

Description

Name

Do not change the default value (OTDM_AGENT_1).

Host

The host name of the machine that is running the Agent, typically the Oracle Data Integrator installation machine.

Port

Do not change the default value. If you encounter a port conflict when you run the Oracle Data Integrator Agents, you might need to use a different port number.

Web application context

Change this value to change the web context root, when the Oracle Data Integrator j2ee application is installed

Protocol

Change this value to enable SSL access for ODI J2EE application

Maximum number of sessions

The maximum number of interfaces that can run in parallel (default is 1000). This value is used when load balancing.

4. Click Test to verify the agent.

Starting the Oracle Data Integrator Agent

The OTDM_AGENT_1 should be started before running Intra-E-LTs or procedures in Oracle Data Integrator. Make sure the Oracle Data Integrator Agent is started each time after the server on which you are running the Oracle Data Integrator Agent is re-booted. This task explains how to start the ODI Agents using the port number 20000.

Note: Note: If you encounter a port conflict when you run the Oracle Data Integrator Agents, you might need to use different port numbers. For more information, see Resolving Conflicts in Oracle Data Integrator Agent Port Numbers.

When you use Oracle Data Integrator Designer to execute Packages and Interfaces, choose OTDM_AGENT_1 Agent from the Agent drop down.

1. Starting ODI Agent on Windows

On the ODI machine, open a command window and change directory to the <Install Directory>/Oracle_ODI1/oracledi/agent/bin/

To install the agent as a Windows service, execute the following commands one time.

agentservice –i –s OTDM_AGENT_1 20000

agentservice.bat

The start the agent services, run 'services.msc' from the Windows > Run dialog and Start the ‘OracleDI Agent OTDM_AGENT_1’ service

Note: Command log information about Agents is stored in the file $ODI_HOME\oracledi\bin\agentservice.log.

2. Starting ODI Agent on Linux or Unix

On the Oracle Data Integrator machine, open a command window and change directory to <Install Directory>/oracledi/bin.

Execute the following command:

./agent.sh -NAME=OTDM_AGENT_1 -PORT=20000 &

Note: Run the above command in nohup mode if you do not want the agent to be shutdown when you log out of the Unix session.

Verifying the Oracle Tax Analytics Installation

Verifying Oracle Tax Analytics Installation and Set Up

To verify an Oracle Tax Analytics environment, do the following:

1. Log into Oracle Data Integrator Designer or Oracle Data Integrator Topology Manager as user SUPERVISOR.

2. Use Oracle Data Integrator Designer to connect to the Work Repository.

3. Use Oracle Data Integrator Topology Manager to check the Oracle Data Server “ORACLE_PHYSICAL_OTDM”

4. Use Oracle Data Integrator Topology Manager to check the Agent “OTDM_AGENT_1”.

5. Use Oracle Data Integrator Topology Designer to check that the Model objects are available.

Verifying Reports with Oracle Business Intelligence Enterprise Edition

Verify reports are working by performing the following:

1. Open Oracle Business Intelligence Enterprise Edition Analytics in a browser.

For example: http://SERVERNAME:9704/analytics

2. Login into Oracle Business Intelligence Enterprise Edition as the obieeuser.

3. Select Dashboards to navigate to a subject areas to view the reports.

Miscellaneous and Supporting Tasks

This section provides information on miscellaneous and supporting tasks related to installing Oracle Tax Analytics.

- Resetting the Default Passwords, Schema Names, and Oracle Data Integrator Connection Details

- Deploying Oracle Data Integrator Across Multiple Environments

- Running an Oracle Data Integrator Agent as a Unix Background Process

- Uninstalling ODI Agent Windows Services

- Resolving Conflicts in Oracle Data Integrator Agent Port Numbers

This section explains how to modify your Oracle Tax Analytics deployment to resolve conflicting port numbers for Oracle Data Integrator Agents.

- List of Log Files

Resetting the Default Passwords, Schema Names, and Oracle Data Integrator Connection Details

Oracle recommends that you use the out-of-the-box user names, schema names, and tablespace names. If you do use different names, follow the procedures in this section to keep the Oracle Tax Analytics components synchronized.

- Changing Default Database Passwords

- Changing the Oracle Data Integrator Topology Connection Details

This section explains how to change the default Oracle Data Integrator Topology Connection details.

- Changing Encoded Passwords in odiparams.bat

This section explains how to change the encoded passwords that are set in the Oracle Data Integrator agent configuration file, odiparams.sh or odiparams.bat.

- Changing the Password for the ODI SUPERVISOR User

This section explains how to change the ODI SUPERVISOR password.

- Using Different Schema and Tablespace Names

This section explains the changes necessary when using different schema and tablespace names.

Changing Default Database Passwords

This section explains how to change the default passwords for the database users that you set up in Create Required Users.

1. Use a SQL client to change the database password.

For example, you might connect to the database using SQL Developer or SQL*Plus and execute the following command:

ALTER USER OTDM IDENTIFIED BY <New Password> REPLACE <Old Password>

Note: If you change the OTDM_ODI_STAGE, you must update ORACLE_PHYSICAL_OTDM using Oracle Database Integrator Topology manager as described in Changing the Oracle Data Integrator Topology Connection Details.

2. If you change the password for OTDM or OTDM_MINING schemas, you must update the RPD and redeploy.

Changing the Oracle Data Integrator Topology Connection Details

This section explains how to change the default Oracle Data Integrator Topology Connection details.

Use the Oracle Data Integrator Topology Manager to change the connection details.

1. Open the physical tab

2. Expand the Technologies > Oracle node.

3. Edit the ORACLE_PHYSICAL_OTDM

4. Use the Password field to modify the password; click Test to verify the new password.

5. Click OK to save the details.

Changing Encoded Passwords in odiparams.bat

This section explains how to change the encoded passwords that are set in the Oracle Data Integrator agent configuration file, odiparams.sh or odiparams.bat.

As an example, the Oracle Data Integrator parameter file, which is located in the <ODI install dir>\oracledi\agent\bi directory, might contain the following parameters:

set ODI_SECU_USER=REPOMTR

set ODI_SECU_ENCODED_PASS=dpfHHIqHwW.v9VGofVVd6eG0x set ODI_USER=SUPERVISOR

set ODI_ENCODED_PASS=d,ypFC5Tzt5plXN82JwXASAUp

You might want to change the password for REPOMTR user or the SUPERVISOR user.

1. On the ODI machine, open a command prompt, and use the CD command to change to the <Install Directory>\oracledi\agent\bin\directory.

2. Enter the following command: ./encode.sh <password in plain text> Where <password> is either REPOMTR or SUPERVISOR’s password The command returns an encoded password for REPOMTR or SUPERVISOR and displays it on screen.

3. Copy the encoded password.

4. Open the file <Install Directory>\oracledi\agent\bin\odiparams.bat/.sh in a text editor.

5. If you obtained a new encoded password for the REPOMTR user, type in or paste in the encoded password that you obtained in step 3 as the value of the set 'ODI_SECU_ENCODED_PASS=' parameter.

6. If you obtained a new encoded password for the SUPERVISOR user, enter the encoded password (obtained in step 3) as the value of the 'set ODI_ENCODED_PASS=' parameter.

7. Save the file.

Changing the Password for the ODI SUPERVISOR User

This section explains how to change the ODI SUPERVISOR password.

1. Log into Oracle Data Integrator Designer or Oracle Data Integrator Topology Manager.

2. Choose File > Change Password to display the Password change dialog box.

3. Use the Password change dialog box to specify the current password and the new password.

4. Save the details.

You now need to modify the ODI Connections to use the new SUPERVISOR password.

Using Different Schema and Tablespace Names

This section explains the changes necessary when using different schema and tablespace names.

Changing the Oracle Tax Analytics Schema Names

At time of the release of this document, schema names must follow the out-of-box naming convention

Changing the Tablespace Names

The tablespace for tables and indexes can be modified after the installation is complete and verified.

To change the tablespace, create new tablespace and use Oracle “move” command to move the objects to the new tablespace. Oracle's export/import or datapump utilities may also be used move the objects. Refer to Oracle Database Documentation Library for more details.

Deploying Oracle Data Integrator Across Multiple Environments

In Oracle Data Integrator deployments, you typically maintain different environments (known as Contexts) for Production (PROD), Development (DEV) and Quality Assurance (QA) activities. Oracle recommends that you install multiple Oracle Data Integrator Repositories and create Topologies to support multiple environments.

To avoid collision between different environments, it is also recommended that you install Oracle Data Integrator separately on different servers for each of the environments.

Note: For detailed information about ODI Contexts, refer to the Oracle Data Integrator Documentation Library.

Running an Oracle Data Integrator Agent as a Unix Background Process

To run an ODI Agent as a Unix background process:

1. Open a command window and change directory to the <Install Directory>\oracledi\agent\bin\ directory.

2. Execute: ./agent.sh -NAME=OTDM_AGENT_1 -PORT=20000 &

Uninstalling ODI Agent Windows Services

If you have a problem with the Oracle Data Integrator Agent processes, you might need to uninstall the services so that you can reinstall them. To uninstall the Oracle Data Integrator Agent service:

1. Display the Windows Services dialog. For example, run 'services.msc' from the Windows > Run dialog.

2. Stop the service OracleDI Agent.

3. Open a command window and change directory to the $ODI_HOME\oracledi\bin directory.

4. Execute the following command agentservice -r -s OTDM_AGENT_1 9000

If required, you can now reinstall the services. For more information about installing these services, see Starting the ODI Agent.

Resolving Conflicts in Oracle Data Integrator Agent Port Numbers

This section explains how to modify your Oracle Tax Analytics deployment to resolve conflicting port numbers for Oracle Data Integrator Agents.

Context for the current task

1. Modify the port number of the OTDM_AGENT_1 agent, as described in Setting up the ODI Agent.

2. Uninstall the ODI Agents, as described in Uninstalling ODI Agent Windows Services.

3. Re-install the ODI Agents using the new port numbers, as described in Setting up the ODI Agent.

List of Log Files

The Oracle Tax Analytics Installer generates the following log files in the <install_dir>\TA\log directory:

Table 1. Log Files

Name

Description

install.log

Main installation log

License and Copyright Notices

License and Copyright notices for associated products:

Third Party Products

Notice concerning usage of Apache Software

The following are covered under the Apache 2.0 license.

1. commons-cli-1.2.jar

2. log4j-1.2.9.jar

Apache License

Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this

License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

License and Copyright Notices A-1

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a

Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and

You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such

License and Copyright Notices

NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or,

within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

Table of Contents

Cover Page

Legal Notices

Preface

Oracle Tax Analytics Installation Overview

Oracle Tax Analytics in Brief

Oracle Tax Analytics Architecture Overview

Architecture Components

Hardware and Software Requirements

Introduction to Oracle Tax Analytics Installation

Install Components

Oracle Tax Analytics Installer Directory Structure

Overview of the Installation Process

Installing Oracle Tax Analytics

Pre-Installation Tasks

Verifying Required Software

Changing the Default Value for the Maximum Processes Initialization Parameter

Disabling the Data Vault Option

Create Recommended Tablespaces

Create Required Users

Updating the Installer Properties File

Installer Execution

Setting Up Environment Variables

Launching the Installer

Understanding Installer Options

Installing Oracle Tax Analytics ODI Repositories

Installing Oracle Tax Data Model Schema

Post Installation Steps

Re-Enabling the Vault Option on the Database

Ensuring That Oracle Tax Data Model Schema Objects Are Valid

Verifying the Value of PGA_AGGREGATE_TARGET

Refresh “GET_SCHEMA_NAME” variable

Generating the ODI Scenarios

Installing OBIEE Components

Deploying Oracle Tax Analytics Components to Oracle Business Intelligence Enterprise Edition

Adding OBIEE Users

Refreshing User GUID

Adding TNSNAMES.ora Entry

Oracle Tax Analytics-Oracle Data Integrator Component Setup

Installing Oracle Data Integrator Software

Configuring the Oracle Data Integrator Parameter File

Updating OTDM_AGENT_1 using ODI Topology Manager

Starting the Oracle Data Integrator Agent

Verifying the Oracle Tax Analytics Installation

Verifying Oracle Tax Analytics Installation and Set Up

Verifying Reports with Oracle Business Intelligence Enterprise Edition

Miscellaneous and Supporting Tasks

Resetting the Default Passwords, Schema Names, and Oracle Data Integrator Connection Details

Changing Default Database Passwords

Changing the Oracle Data Integrator Topology Connection Details

Changing Encoded Passwords in odiparams.bat

Changing the Password for the ODI SUPERVISOR User

Using Different Schema and Tablespace Names

Deploying Oracle Data Integrator Across Multiple Environments

Running an Oracle Data Integrator Agent as a Unix Background Process

Uninstalling ODI Agent Windows Services

Resolving Conflicts in Oracle Data Integrator Agent Port Numbers

List of Log Files

License and Copyright Notices