How to Define Application Sources As Pre-Installation Step for OFSAA 5.1 (Doc ID 1079608.1)

Last updated on FEBRUARY 09, 2011

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version: 7.1 and later   [Release: 7 and later ]
Oracle Financial Services Profitability Management - Version: 5.1 and later    [Release: 5 and later]
Oracle Financial Services Asset Liability Management - Version: 5.1 and later    [Release: 5 and later]
Oracle Financial Services Funds Transfer Pricing - Version: 5.1 and later    [Release: 5 and later]
Information in this document applies to any platform.
OFSAA
OFSAAI

Goal

How to Define Application Sources As Pre-Installation Step for Oracle Financial Services (OFS) Applications version 5.1.

Every application has a data source associated with it. A data source definition refers to the physical location of data and its connection attributes, servicing one or more source applications. Data sources are of three main types:
  • RDBMS files - refers to Relational databases
  • Non-RDBMS files - refers to Mainframe systems and sources in VSAM and ISAM files formats.
  • Flat-Files - refer to text or ASCII files
Source Data Models should be generated from the source systems to enable the definition of source extracts. Infrastructure Data Integrator allows the generation of the Source Data Models for a Source Application-Data Source combination.

When you install Oracle Financial Services (OFS) Application, defining application sources is a pre-requisite step prior to running the setup.sh for the applications.

The following are Oracle Financial Services (OFS) Application products:
Oracle Financial Services Asset Liability Management 5.1
Oracle Financial Services Funds Transfer Pricing 5.1
Oracle Financial Services Profitability Management 5.1
Please note the following limitations with Defining Application Sources in version 5.1:
  • Application and Source names are not dynamic. They have to be the exact name as mentioned in the solution steps below.
  • The installer assumes the application and sources have been created, thus deploys the ETL definitions into this source when you run setup.sh.
  • The source recommended may be an RDBMS based source, in which case the source should be defined on the same schema as the one in which the solution is being installed.
  • Once an application and source has been created in the framework, you cannot create a new application and source with the same name. The source created earlier will hence be re-used for installing the new OFS Applications, be it on an information domain(infodom) already containing an OFS Application or a new infodom.
  • As a result, if you need to install an OFS Application into an infodom #2, there will be a mismatch since the pre-created source will point to schema of infodom #1.
It is recommended for 5.1 release, that you do not create multi-infodom installation unless you intend to do it on a non-production environment where ETL activities will NOT be performed through OFS Infrastructure.

The plan is to address this in release 5.2 by making the source name selection dynamic i.e. source name will not be mandated, but will be user-specified at install time.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms