Oracle Financial Services Data Integration...This section provides supporting information for the...

Oracle Financial Services Data Integration

Installation and Configuration Guide

Release 8.1.0.0.0

October 2020

F31716-01

ORACLE FINANCIAL SERVICES DATA INTEGRATION INSTALLATION AND CONFIGURATION GUIDE | 2

Oracle Financial Services Data Integration Installation and Configuration Guide

Copyright © 2021 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 is software or related documentation that is delivered to the U.S. Government or anyone

licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated

software, any programs installed on the hardware, and/or documentation, delivered to U.S.

Government end users are “commercial computer software” pursuant to the applicable Federal

Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,

disclosure, modification, and adaptation of the programs, including any operating system, integrated

software, any programs installed on the hardware, and/or documentation, shall be subject to license

terms and license restrictions applicable to the programs. No other rights are granted to the U.S.

Government.

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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable

agreement between you and Oracle.

For information on third party licenses, click here.

http://www.google.com/http://www.google.com/http://www.google.com/http://www.google.com/https://docs.oracle.com/cd/E61555_01/licensing.htmhttps://docs.oracle.com/cd/E61555_01/licensing.htm


Document Control

Table 1: Document Version Control

Version Number Revision Date Change Log

1.2 October 20202 Updated sections Upgrade from OFSDI v8.0.6.0.0 or a later

version to OFSDI v8.1.0.0.0 in Upgrade for alter table

configuration query.

1.1 August 2020 Added information for the mandatory one-off patch

31605076 and 31545589 in the Download the OFS DI

Applications Pack Installer and Extract the Software sections.

1.0 June-2020 Created the document with instructions for the installation of

the OFS DI Release 8.1.0.0.0.


Table of Contents

1 Preface .................................................................................................................................... 7

1.1 Audience ................................................................................................................................................................................ 7

1.2 Access to Oracle Support ................................................................................................................................................... 7

1.3 Related Documents ............................................................................................................................................................. 7

1.4 Conventions .......................................................................................................................................................................... 8

1.5 Abbreviations ........................................................................................................................................................................ 9

Part I .............................................................................................................................................. 11

2 Introduction........................................................................................................................... 12

2.1 Oracle Financial Services Analytical Applications Infrastructure (OFS AAI) ......................................................... 13

2.1.1 Components of OFSAA Infrastructure ..................................................................................................................... 13

2.1.2 OFSAA Infrastructure High Availability ................................................................................................................... 13

2.1.3 Deployment Topology ................................................................................................................................................ 14

2.2 About the Oracle Financial Services Data Integration Application Pack .............................................................. 14

2.3 Installation Overview .......................................................................................................................................................... 15

2.4 OFS AAI Extension Pack ....................................................................................................................................................16

2.5 Installation and Upgrade Scenarios ................................................................................................................................16

3 Complete Installation Checklist ........................................................................................... 19

4 Pre-installation ..................................................................................................................... 21

4.1 Hardware and Software Requirements .......................................................................................................................... 21

4.1.1 License Information ..................................................................................................................................................... 21

4.1.2 Verify the System Environment ................................................................................................................................ 22

4.2 Create the Installation, Download, and Metadata Directories ................................................................................. 22

4.3 Preparing for Installation .................................................................................................................................................. 22

4.3.1 Download the OFS DI Application Pack Installer and Mandatory Patches .................................................... 23

4.4 Extract the Software .......................................................................................................................................................... 24

4.4.1 Prerequisites for Installation ..................................................................................................................................... 24

5 Installation............................................................................................................................. 25

5.1 Configure the OFS_DI_PACK.xml File ........................................................................................................................... 25

5.2 Configure the Schema Creator Utility ........................................................................................................................... 27


5.2.1 Prerequisites.................................................................................................................................................................. 28

5.2.2 Configure the Schema Creator Utility for RDBMS Installation .......................................................................... 28

5.2.3 Configure the Schema Creator Utility for HDFS Schema.................................................................................... 36

5.3 Execute the Schema Creator Utility ............................................................................................................................... 45

5.3.1 Execute the Schema Creator Utility in Offline Mode ........................................................................................... 45

5.3.2 Execute the Schema Creator Utility in Online Mode ............................................................................................ 48

5.3.3 Execute the Schema Creator Utility in TCPS Mode .............................................................................................. 50

5.3.4 Execute the Schema Creator Utility while Installing Subsequent Applications Pack ................................... 53

5.4 Verify the Schema Creator Log Files ............................................................................................................................. 55

5.5 Configure the OFSAAI_InstallConfig.xml File .............................................................................................................. 55

5.5.1 Set Up the SFTP Private Key ...................................................................................................................................... 61

5.6 Configure the Silent.props file ........................................................................................................................................ 62

5.7 Install the OFSDI Application Pack ................................................................................................................................. 62

5.8 Install OFSDI Application Pack v8.1.0.0.0 on an Existing OFSAA Instance .......................................................... 67

6 Post-installation .................................................................................................................. 68

6.1 Verify the Log File Information ....................................................................................................................................... 68

6.2 Backup the Schema Creator XML files, OFS_DI_SCHEMA_OUTPUT.xml, and Silent.props Files .................. 68

6.3 Importing ODI Artifacts ..................................................................................................................................................... 69

6.4 Start the DI Services ............................................................................................................................................................ 71

6.5 Map the Application DI User (or Users) to User Group .............................................................................................. 71

Part II ............................................................................................................................................ 73

7 Upgrade ................................................................................................................................ 74

7.1 Upgrade Scenarios ............................................................................................................................................................. 74

7.2 Prepare for Upgrade .......................................................................................................................................................... 74

7.3 Upgrade from Release v8.0.x of OFSDI or OFSDI on AIX or Solaris x86 Operating System............................ 75

7.4 Upgrade from OFSDI v8.0.6.0.0 or a later version to OFSDI v8.1.0.0.0 ................................................................ 75

7.5 Clone Your Existing Environment .................................................................................................................................. 76

7.6 Update the OFS_DI_PACK.xml File ................................................................................................................................ 76

7.7 Update the Silent.props File in Release 8.1.0.0.0 Pack ............................................................................................. 78

7.8 Trigger the Upgrade Installation .................................................................................................................................... 78

7.9 Verify the Log File Information ........................................................................................................................................ 81

7.10 Post-installation Steps ...................................................................................................................................................... 82


Part III .......................................................................................................................................... 83

8 Additional Configuration .................................................................................................... 84

9 Frequently Asked Questions (FAQs) and Error Dictionary ............................................... 85

PREFACE

AUDIENCE


1 Preface

This section provides supporting information for the Oracle Financial Services Data Integration (OFS

DI) Application Pack Installation Guide.

You can find the latest copy of this document in the OHC Documentation Library which includes all

the recent additions or revisions (if any) done to date.

Before you begin the installation, ensure that you have access to Oracle Support with the required

login credentials to quickly notify us of any issues at any stage.

1.1 Audience

The OFS DI Installation Guide is intended for administrators, business users, strategists, data analysts,

and implementation consultants who are responsible for installing and maintaining the application

pack components.

This document assumes that you have experience installing Enterprise components and basic

knowledge of the following:

• Oracle Financial Services Data Integration Application Pack components

• OFSAA architecture

• UNIX commands

• Database concepts

• Web server or web application server

1.2 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.

1.3 Related Documents

We strive to keep this and all other related documents updated regularly; visit the OHC

Documentation Library to download the latest version available there. The list of related documents is

provided here.

• OHC Documentation Library for OFS Data Integration:

▪ OFS Data Integration Hub User Guide Release 8.1.0.0.0

▪ Oracle Financial Services Data Integration User Guide Release

▪ Data Foundation Integration With Fusion Accounting Hub Cloud

▪ Insurance Data Foundation Integration With Fusion Accounting Hub Cloud

▪ Oracle Financial Services Analytical Application-DRM Interface User Guide Release

https://docs.oracle.com/cd/F31776_01/get_started.htmhttp://support.oracle.com/http://www.oracle.com/pls/topic/lookup?ctx=acc&id=infohttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trshttps://docs.oracle.com/cd/F31776_01/get_started.htmhttps://docs.oracle.com/cd/F31776_01/get_started.htmhttps://docs.oracle.com/cd/F31776_01/get_started.htmhttps://docs.oracle.com/cd/E92630_01/PDF/8.0.7.0.0/OFS_Data_Foundation_Integration_With_Fusion_Accounting_Hub_Cloud_8.0.7_User_Guide.pdfhttps://docs.oracle.com/cd/E92630_01/PDF/8.0.7.0.0/Oracle_Insurance_Data_Foundation_Integration_With_Fusion_Accounting_Hub_Cloud_8.0.7_User_Guide.pdf

PREFACE

CONVENTIONS


▪ Oracle Financial Services Analytical Application-OBP Interface User Guide Release

▪ Oracle Financial Services Analytical Application-FAH Interface User Guide Release

▪ Oracle Financial Services Analytical Application-FCUBS Interface User Guide Release

▪ Oracle Financial Services Data Integration Security Guide

▪ Oracle Financial Services Data Integration Cloning Guide

• OHC Documentation Library for OFS AAAI Application Pack:

▪ OFS Advanced Analytical Applications Infrastructure (OFS AAAI) Application Pack

Installation and Configuration Guide

▪ OFS Analytical Applications Infrastructure User Guide

▪ OFS Analytical Applications Infrastructure Administration Guide

▪ Oracle Financial Services Analytical Applications Infrastructure Environment Check

Utility Guide

• Additional documents:

▪ OFSAA Licensing User Manual, Release 8.1.0.0.0

▪ OFS DI Cloning Guide Release 8.0.x

▪ OFS DI Cloning Guide Release 8.1.x

▪ OFS Analytical Applications Infrastructure Security Guide

▪ OFSAAI FAQ Document

▪ OFS Analytical Applications 8.1.0.0.0 Technology Matrix

▪ Oracle Financial Services Analytical Applications Infrastructure Cloning Guide

1.4 Conventions

The following text conventions are used in this document.

Table 2: Document 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, file names, text that appears on the screen, or text that you

enter.

Hyperlink Hyperlink type indicates the links to external websitesand internal

document links.

https://docs.oracle.com/cd/F29631_01/get_started.htmhttps://docs.oracle.com/cd/E61555_01/licensing.htmhttps://docs.oracle.com/cd/E61555_01/licensing.htmhttps://docs.oracle.com/cd/E92630_01/otherguides.htmhttps://docs.oracle.com/cd/F31776_01/otherguides.htmhttp://docs.oracle.com/cd/E61555_01/books/OFSAAI_Security_Guide.pdfhttp://docs.oracle.com/cd/E61555_01/books/OFSAAI_Security_Guide.pdfhttp://docs.oracle.com/cd/E61555_01/books/OFSAAI%20FAQs/WebHelp/OFSAA_FAQs.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttps://docs.oracle.com/cd/E61555_01/homepage.htmhttps://docs.oracle.com/cd/E61555_01/homepage.htm

PREFACE

ABBREVIATIONS


1.5 Abbreviations

The following table lists the abbreviations used in this document.

Table 3: Abbreviations

Conventions Description

AIX Advanced Interactive Executive

BDP Big Data Processing

DBA Database Administrator

DDL Data Definition Language

DEFQ Data Entry Forms and Queries

DIH Data Integration Hub

ODI Oracle Data Integrator

ADI Application Data Interface

KM Knowledge Module

DML Data Manipulation Language

EAR Enterprise Archive

EJB Enterprise JavaBean

ERM Enterprise Resource Management

FTP File Transfer Protocol

HDFS Hadoop Distributed File System

HTTPS Hypertext Transfer Protocol Secure

J2C J2EE Connector

J2EE Java 2 Enterprise Edition

JDBC Java Database Connectivity

JDK Java Development Kit

JNDI Java Naming and Directory Interface

JRE Java Runtime Environment

JVM Java Virtual Machine

LDAP Lightweight Directory Access Protocol

LHS Left Hand Side

MFA Multi-Factor Authentication

MOS My Oracle Support

OFSAA Oracle Financial Services Analytical Applications

OFSAAI Oracle Financial Services Analytical Application Infrastructure

PREFACE

ABBREVIATIONS


Conventions Description

OFSAAAI Oracle Financial Services Advanced Analytical Applications Infrastructure

Application Pack

OFS DI Oracle Financial Services Data Integration

OHC Oracle Help Center

OLAP On-Line Analytical Processing

OLH Oracle Loader for Hadoop

ORAAH Oracle R Advanced Analytics for Hadoop

OS Operating System

RAM Random Access Memory

RDBMS Relational Database Management System

RHEL Red Hat Enterprise Linux

SFTP Secure File Transfer Protocol

SID System Identifier

SSL Secure Sockets Layer

TDE Transparent Data Encryption

TNS Transparent Network Substrate

URL Uniform Resource Locator

VM Virtual Machine

WAR Web Archive

XML Extensible Markup Language

PREFACE

ABBREVIATIONS


Part I Topics:

• Pre-installation

• Installation

• Post-installation

INTRODUCTION

ABBREVIATIONS


2 Introduction

In today's turbulent markets, financial institutions require a better understanding of their risk-return,

while strengthening competitive advantage and enhancing long-term customer value. Oracle

Financial Services Analytical Applications (OFSAA) enable financial institutions to measure and meet

risk-adjusted performance objectives, cultivate a risk management culture through transparency,

lower the costs of compliance and regulation, and improve insight into customer behavior.

OFSAA uses industry-leading analytical methods, shared data models, and applications architecture to

enable integrated risk management, performance management, customer insight, and compliance

management. OFSAA actively incorporates risk into decision making, enables to achieve a consistent

view of performance, promote a transparent risk management culture, and provide pervasive

intelligence.

Oracle Financial Services Analytical Applications delivers a comprehensive, integrated suite of

financial services analytical applications for both banking and insurance domains.

The following figure depicts the various application packs that are available across the OFSAA Banking

and Insurance domains.

Figure 1: Application Packs of OFSAA

INTRODUCTION

ORACLE FINANCIAL SERVICES ANALYTICAL APPLICATIONS INFRASTRUCTURE (OFS AAI)


2.1 Oracle Financial Services Analytical Applications Infrastructure (OFS AAI)

Oracle Financial Services Analytical Applications Infrastructure (OFS AAI) powers the Oracle Financial

Services Analytical Applications family of products to perform the processing, categorizing, selection

and manipulation of data and information required to analyze, understand and report on specific

performance, risk, compliance and customer insight issues by providing a strong foundation for the

entire family of Oracle Financial Services Analytical Applications across the domains of Risk,

Performance, Compliance and Customer Insight.

2.1.1 Components of OFSAA Infrastructure

The OFSAA Infrastructure includes frameworks that operate on and with the Oracle Financial Services

Analytical Applications Data Model and forms the array of components within the Infrastructure.

The OFSAA Infrastructure components/frameworks are installed as two layers; primarily, the

metadata server and Infrastructure services run on one layer, while the UI and presentation logic run

on the other. The UI and presentation layer is deployed on any of the supported J2EE Servers.

The following figure depicts the various frameworks and capabilities that make up the OFSAA

Infrastructure.

Figure 2: Components of OFSAAI

2.1.2 OFSAA Infrastructure High Availability

The current release of the OFSAA Infrastructure supports only the "Single Instance" installation for the

Infrastructure components. However, the High Availability (HA) for the Database Server and/ or the

Web application server clustering and deployment is supported in this release.

INTRODUCTION

ABOUT THE ORACLE FINANCIAL SERVICES DATA INTEGRATION APPLICATION PACK


This release supports the Active-Passive model of implementation for OFSAAI components. For more

information, see Oracle Financial Services Analytical Applications Configuration for High Availability

Best Practices Guide.

2.1.3 Deployment Topology

The following figure illustrates the deployment topology of OFSAA application packs.

Figure 3: Logical Architecture Implemented for OFSAA Application Packs

2.2 About the Oracle Financial Services Data Integration Application Pack

Oracle Financial Services Data Integration (OFS DI) helps financial services institutions loading data

from multiple sources via logical interfaces. OFS DI Application Pack includes the following

application:

• Financial Services Data Integration Hub: Data Integration Hub (DIH) enables to load the data

from the source systems to the OFSAA staging tables, through logical interfaces, known as

Application Data Interfaces (ADI). DIH provides a set of User Interfaces (UI), which is used to

define and maintain External Data D (EDD), Application Data Interfaces, and also map the EDDs

and ADIs through Connectors. The mappings can be one to one, one to many, many-to-many,

and many to one.

• Accounting Hub Cloud Service (AHCS): AHCS is an accounting integration and reporting

platform in oracle cloud that includes products, such as sub-ledger Accounting, Ledger, and

Financial Reporting Center. AHC is an accounting integration platform. It standardizes the

accounting from multiple third-party transactional systems to consistently enforce accounting

policies and meet multiple reporting requirements in an automated and controlled fashion. AHC

includes a rules repository to centrally define and maintain accounting rules, a rules

transformation engine to create, validate and store the accounting journals, and a detailed

accounting repository that is used to reconcile to the source system.

https://docs.oracle.com/cd/E61555_01/books/8.1.x/OFSAA_Config_High_Availability_Best_Practices_Guide_8.1.x.pdfhttps://docs.oracle.com/cd/E61555_01/books/8.1.x/OFSAA_Config_High_Availability_Best_Practices_Guide_8.1.x.pdf

INTRODUCTION

INSTALLATION OVERVIEW


• Financial Services Oracle FLEXCUBE Universal Banking (FCUBS) Interface: Oracle

FLEXCUBE Universal Banking (FCUBS) supports the changing landscape of retail, corporate,

and investment banking needs with strong transaction banking and Islamic banking

capabilities. The current FCUBS-OFSAA interfaces transfer all key data elements across various

modules within FCUBS to OFSAA Common Staging Area (CSA). The integration between the

Oracle FCUBS and the OFSAA enables the financial institutions to:

▪ Get insight into customer patterns based on the data captured in core banking.

▪ Achieve end-to-end improvement in business delivery.

▪ Achieve effective performance and risk-free management using the available customer

data.

▪ This integration is achieved by handing off FCUBS core banking data with OFSAA

through FLEXCUBE Information Server (FIS) and DIH.

• Financial Services Oracle Banking Platform (OBP) Interface:

▪ Oracle Business Platform (OBP) is designed to help banks respond strategically to

today's business challenges and progressively transform their business models through

industrialized business processes, driving productivity improvements across front and

back offices, and reducing operating costs.

▪ It supports banks' growth agenda through new distribution strategies including multi-

brand or white labeling to tap new markets and enterprise product origination

supporting multi-product and packages to drive an increased customer-to-product

ratio.

• Financial Services Data Relationship Management (DRM) Interface: Oracle Data

Relationship Management (DRM) helps proactively manage changes in master data across

operational, analytical, and enterprise performance management silos. Users may make

changes in their departmental perspectives while ensuring conformance to enterprise

standards.

2.3 Installation Overview

To install an OFS DI application pack 8.1.0.0.0 instance, users and administrators must download this

installer. The following figure displays the order of procedures you will need to follow to install a new

OFS DI Pack 8.1.0.0.0 instance.

NOTE This installer supports both upgrade and fresh installation of OFS DI 8.1.0.0.0.

Figure 4: Installation Flow

INTRODUCTION

OFS AAI EXTENSION PACK


2.4 OFS AAI Extension Pack

The Oracle Financial Services Analytical Applications Infrastructure Extension (OFS AAIE) Pack adds a

set of new advanced features for 8.1.0.0.0 Release across OFSAA applications. This pack can be

installed on an OFSAA instance having one or more OFSAA application packs.

The Oracle Financial Services Analytical Applications Infrastructure Extension Pack includes the

following advanced features and functionalities:

• Distributed Processing Capabilities

• Analytic Pipeline and Process models

• Attribution Analysis

• Content Management Interoperability Services

NOTE The pack is enabled by procurement of an additional license. For more information, see the OFS AAIE Release Notes and Installation Guide on the OHC.

2.5 Installation and Upgrade Scenarios

Release v8.1.0.0.0 of OFSDI Application Pack supports various installation and upgrade scenarios. A

high-level overview of the possible scenarios is provided in the following table. Detailed procedural

steps are provided in the succeeding sections of this document.

Table 4: OFSDI Release 8.1.0.0.0 Installation and Upgrade Scenarios

Scenario Installation and Upgrade Instructions

New Installation

https://docs.oracle.com/cd/F29631_01/extension_pack.htm

INTRODUCTION

INSTALLATION AND UPGRADE SCENARIOS



Installing Release 8.1.0.0.0

application pack for the first time

(new installation).

1. Prepare for the Installation.

2. Execute the Schema Creator Utility.

3. Install the OFSDI Application Pack.

4. Perform Post Installation Activities.

Install a new product from OFS DI

8.1.0.0.0 application pack where

another application from the same

application pack is already

installed.

You have installed some applications

from the Release 8.1.0.0.0 pack and

in the future, you decide to include

other applications from the same

pack.

Example: You have installed DI

applications using the DI Pack.

If the schema creator output file (OFS_DI_SCHEMA_OUTPUT.xml)

EXISTS:

1. Update the OFS_DI_PACK.xml file to disable the existing

applications and enable the newly licensed applications.

2. Update the Silent.props file present in the Release 8.1.x pack

ONLY for the newly licensed applications.

3. Trigger the Release 8.1.0.0.0 installation.

If the schema creator output file DOES NOT EXIST:

1. Run the schema creator utility.

ATTENTION: While defining the schema details for the

applications, provide the same schema details given in the previous

installation. The output file (OFS_DI_SCHEMA_OUTPUT.xml) is

generated as a result of the schema creation process.

2. Update the OFS_DI_PACK.xml file to disable the existing

applications and enable the newly licensed applications.

3. Update the Silent.props file.


NOTE: Configuring the OFSAAI_InstallConfig.xml file is not required.

Install OFS DI Application Pack

v8.1.0.0.0 on an Existing OFSAA

Instance

You have already installed an

application pack from release

8.1.x.0.0 and now you want to install

another application pack from

Release 8.1.0.0.0.

Example: OFS ALM Pack is already

installed and now you want to install

OFS DI Pack.

1. Run the schema creator utility ONLY for the new pack.

2. Update the OFS_DI_PACK.xml file for the newly licensed pack.

3. Update the Silent.props file of the newly licensed pack.


Upgrade Installation

Upgrade from Release v8.0.x of

OFSDI or OFSDI on AIX or Solaris

x86 Operating System

Release v8.1.0.0.0 of OFSDI is not certified for AIX and Solaris x86

Operating Systems. If you are currently running OFSAA v8.0.x on AIX or

Solaris x86 Operating Systems and plan to upgrade to Release v8.1.0.0.0,

then you must migrate from AIX or Solaris x86 to Linux or Solaris SPARC.

See the MOS Doc ID 2700084.1 for details.

Upgrade an already installed

8.0.6.0.0 or later application and

add new applications from the

same pack

You have two applications from a

pack on 8.0.6.0.0 or later. You want

1. Run the Environment Check Utility tool and ensure that the

hardware and software requirements are installed as per the OFS

Analytical Applications Technology Matrix. See the OFSAA

Environment Check Utility Guide for detailed steps.

2. Clone your existing environment to the 8.1.0.0.0 OFS Analytical

Applications Technology Matrix.

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2700084.1http://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFSAA_envCheck_Utility_Guide_8.1.x.pdfhttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFSAA_envCheck_Utility_Guide_8.1.x.pdfhttps://docs.oracle.com/cd/E61555_01/books/OFSAA_Cloning_Reference_Guide_8.0.pdfhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htm

INTRODUCTION




two new applications from the same

pack on 8.1.0.0.0.

Example: You have installed OFSDI

from Release 8.0.6.0.0. Now you

want to install OFSDI of Release

8.1.0.0.0.

3. Run the schema creator utility.

IMPORTANT NOTE: While defining the schema details for the

newly licensed applications, provide the same schema details given

in the previous installation. The output file

(OFS_DI_SCHEMA_OUTPUT.xml) is generated as a result of the

schema creation process.

4. Update the OFS_DI_PACK.xml file to enable ONLY the newly

licensed applications.

5. Update the Silent.props file for the sections related to the

newly licensed applications.

6. Trigger the Release 8.1.0.0.0 installer.

NOTE: Configuring the OFSAAI_InstallConfig.xml file is

not required.

7. This process upgrades the existing applications and installs the

newly licensed applications.

NOTE If you are upgrading the OFSAA Application Pack to release v8.1.0.0.0, you must upgrade the other packs installed in the same environment to release v8.1.0.0.0, to ensure successful deployment.

COMPLETE INSTALLATION CHECKLIST



3 Complete Installation Checklist

For a successful installation, perform the steps listed in the Complete Installation Checklist. You can

use this checklist to have a glance at everything that you will be doing to install this application. The

link provided in each step takes you to a section either within this document or to another referenced

document.

Table 5: Complete Installation Checklist

Sl. No. Pre-installation Activity

1 Install all the prerequisite hardware and software as per the OFS Analytical


• Configure the Database Instance settings.

• Install and configure the web application server.

• Configure the HTTP settings on the web server.

• Configure the following Operating System and File System settings.

• Update the Environment Settings as required for the installation in the

.profile file.

2 Verify the System Environment using the Environment Check Utility.

3 Create all the necessary directories.

4 Download and Extract the OFS DI Application Pack installer kit.

Sl. No. Installation Activity

1 Configure the OFS_DI_PACK.xml file.

2 Configure the OFS_DI_SCHEMA_IN.xml and Configure the

OFS_DI_SCHEMA_BIGDATA_IN.xml file.

3 Execute the Schema Creator Utility in Offline, Online, or TCPS modes and

verify the Schema Creator Log Files.

4 Configure the OFSAAI_InstallConfig.xml file.

5 Configure the Silent.props file.

6 Trigger the OFSDI Application Pack installation.

Sl. No. Post-installation Activity

1 Verify the installation logs.

2 Back up the schema creator XML files, OFS_DI_SCHEMA_OUTPUT.xml,

and Silent.props files.

3 Deploy the EAR or WAR files.

4 Import the ODI Artifacts.

http://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFS_AAAI_Installation_Guide_8.1.0.0.0.pdf#CrtDepEarWar

COMPLETE INSTALLATION CHECKLIST



Sl. No. Post-installation Activity

5 Start DI Service.

6 Access the OFSAA Application to Create Application Users and Map them to DI

User Groups.

https://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFS_AAAI_Installation_Guide_8.1.0.0.0.pdf#AccOFSApphttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFS_AAAI_Installation_Guide_8.1.0.0.0.pdf#CrtAppUsr

PRE-INSTALLATION

HARDWARE AND SOFTWARE REQUIREMENTS


4 Pre-installation

This section contains the pre-installation requirements to install the OFS Data Integration Application

Pack.

You can use this checklist to have a glance at everything that you will be doing before installing this

application. The link provided in each step takes you to a section either within this document or to

another referenced document.

Table 6: Pre-installation Checklist

Sl. No. Pre-installation Activity

1 Install all the prerequisite hardware and software as per the OFS Analytical


• Configure the Database Instance settings.

• Install and configure the web application server.

• Configure the HTTP settings on the web server.

• Configure the following Operating System and File System settings.

• Update the Environment Settings as required for the installation in the

.profile file.

2 Verify the System Environment using the Environment Check Utility.

3 Create all the necessary directories.

4 Download and Extract the OFS DI Application Pack installer kit.

4.1 Hardware and Software Requirements

For a list of all the hardware and software requirements including operating systems, database, web

servers, and web application server versions for which this release of the Oracle Financial Services

Data Integration Application Pack is qualified, see the OFSAA Technology Matrix..

NOTE OFS DI Application Pack installation can be performed on both Virtual and Physical servers.

OFS DI application pack recommends the following software combinations for deployment.

Table 7: Recommended Software Combination

Operating System Database Web Application Server Web Server

Oracle Linux Oracle Database Oracle WebLogic Server/

Apache Tomcat Server

Oracle HTTP Server/

Apache HTTP Server

4.1.1 License Information

For details of the third-party software tools used, see the OFSAA Licensing Information User Manual

Release 8.1.0.0.0.

http://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttp://docs.oracle.com/cd/E55339_01/homepage.htmhttps://docs.oracle.com/cd/E61555_01/licensing.htmhttps://docs.oracle.com/cd/E61555_01/licensing.htm

PRE-INSTALLATION

CREATE THE INSTALLATION, DOWNLOAD, AND METADATA DIRECTORIES


4.1.2 Verify the System Environment

To verify your system environment meets the minimum requirements for the installation, a Pre-Install

Check utility is available within the Install Kit archive file. This utility can also be obtained separately by

contacting Oracle Support.

Though the system environment verification is an integral and automated part of the installation of

this software product, Oracle strongly recommends running this utility before beginning the

installation as part of your organization's "Installation Readiness Verification Process".

For information about the download and usage of this utility, see the Oracle Financial Services

Analytical Applications Infrastructure Environment Check Utility Guide.

4.2 Create the Installation, Download, and Metadata Directories

To install the OFSDI Application Pack, create the following directories:

• OFSDI Download Directory (Optional): Create a download directory and copy the OFSDI

Application Pack Installer File (archive). This is the directory where the downloaded installer or

patches can be copied. Assign 755 permission to this directory.

• OFSAA Installation Directory (Mandatory): Create an installation directory where the product

binaries are installed. Assign 755 user permission to the installation directory. FIC_HOME

variable to be set in the .profile pointing to this OFSAA Installation Directory.

• OFSAA Staging or Metadata Repository Directory (Mandatory): A directory to hold the

application metadata artifacts and additionally act as the staging area for the flat files. This

directory is also referred to as FTPSHARE. Create a Staging or Metadata Repository Directory to

copy data files, save data extracts, and so on.

The directory must exist on the same system as the OFSAA Installation. This directory can be

configured on a different mount or under a different user profile. However, the owner of the

installation directory must have RWX (775) permissions to this directory.

NOTE Ensure the OFSAA staging directory is not set to the same path as the OFSAA installation directory and is not a subdirectory inside the OFSAA installation directory.

• OFSDI Hive Directory (Mandatory for Big Data Installation): Create a directory for the file

system stage area of the Hive server. This is commonly referred to as FTPSHAREH or

HIVE_SERVER_FTPDRIVE. Ensure the user permission is set to 775 on the Installation Directory.

4.3 Preparing for Installation

This section describes how to download the installer and the mandatory prerequisites you must

ensure installing the OFS DI Application Pack.

http://support.oracle.com/https://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFSAA_envCheck_Utility_Guide_8.1.x.pdfhttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFSAA_envCheck_Utility_Guide_8.1.x.pdf

PRE-INSTALLATION

PREPARING FOR INSTALLATION


4.3.1 Download the OFS DI Application Pack Installer and Mandatory Patches

To download the OFS Data Integration Pack Installer Release 8.1.0.0.0, follow these steps:

1. Log in to the Oracle Software Delivery Cloud (OSDC) with a valid Oracle account.

Figure 5: OSDC Login Window

2. Enter Oracle Financial Services Data Integration Application Pack in the search box.

Figure 6: OSDC - Search Results

3. Download the installer archive and copy (in Binary mode) to the download directory that exists

in the OFS DI installation setup.

4. Download the following mandatory one-off patches from My Oracle Support into the download

directory that exists in the OFSAAAI installation setup:

Patch ID Description

31605076 Access to features owing to the additional license functionality that gets installed

through the OFS AAI Extension Pack.

31545589 For pack-on-pack installation on new atomic schema.

https://edelivery.oracle.com/http://support.oracle.com/

PRE-INSTALLATION

EXTRACT THE SOFTWARE


4.4 Extract the Software

You must be logged in to the UNIX operating system as a non-root user to perform the following

steps. To extract the software, follow these steps:

1. If you already have an unzip utility to extract the contents of the downloaded archive, skip this

step. Download the unzip utility (OS-specific) unzip_.Z and copy it in Binary mode to the

directory that is included in your PATH variable.

2. Uncompress the unzip installer file with the following command:

uncompress unzip_.Z

NOTE If an error message uncompress: not found [No such file or directory] is displayed, contact your UNIX administrator.

3. Assign 751 permission to the file with the following command:

chmod 751 unzip_

For example: chmod 751 unzip_sparc

4. Extract the contents of the OFS DI Application Release 8.1.0.0.0 installer archive file in the

download directory with the following command:

unzip OFS_DI_PACK.zip

5. Extract the following one-off patches in the download directory:

a. 31545589

b. 31605076

6. Navigate to the download directory and assign 750 permission to the installer directory with the

following command:

chmod -R 750 OFS DI Pack

4.4.1 Prerequisites for Installation

This installer has Fresh install capabilities and following is the prerequisite to install the OFSDI

Application Pack:

• Oracle Data Integrator Studio Client is installed in the OFSAA instance.

• ODI_HOME variable is set in the environment.

INSTALLATION

CONFIGURE THE OFS_DI_PACK.XML FILE


5 Installation

This section details the steps to be followed during the OFSDI Application Pack installation.

You can use this checklist to have a glance at everything that you will be doing to install this

application. The link provided in each step takes you to a section either within this document or to

another referenced document.

Table 8: Installation Checklist

Sl. No. Installation Activity

1 Configure the OFS_DI_PACK.xml file.

2 Configure the OFS_DI_SCHEMA_IN.xml and Configure the


3 Execute the Schema Creator Utility in Offline, Online, or TCPS modes and

verify the Schema Creator Log Files.

4 Configure the OFSAAI_InstallConfig.xml file.

5 Configure the Silent.props file.

6 Trigger the OFSDI Application Pack installation.

5.1 Configure the OFS_DI_PACK.xml File

The OFS_DI_PACK.xml file contains details on the various products that are packaged in the OFS DI

application pack. This section details the various tags and parameters available in the file and the

values that must be updated. Before installing the DI Application Pack, it is mandatory to update this

file.

To configure the OFS_DI_PACK.xml file, follow these steps:

1. Navigate to the OFS_DI_PACK/conf directory.

2. Open the OFS_DI_PACK.xml file in a text editor.

INSTALLATION

CONFIGURE THE OFS_DI_PACK.XML FILE


Figure 7: Sample OFS_DI_PACK.xml File

3. Configure the OFS_DI_PACK.xml file as mentioned in the following table.

Table 9: OFS_DI_PACK.xml File Parameters

Tag Name or Attribute

Name

Description Mandatory (Y or N) Comments

APP_PACK_ID Unique Application Pack

Identifier

Y Unique Seeded Value

APP_PACK_NAME Unique Application Pack

Name


INSTALLATION

CONFIGURE THE SCHEMA CREATOR UTILITY


Tag Name or Attribute

Name

Description Mandatory (Y or N) Comments

APP_PACK_DESCRIPTION Unique Application Pack

Description


VERSION Unique release version Y Unique Seeded Value

APP Unique Application Entries Y Unique Seeded Value

APP_ID Unique Application Identifier Y Unique Seeded Value

APP_ID/ PREREQ Prerequisite Application/

Product


APP_ID/ DEF_SEL_FLAG Default Selected Flag Y Default value: YES

APP_ID/ ENABLE Enable Application/ Product YES if installing in

SILENT mode.

Default value:

YES for Infrastructure

NO for Others

Permissible value:

YES or NO

Note: The Application/

Product cannot be

disabled once enabled.

Only

Applications/Products

which are enabled are

installed. In order to

install a licensed

Applications/Products,

you need to restart

installation process by

specifying the ENABLE

flag as Y for the

application. The

execution of Schema

Creation Utility must be

skipped.

APP_NAME Unique Application/ Product

Name


APP_DESCRIPTION Unique Application/ Product

Name


VERSION Unique release version Y Unique Seeded Value

4. Save and close the file.

5.2 Configure the Schema Creator Utility

Creating database users or schemas (RDBMS) is one of the primary steps in the complete installation

process. The Schema Creator utility enables you to quickly get started with the installation by creating

INSTALLATION



Database User (or Users) or Schema (or Schemas) (RDBMS), assigning the necessary GRANT (or

GRANTs), creating the required entities in the schemas and so on.

Configure and execute the schema creator utility before installing the OFSAA Application Pack.

5.2.1 Prerequisites

Ensure you have the following before configuring the Schema Creator Utility:

• Oracle User ID or Password with SYSDBA privileges.

• JDBC Connection URL for RAC or Non-RAC database.

• The HOSTNAME or IP of the server on which OFSAA is being installed.

• It is recommended to set the PGA_AGGREGATE_LIMIT database-parameter value sufficiently

when Oracle 18c or 19c is installed.

• You must add a TNS entry before the installation. For details, see the Add TNS entries in the

TNSNAMES.ORA file section.

For HIVE installation, you must also have the following:

• HIVE connection credentials (for example, Kerberos connection properties).

• Hostname or IP of the HIVE Server installation.

5.2.2 Configure the Schema Creator Utility for RDBMS Installation

If the installation is being performed for RDBMS, provide the Pack specific schema details in the

OFS_DI_SCHEMA_IN.xml file.

You can configure the following types of schemas:

• CONFIG: This schema holds the entities and other objects required for OFSAA setup

configuration information. Only one CONFIG schema per OFSAA instance is permitted.

• ATOMIC: This schema holds the data model entities. One ATOMIC schema is attached to one

Information Domain. You can have multiple ATOMIC schemas for a single OFSAA instance.

5.2.2.1 Configure the OFS_DI_SCHEMA_IN.xml File

This section describes how to create database schemas, objects within schemas, and assigning

appropriate grants.

Specify the database schemas required for the installation in the OFS_DI_SCHEMA_IN.xml file.

Update the values of the various tags and parameters available in this file before executing the

schema creator utility.

NOTE This file must be configured only in the case of the OFSDI Application Pack installation for RDBMS ONLY target. This file is not required to be configured for an HDFS ONLY target installation.

To configure the OFS_DI_SCHEMA_IN.xml file, follow these steps:

https://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFS_AAAI_Installation_Guide_8.1.0.0.0.pdf#AdTNSEnthttps://docs.oracle.com/cd/F29631_01/PDF/8.1.0.x/8.1.0.0.0/OFS_AAAI_Installation_Guide_8.1.0.0.0.pdf#AdTNSEnt

INSTALLATION



1. Log in to the system as a non-root user.

2. Navigate to the OFS_DI_PACK/schema_creator/conf/ directory.

3. Delete the file OFS_DI_SCHEMA_BIGDATA_IN.xml.

4. Edit the OFS_DI_SCHEMA_IN.xml file using a text editor.

Figure 8: Sample of the OFS_DI_SCHEMA_IN.xml file

Figure 9: Sample of the OFS_DI_SCHEMA_IN.xml file (APPPACKSCHEMA Block)

5. Configure the values as mentioned in the following table.

NOTE On successful execution of the utility, the passwords entered in the OFS_DI_SCHEMA_IN.xml file are nullified.

INSTALLATION



Table 10: OFS_DI_PACK_SCHEMA_IN.xml file (APPPACKSCHEMA Parameters)

Tag Name or

Attribute Name

Description Mandatory

or Optional

Default Value or Permissible Value Comments

Unique Application Pack Identifier Y Unique Seeded Value DO NOT modify this value.

Enter the JDBC URL.

NOTE: You can enter RAC and NON-RAC

enabled database connectivity URL.

Y Example,

jdbc:oracle:thin:@< DBSERVER IP/HOST/

IP>::

oror

jdbc:oracle:thin:@//[HOST][:PORT]/SERVIC

E

or

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS

_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=

[HOST])(port=[PORT]))(ADDRESS=(PROTOC

OL=TCP)(HOST=[HOST])(PORT=[PORT]))(L

OAD_BALANCE=yes)(FAILOVER=yes))(CON

NECT_DATA=(SERVICE_NAME=[SERVICE])))

For example,

jdbc:oracle:thin:@//dbhost.server.com:1521/

service1

or

jdbc:oracle:thin:@//dbshost.server.com:1521

/scan-1

or

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS

_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=

dbhost1.server.com)(port=1521))(ADDRESS=(

PROTOCOL=TCP)(HOST=dbhost2.server.co

m)(PORT=1521))(LOAD_BALANCE=yes)(FAIL

OVER=yes))(CONNECT_DATA=(SERVICE_NA

ME=service1)))

Ensure to add an entry (with SID

or SERVICE NAME) in the

tnsnames.ora file on the

OFSAA server. The entry must

match with the SID or SERVICE

NAME used in the JDBC URL.

INSTALLATION



Tag Name or

Attribute Name


or Optional


The name of the driver is seeded.

NOTE: Do not edit this attribute value.

Y Example,

oracle.jdbc.driver.OracleDriver

Only JDBC Thin Driver is

supported.

DO NOT modify this value.

Enter the Hostname or IP Address of the system

on which you are installing the OFSAA

components.

Y Host Name or IP Address

/ NAME Enter the acronym for the type of

implementation. This information will be

displayed in the OFSAA Home Page.

NOTE: On executing the schema creator utility,

this value will be prefixed with each schema

name. For example: dev_ofsaaconf,

uat_ofsaaatm.

Y Accepts strings with a minimum length of

two and a maximum of four.

Example, DEV, SIT, PROD

This message appears in the

OFSAA Landing Page as

Connected To: xxxx.

The schemas being created would

get this prefix. For example:

dev_ofsaaconf, uat_ofsaaconf,

and so on.

/

PREFIX_SCHEMA_NAM

E

Identifies if the value specified in

/ NAME attribute must be

prefixed to the schema name.

N YES or NO Default value is YES.

/

APPLYSAMEFORALL

Enter as Y if you want to apply the password

specified in the DEFAULT attribute for all the

schemas.

If you enter as N, you need to provide individual

passwords for all schemas.

NOTE: In case you have entered Y in

APPLYSAMEFORALL attribute and also have

specified individual passwords for all the

schemas, then the specified individual

passwords will take precedence.

Y Default – N

Permissible – Y or N

NOTE: Setting this attribute value

is mandatory If the DEFAULT

attribute is set.

INSTALLATION



Tag Name or

Attribute Name


or Optional


/

DEFAULT*

Enter the password if you want to set a default

password for all schemas.

NOTE: You also need to set the

APPLYSAMEFORALL attribute as Y to apply the

default password for all the schemas.

N The maximum length allowed is 30

characters. Special characters are not

allowed.

/ TYPE The different types of schemas that are

supported in this release are ATOMIC, CONFIG,

SANDBOX, and ADDON.

By default, the schemas types are seeded based

on the Application Pack.

NOTE: Do not edit this attribute value.

Y ATOMIC, CONFIG, SANDBOX, or ADDON

NOTE:

SANDBOX AND ADDON schemas are not

applicable for OFS AAAI Application Pack.

Only One CONFIG schema can

exist in the file.

This schema identifies as the

CONFIGURATION schema that

holds the OFSAA setup details

and other metadata information.

Multiple ATOMIC, SANDBOX,

ADDON schemas can exist in the

file.

ATOMIC schema refers to the

Information Domain schema.

SANDBOX schema refers to the

SANDBOX schema. ADDON

schema refers to another

miscellaneous schema (not

applicable for this Application

Pack).

/ NAME By default, the schema names are seeded based

on the Application Pack.

You can edit the schema names if required.

NOTE:

The Schema Name will have a prefix of the

SETUPINFO/ NAME attribute.

SCHEMA NAME must be the same for all the

ATOMIC Schemas of applications within an

Application Pack.

Y The permissible length is 15 characters and

only alphanumeric characters allowed. No

special characters allowed except underscore

‘_’.

SETUPINFO/ NAME attribute

value would be prefixed to the

schema name being created.

For example. if the name is set as

‘ofsaaatm’ and setupinfo as ‘uat’

then schema being created would

be ‘uat_ofsaaatm’.

NAME must be the same where

APP_GRP=1 for all SCHEMA tags

(Not applicable for this

Application Pack).

INSTALLATION



Tag Name or

Attribute Name


or Optional


/

PASSWORD*

Enter the password of the schema to be created.

NOTE:

If this attribute is left blank, then the password

specified in the /DEFAULT

attribute is applied as the Schema Password.



allowed.

NOTE: You need to mandatorily

enter the password if you have set

the /

APPLYSAMEFORALL attribute as

N.

/ APP_ID By default, the Application ID is seeded based on

the Application Pack. NOTE: Do not modify this

attribute value.

Y Unique Seeded Value Identifies the Application or

Product for which the schema is

being created.


/

DEFAULTTABLESPACE

Enter the available default tablespace for DB

User.

NOTE: If this attribute is left blank, then USERS

is set as the default tablespace.

N Default value: USERS

Permissible value: Any existing valid

tablespace name.

Modify this value to associate any

valid tablespace with the schema.

/

TEMPTABLESPACE

Enter the available temporary tablespace for the

DB User.

NOTE: If this attribute is left blank, then TEMP is

set as the default tablespace.

N Default value: TEMP


temporary tablespace name.

Modify this value to associate any

valid tablespace with the schema.

/ QUOTA Enter the quota to be set on the

DEFAULTTABLESPACE attribute for the schema

or user. By default, the quota size is set to 500M.

Minimum: 500M or Unlimited on default

Tablespace

N Example:

600M/m

20G/g

UNLIMITED/unlimited

Modify this value to grant the

specified quota on the mentioned

tablespace to the user.

/

INFODOM

Enter the name of the Information Domain to

associate this schema.

The schema creator utility automatically derives

an Information Domain Name based on the

Application Pack if no value is specified for this

attribute.

N

(Optional for

Atomic and

mandatory

for

SANDBOX)

Permissible length is 16 characters and only

alphanumeric characters allowed. No special

characters allowed.

Enter this field in UPPERCASE.

If DI media pack is first media

pack installation in the setup, then

INFODOM must be specified

mandatorily otherwise it is

optional.

INSTALLATION



Tag Name or

Attribute Name


or Optional


Parent tag to hold Advance Security Options. N Uncomment the tag and edit if

you want to add security options.

For example, TDE and Data

Redact.

For details, see the example

following the table.

/TDE

Tag to enable or disable TDE. N Default is FALSE. To enable TDE, set this to

TRUE.

Ensure this tag is not commented

if you have uncommented

.

/ DATA_REDACT

Tag to enable or disable the Data Redaction

feature.

N Default is FALSE. To enable DATA_REDACT,

set this to TRUE

Ensure this tag is not commented

if you have uncommented

.

Parent tag to hold elements N NA Uncomment the tag and edit.

ONLY if tablespaces are to be

created as part of the installation.

For details, see the example

following the table.

NOTE: When TDE is TRUE in

ADV_SEC_OPTIONS, it is

mandatory for the

tag to be

present in the XML file.

/

NAME

Logical Name of the tablespace to be created. Y Name if specified must be

referred in the attribute.

NOTE the ## syntax.

INSTALLATION



Tag Name or

Attribute Name


or Optional


/

VALUE Physical Name of the tablespace to be created Y NA Value if specified will be the actual

name of the TABLESPACE.

/

DATAFILE

Specifies the location of the data file on the

server Y NA Enter the absolute path of the file

to be created.

/

AUTOEXTEND

Specifies if the tablespace must be extensible or

have a hard limit Y ON or OFF Set to ON to ensure that the

tablespace does not run out of

space when full.

/

ENCRYPT

Specifies if the tablespace (or tablespaces) must

be encrypted using TDE. Y ON or OFF Set to ON to ensure that the

tablespaces when created are

encrypted using TDE.

INSTALLATION



5.2.3 Configure the Schema Creator Utility for HDFS Schema

To install for Big Data, provide the Pack specific schema details in the


The types of schemas that you can configure are:

• CONFIG: This schema holds the entities and other objects required for OFSAA setup

configuration information. Only one CONFIG schema per OFSAA instance is permitted. This

schema is created only in RDBMS.

• METADOM: This schema holds the data model entities. One METADOM schema is attached to

one Information Domain. You can have multiple DATADOM schemas for a single OFSAA

instance. This schema is created only in RDBMS. It has only platform entities that hold the

metadata details. However, it does not hold the data model entities.

• DATADOM: This schema holds data model entities. One DATADOM schema is attached to one

Information Domain. You can have multiple DATADOM schemas for a single OFSAA instance.

5.2.3.1 Configure the OFS_DI_SCHEMA_BIGDATA_IN.xml File

To create Hive schemas and objects within for the various application schemas, update the values of

the various tags and parameters available in the OFS_DI_SCHEMA_BIGDATA_IN.xml file before

executing the schema creator utility.

NOTE This file must be configured only in case of the OFSDI Application Pack installation for the HDFS ONLY target. This file configuration is not required for an RDBMS ONLY target installation.

To configure the OFS_DI_SCHEMA_BIGDATA_IN.xml file, follow these steps:


2. Navigate to the OFS_DI_PACK/schema_creator/conf/ directory.

▪ Delete OFS_DI_SCHEMA_IN.xml.

3. Edit the OFS_DI_SCHEMA_BIGDATA_IN.xml file using a text editor and configure the values as

mentioned in the following table.

INSTALLATION



Figure 10: Sample of the OFS_DI_BIGDATA_SCHEMA_IN.xml file

INSTALLATION



Table 11: OFS_DI_BIGDATA_SCHEMA_IN.xml file (APPPACKSCHEMA Parameters)

Tag Name/ Attribute

Name


(Y/N)

Default Value/ Permissible Value Comments

Seeded unique ID for the

OFSAA Application Pack.

Y Seeded DO NOT modify this value.

Enter the JDBC URL.

NOTE: You can enter the RAC/

NON-RAC enabled database

connectivity URL.

Y Example,

jdbc:oracle:thin:@::

or

jdbc:oracle:thin:@//[HOS

T][:PORT]/SERVICE

or

jdbc:oracle:thin:@(DESCRI

PTION=(ADDRESS_

LIST=(ADDRESS=(PROT

OCOL=TCP)(HOST=[HO

ST])(port=[PORT]))(ADD

For an HDFS ONLY target installation, this URL

must be of the RDBMS instance that hosts the

Application’s METADOM.

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


RESS=(PROTOCOL=TCP)

(HOST=[HOST])(PORT=[ PORT]))(LOAD_

BALANCE=yes)(FAILOV

ER=yes))(CONNECT_ DATA=(SERVICE_

NAME=[SERVICE])))

For example, jdbc:oracle:thin:@//dbhos

t.server.com:1521/service 1

or

jdbc:oracle:thin:@//dbsho

st.server.com:1521/scan-1

or

jdbc:oracle:thin:@(DESCRI

PTION=(ADDRESS_

LIST=(ADDRESS=(PROT

OCOL=TCP)(HOST=dbho

st1.server.com)(port=1521)

)(ADDRESS=(PROTOCO

L=TCP)(HOST=dbhost2.s

erver.com)(PORT=1521))( LOAD_

BALANCE=yes)(FAILOV

ER=yes))(CONNECT_ DATA=(SERVICE_

NAME=service1)))

By default, this driver name is

seeded.

NOTE: Do not modify this

attribute value.

Y Example,

oracle.jdbc.driver.OracleD river

Only JDBC Thin Driver is supported.


Enter the Hostname or IP

Address of the system on which

you are installing the OFSAA

components.

Y Host Name or IP Address

/ PREFIX_

SCHEMA_ NAME

Identifies if the value specified

in/ NAME

attribute must be prefixed to

the schema name.

N YES or NO Default value is YES.

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


/ NAME Enter the acronym for the type

of implementation. This

information will be displayed in

the OFSAA Home Page.

NOTE: On executing the

schema creator utility, this

value will be prefixed with each

schema name. For example,

dev_ ofsaaconf, uat_ofsaaatm.

Y Accepts strings with a minimum length of

two and a maximum of four.

For example,

DEV, SIT, PROD

This message appears in the OFSAA Landing

Page as Connected To: xxxx.

The schemas being created would get this

prefix. For example, dev_ ofsaaconf,

uat_ofsaaconf, and so on.

/ DEFAULT* Enter the password if you want

to set a default password for all

schemas.

NOTE: You also need to set the

APPLYSAMEFORALL attribute

as Y to apply the default

password for all the schemas.



allowed.

Applies only to the RDBMS type METADOM

schema (or schemas).

/

APPLYSAMEFO RALL

Enter as Y if you want to apply

the password specified in the

DEFAULT attribute for all the

schemas.

If you enter as N, you need to

provide individual passwords

for all schemas.

NOTE: If you have entered Y in

APPLYSAMEFORALL attribute

and also have specified

individual passwords for all the

schemas, then the specified

individual passwords will take

precedence.

Y Default - N Permissible - Y or N NOTE: Setting this attribute value is mandatory

If the DEFAULT attribute is set.

Applies only to the RDBMS type METADOM

schema (or schemas).

/ TYPE=RDBMS Identifies the RDBMS schema

details.

Y Default names for schemas within the pack

would be derived in absence of any value

specified.

In an HDFS ONLY target installation, the

Application’s METADOM (that hosts the

metadata) for an application is stored in

RDBMS schema and the data model entities of

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


the application are stored in the DATADOM

(which would be on Hive).

/ TYPE The different types of schemas

that are supported in this

release are ATOMIC, CONFIG,

SANDBOX, and ADDON.

By default, the schemas types

are seeded based on the

Application Pack.

NOTE: Do not edit this attribute

value.

Y ATOMIC, CONFIG, SANDBOX, or ADDON.

NOTE: SANDBOX AND ADDON schemas

are not applicable for OFS AAAI

Application Pack.

Only One CONFIG schema can exist in the file.

This schema identifies as the CONFIGURATION

a schema that holds the OFSAA setup details

and other metadata information.

Multiple ATOMIC, SANDBOX, ADDON

schemas can exist in the file.

ATOMIC schema refers to the METADOM

within the Information Domain schema.

SANDBOX schema refers to the SANDBOX

schema.

ADDON schema refers to other miscellaneous

schemas (not applicable for this Application

Pack).

/ NAME By default, the schemas names


Application Pack.

You can edit the schema names

if required.

NOTE:

The Schema Name will have a

prefix of the SETUPINFO/

NAME attribute.

SCHEMA NAME must be the

same for all the ATOMIC

Schemas of applications within

an Application Pack.

Y The permissible length is 15 characters and

only alphanumeric characters allowed. No

special characters allowed except

underscore '_'.

SETUPINFO/ NAME attribute value would be

prefixed to the schema name being created.

For example, if the name is set as 'ofsaaatm'

and setupinfo as 'uat' then schema being

created would be 'uat_ofsaaatm'.

NAME must be the same where APP_GRP=1 for

all SCHEMA tags (not applicable for this

Application Pack).

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


/ PASSWORD Enter the password of the

schema to be created.

NOTE: If this attribute is left

blank, then the password

specified in the

/DEFAULT

attribute is applied as the

Schema Password.



allowed.

NOTE: You need to mandatorily enter the

password if you have set the /

APPLYSAMEFORALL attribute as N.

/ APP_ID By default, the Application ID is

seeded based on the

Application Pack.

NOTE: Do not edit this attribute

value.

Y Unique Seeded Value. Identifies the Application or Product for which

the schema is being created. DO NOT modify

this value.

/ DEFAULTTABL

ESPACE

Enter the available default

tablespace for DB User.

NOTE: If this attribute is left

blank, then USERS is set as the

default tablespace.

N Default value: USERS


tablespace name.

Modify this value to associate any valid

tablespace with the schema.

/ TEMPTABLESP

ACE

If this attribute is left blank,

then TEMP is set as the default

tablespace.

N Default value: TEMP


temporary tablespace name.

Modify this value to associate any valid

tablespace with the schema.

/ QUOTA Enter the quota to be set on

DEFAULTTABLESPACE

attribute for the schema or

user. By default, the quota size

is set to 500M. Minimum:

500M or Unlimited on default

Tablespace.

N For example,

600M/m

20G/g

UNLIMITED/unlimited

Modify this value to grant the specified quota

on the mentioned tablespace to the user.

/ TYPE=HDFS Type of schemas being created. Y Refers to the DATADOM of the Application

Pack being installed.

IP or HostName of the server

where HIVE is installed

Y

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


Folder path where HIVE related

drivers or jar files are copied

Y Should contain the list of jars mentioned in the

section Error! Reference source not found. a

nd krb5.conf, keytab files. Manually copy the

preceding listed files from CDH distribution to

this identified folder.

/ NAME By default, the schemas names


Application Pack.

You can edit the schema names

if required.

NOTE: The Schema Name will

have a prefix of the

SETUPINFO/ NAME attribute.

Y The permissible length is 20 characters

and only alphanumeric characters allowed.

Schema Name must not be the same as

Schema Name specified for Schema Type

ATOMIC.

/ TYPE Identifies the type of schema

where the data model entities

would reside.

Y By default, the TYPE attribute in this tag is

set to DATADOM.


/ DB TYPE Identifies the type of driver to

be used for the connection.

Y By default, the only supported type is HIVE

in this release.

In the upcoming releases, the type value can be

HIVE or IMPALA and so on.

//

CO MMENT

COMMENTS for HIVE schema. N

//

LO CATION

You can optionally specify a

location for the table data.

N

//J

DBC_DRIVER

HIVE JDBC driver details. Y com.cloudera.hive.j dbc4.HS2Driver The default cloudera HiveServer 2 driver name.

//J

DBC_URL

Enter the HIVE JDBC URL. Y Valid Hive JDBC URL to be specified. Specify the Hive JDBC URL to connect to the

Hive Server.

INSTALLATION



Tag Name/ Attribute

Name


(Y/N)


//

AUTH_TYPE

Authentication Type. Y Permissible values: KERBEROS_WITH_

KEYTAB

Only “Kerberos with keytab” based

authentication supported in this release.

//

AUTH_ALIAS

Alias name for authentication

credentials.

Y An Alias name mapping to a principal and

password combination specified in the

following tags.

//

PRINCIPAL

Authentication principal name. Y Principal name used in authentication to

connect to the Hive Server.

//

PASSWORD

Authentication password. Y Password used in authentication to connect to

the Hive Server.

//

KRB_GSSJAAS_ FILE_NAME

A keytab file containing pairs of

Kerberos principals and an

encrypted copy of that

principal's key.

Y This file must be copied to the location

specified in .

//

KRB_REALM_ FILE_NAME

REALM configuration file. Y This file must be copied to the location

specified in .

4. Save the file.

INSTALLATION

EXECUTE THE SCHEMA CREATOR UTILITY


5.3 Execute the Schema Creator Utility

Depending on the option selected to run the OFSAA Application Pack installer, you must select the

appropriate schema creator utility execution mode from the following options:

• Execute the Schema Creator Utility in Offline Mode

• Execute the Schema Creator Utility in Online Mode

• Execute the Schema Creator Utility in TCPS Mode

• Execute the Schema Creator Utility while Installing Subsequent Applications Pack

After creating the schema, proceed to Configure the OFSAAI_InstallConfig.xml File.

5.3.1 Execute the Schema Creator Utility in Offline Mode

In the Offline mode, the utility generates an SQL script with all the required DDLs for Users, Objects,

and Grants. This script must be executed by the DBA on the appropriate database identified for

OFSAA usage. If you do not have the SYSDBA privileges, you can execute the Schema Creator Utility in

Offline mode and generate the script file that contains the Schemas, Objects, and Grants information.

Subsequently, an SYSDBA user can execute the script file manually. To run the OFSAA Application

Pack installer in Silent mode, it is mandatory to execute the schema creator utility with -s option.

To execute the utility in Offline mode, you must have a database user with the following GRANTS

(alternatively, you can also connect as a user with SYSDBA privileges):

• SELECT ON DBA_ROLES

• SELECT ON DBA_USERS

• SELECT ON DBA_DIRECTORIES

• SELECT ON DBA_TABLESPACES

• CREATE SESSION

NOTE Explicit Grants to the user are required. Grants assigned through Roles are not supported.

To execute the schema creator utility in the offline mode, follow these steps:


2. Navigate to the OFS_DI_PACK/schema_creator/bin/ directory.

3. Execute the osc.sh file using the following command:

./osc.sh -s -o

The following message is displayed:

You have chosen OFFLINE mode. Triggering the utility in OFFLINE mode will generate the script.

Do you wish to proceed? (Y/y or N/n).

4. Enter Y to proceed.

5. Enter the DB Username with SELECT privileges.

INSTALLATION

EXECUTE THE SCHEMA CREATOR UTILITY


6. Enter the User Password.

7. The console runs the initial validation checks and displays the following message:

You have chosen to install this Application Pack on ATOMIC

schema. Do you want to proceed? (Y/N).

Figure 11: Schema Creation in the Offline Mode - Script Generation

8. Enter Y to start the script generation. T

Oracle Financial Services Data Integration...This section provides supporting information for the...

Documents

Transcript of Oracle Financial Services Data Integration...This section provides supporting information for the...