This section contains the pre-installation requirements for a successful installation and functioning of the OFS Data Foundation Application Pack.
Topics:
· Hardware and Software Requirements
· Oracle Database Instance Settings
· Web Application Server Settings
· Create the Installation, Download and Metadata Directories
· Configure the OS File System Settings and Environment Settings in the .profile File
To complete the pre-installation process, you must perform the following steps listed in the Pre-installation Checklist table. Use this checklist to verify whether these steps are completed or not.
Table 8: Pre-installation Checklist
Sl. No. |
Activity |
1 |
Install all the prerequisite hardware and software as per the OFSAA Technology Matrix. |
2 |
Install and configure the prerequisite hardware and software for the Big Data (Only for the Big Data installation). |
3 |
Verify the System Environment using the Environment Check Utility. |
4 |
Download the OFSDF Application Pack installer kit. |
5 |
Download the Data Model (optional). |
6 |
Download the mandatory patches. |
7 |
Configure the Database Instance settings. |
8 |
Install and configure the web application server. |
9 |
Configure the HTTP settings on the webserver. |
10 |
Create the Installation, Download, and Metadata Repository Directories: · Installation directory · Temporary directory · Staging Area/Metadata Repository · Download directory |
11 |
Configure the following Operating System and File System settings: · File Descriptor · Total number of processes · Port(s) · .profile file permissions · Set Up the SFTP Private Key |
12 |
Update the following Environment Settings as required for the installation in the .profile file: · Java Settings · Oracle Database Server and Client Settings · Add TNS entries in the tnsnames.ora file · Oracle Essbase Settings · Time Zone Settings |
This section describes the various Operating System, database, web server, and web application server version and other variant details on which this release of the Oracle Financial Services Data Foundation Application Pack has qualified.
Topics:
· Third-party Licensing Information
· Verify the System Environment
See the OFSAA Technology Matrix document for the hardware and software required for the Oracle Financial Services Data Foundation Application Pack Release 8.1.0.0.0.
Table 9: 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 |
Oracle Solaris |
Oracle Database |
Oracle WebLogic Server/Apache Tomcat Server |
Oracle HTTP Server/Apache HTTP Server |
This is an optional section and required only if you intend to install the OFSAA Big Data Processing. See the OFSAA Technology Matrix for the software required for the Big Data software Hadoop Distribution on the Oracle Financial Services Data Foundation Application Pack Release 8.1.0.0.0.
· Install CDH. For installation information, see the Cloudera documentation at https://docs.cloudera.com/.
· Install the Apache Livy (Incubating) web service:
a. Go to https://incubator.apache.org/clutch/livy.html.
b. Download the livy-0.4.0-incubating zip files.
c. Install livy-0.4.0-incubating for Spark 2. For installation information, see the documentation at https://docs.cloudera.com/HDPDocuments/HDP2/HDP-2.6.5/bk_command-line-installation/content/install_livy.html.
For details on the third-party software tools used, see the Oracle Financial Services Analytical Applications (OFSAA) Licensing Information User Manual Release 8.1.0.0.0.
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 Services.
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 more details on download and usage of this utility, see the Oracle Financial Services Advanced Analytical Applications Infrastructure Environment Check Utility Guide Release 8.1.x.
This section details the preparatory procedures that must be followed before triggering the installation.
Topics:
· Download the OFSDF Application Pack Installer
· Download the Mandatory Patches
To download the OFSDF Application Pack installer Release v8.1.0.0.0, follow these steps:
1. Log in to the Oracle Software Delivery Cloud with a valid Oracle account.
Figure 4: Oracle Software Delivery Cloud Login Page
2. Search for the full product name Oracle Financial Services Data Foundation and download the installer archive.
Figure 5: Oracle Software Delivery Cloud Page
3. Copy the installer archive into the download directory (in Binary mode) in the setup identified for the OFSDF Application Pack installation.
To download the OFSDF OOB v8.1.0.0.0 Data Model, follow these steps:
NOTE |
This is an optional section, which is applicable if you are performing the customized model upload. |
1. Log in to the My Oracle Support (MOS) with a valid Oracle account.
2. In the Patches & Updates tab, search for the OFSDF Data Model installer patch 30812072 and download the patch. See the Readme available with the patch for further instructions on downloading the patch and extracting the erwin files.
The following table includes information about the mandatory patches that must be applied.
Table 10: Mandatory Patches
One-Off Patch |
Description |
31544548 |
Download this OFSDF one-off patch for the fresh installation of the OFSDF Application Pack 8.1.0.0.0 release. This patch is applicable only to the RDBMS mode of installation. |
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 a new atomic schema. |
33663417 |
Download this mandatory OFSAAI One-off Patch. See the ATTENTION below. |
ATTENTION |
For the Mandatory Patch ID 33663417: On the 10th of December 2021, Oracle released the Security Alert CVE-2021-44228 in response to the disclosure of a new vulnerability affecting Apache Log4J prior to version 2.15. The application of the 33663417 Mandatory Patch fixes the issue. For details, see the My Oracle Support Doc ID 2827801.1. Ensure that you reapply the OFSAAI Mandatory Patch 33663417 whenever you Install or Upgrade the Application, or whenever you apply an Incremental Patch. |
NOTE |
Ensure that the tablespace or tablespaces used for the database user or users is set to AUTOEXTEND ON. |
Ensure that the following database instance settings are configured:
· NLS_CHARACTERSET to AL32UTF8
· NLS_LENGTH_SEMANTICS to BYTE
· OPEN CURSORS limit to greater than 1000
Ensure that the web application server is installed and the profile (when using WebSphere) or domain (when using WebLogic) is created.
Table 11: Web Application Server Settings
Description |
Example Value |
WebSphere/ WebLogic/ Tomcat |
Web Application Server should be installed and the profile/domain created. You will be prompted to enter the WebSphere Profile path, the WebLogic Domain path, or the Tomcat Deployment path during OFSAAI installation. NOTE: See the Configure the Web Server section for WebSphere Profile and WebLogic Domain creation. |
This is an optional requirement. If you have installed an HTTP Server, then configure the appropriate HTTP server settings:
Table 12: Web Server Settings
Description |
Example Value |
Apache HTTP Server/ Oracle HTTP Server/ IBM HTTP Server |
Configure the HTTP Server and note down the IP/ Hostname and Port details as you will be prompted to enter these details during installation. NOTE: See the Configure the Web Server section for the Web Server configuration. |
To install the OFSDF Application Pack, create the following directories:
· OFSDF Download Directory (Optional): Create a download directory and copy the OFSDF Application Pack Installer File (archive). This is the directory where the downloaded installer/ 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/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/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. |
· OFSDF 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 that the user permission is set to 775 on the Installation Directory.
Topics:
· Configure Operating System and File System Settings
· Configure the Environment Settings
A .profile file is a start-up file of a UNIX user. Create the .profile file at the home directory of the logged-in user if it is not already available. The user must have 755 permission on the file to execute it. This file consists of various parameters for Environment Settings, OS, and File System Settings.
To set the parameters for the .profile file, login as a non-root user, and configure the environment settings.
WARNING |
Do not modify any other parameters other than the parameters mentioned in the following subsections. |
The following table displays the required settings for the operating system and file system.
Table 13: Configure Operating System and File System Settings
Parameter |
Configuration Action |
Installation Directory |
In the .profile file, set the variable FIC_HOME to point to the OFSAA Installation Directory. |
File Descriptor Settings |
In the sysctl.conf file, to change the number of file descriptors, do the following as the root user: 1. Edit the following line in the /etc/sysctl.conf file: fs.file-max = <value> where <value> is greater than 15000 2. Apply the change by running the following command: # /sbin/ sysctl -p NOTE: The value specified here is the minimum value to be set for the installation process to go forward. For other modules, this value may depend on the available resources and the number of processes executed in parallel. |
Total Number of Process Settings |
In the sysctl.conf file set the value to greater than 4096. NOTE: The value specified here is the minimum value to be set for the installation process to go forward. For other modules, this value may depend on the available resources and the number of processes executed in parallel. |
Port Settings |
Default port numbers to be enabled on the system are 6500, 6501, 6505, 6507, 6509, 6510, 6666, 9999, and 10101. |
.profile permissions |
You must have 755 permission on the .profile file. |
OS Locale |
· Linux: en_US.utf8 · AIX: EN_US.UTF-8 · Solaris: en_US.UTF-8 To check the locale installed, execute the following command: locale -a | grep -i 'en_US.utf' |
This section provides information to configure the environment settings before installation.
Topics:
· Oracle Database Server and Client Settings
· TNS Entries in the TNSNAMES.ORA File
NOTE |
If you are installing an application pack on an environment, where another application pack is already installed, you may sometimes get a warning message such as "Object Already Exists". This message can be ignored. |
The following table displays the Java settings required for installation.
Table 14: Java Settings
Description |
Example Value |
In the .profile file, set PATH to include the Java Runtime Environment (JRE) absolute path. Ensure that SYMBOLIC links to JAVA installation are not set in the PATH variable. |
JAVA_HOME=/scratch/jdk<<version>>/jre For example: PATH=/usr/java/jre1.8.0_221/bin:$ORACLE_ HOME/ bin:$PATHJAVA_HOME=/scratch/jdk<<version>>/jre |
In the .profile file, set PATH to include the Java Runtime Environment bin path. |
JAVA_BIN=/scratch/<<version>>/jre/bin For example: PATH=/usr/java/jre1.8.0_221/bin:$ORACLE_ HOME/bin:$PATH |
Enable unlimited cryptographic policy for Java. |
For more information, see the Enabling Unlimited Cryptographic Policy for Java section from the OFS Analytical Applications Infrastructure Administration Guide. |
The following table displays the Oracle Database server and client settings required for installation.
Table 15: Oracle Database Server and Client Settings
Description |
Example Value |
In the .profile file, set TNS_ADMIN pointing to the appropriate tnsnames.ora file. |
TNS_ADMIN=$HOME/tns |
In the .profile file, set ORACLE_HOME pointing to the appropriate Oracle Client installation. |
ORACLE_HOME=/scratch/oraofss/app_client18c/product/18.0.0/client_1 |
In the .profile file, set PATH to include the appropriate $ORACLE_HOME/bin path. |
PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin |
OFSAA Processing Server
|
· ORACLE_HOME must be set in the .profile file and point to appropriate Oracle DB Client installation. · PATH in the .profile file must be set to include the appropriate $ORACLE_HOME/bin path. · Ensure that an entry (with SID/SERVICE NAME) is added in the tnsnames.ora file. |
This section provides information about the TNS entries in the TNSNAMES.ORA file.
Topics:
· Non-TCPS
· TCPS
Table 16: TNS entries in the TNSNAMES.ORA file for the Non-TCPS mode
Description |
Example Value |
Ensure that an entry (with SID/ SERVICE NAME) is added in the tnsnames.ora file on the OFSAA server. |
<SID_NAME> = DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <HOST_NAME>.in.oracle.com)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = <SID_NAME>)))<ATOMIC_SCHEMA_NAME> = (DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <HOST_NAME>.in.oracle.com)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = <SID_NAME>))) |
<SID NAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <HOST NAME>)(PORT = <PORT NUMBER>))
)
(CONNECT_DATA =
(SERVICE_NAME = <SID NAME>)
)
)
<ATOMICSCHEMANAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <HOST NAME>)(PORT = <PORT NUMBER>))
)
(CONNECT_DATA =
(SERVICE_NAME = <SID NAME>)
)
)
NOTE |
The ATOMIC SCHEMA NAME must be the same as defined in the OFS_<App Pack>_SCHEMA_IN.xml file. |
Table 17: TNS entries in the TNSNAMES.ORA file for the Non-TCPS mode
Description |
Example Value |
Ensure that an entry (with SID/ SERVICE NAME) is added in the tnsnames.ora file on the OFSAA server. |
<SID_NAME> = DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCPS)(HOST = <HOST_NAME>.in.oracle.com)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = <SID_NAME>)))<ATOMIC_SCHEMA_NAME> = (DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCPS)(HOST = <HOST_NAME>.in.oracle.com)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = <SID_NAME>)))(security=(ssl_server_cert_dn=CN=<HOST_NAME>)))) |
Ensure that an entry (with WALLET_HOME and wallet parameters) is added in the sqlnet.ora file on the OFSAA server must be the same as the Oracle database server running with TCPS. |
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)WALLET_LOCATION = (SOURCE = (METHOD = FILE) (METHOD_DATA = (DIRECTORY = <PATH TO WALLET DIRECTORY>)))SQLNET.WALLET_OVERRIDE = TRUE SSL_CLIENT_AUTHENTICATION = FALSE SQLNET.AUTHENTICATION_SERVICES = (TCPS,NTS,BEQ) SSL_CIPHER_SUITES = (SSL_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA) |
<SID NAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCPS)(HOST = <HOST NAME>)(PORT = <PORT NUMBER>))
)
(CONNECT_DATA =
(SERVICE_NAME = <SID NAME>)
(security=(ssl_server_cert_dn=CN=<HOST NAME>))
)
)
<ATOMICSCHEMANAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCPS)(HOST = <HOST NAME>)(PORT = <PORT NUMBER>))
)
(CONNECT_DATA =
(SERVICE_NAME = <SID NAME>)
(security=(ssl_server_cert_dn=CN=<HOST NAME>)) )
)
NOTE |
The ATOMIC SCHEMA NAME must be the same as defined in the OFS_BFND_SCHEMA_IN.xml file, which also includes prefix without underscore. For example, DEVOFSAAATM. |
In the .profile file, set the following parameters if you want to use Oracle Hyperion Essbase OLAP features.
Table 18: Oracle Essbase Settings
Description |
Example Value |
ARBORPATH to point to an appropriate Oracle Essbase Client installation. |
PATH=$PATH:$ARBORPATH/bin |
ESSBASEPATH to point to an appropriate Oracle Essbase Client installation. |
ESSBASEPATH=/scratch/essps3/Oracle/MiddlewareHome/EPMSystem11R1/common/EssbaseRTC-64/11.1.2.0 export ESSBASEPATH |
HYPERION_HOME to point to an appropriate Oracle Essbase Client installation. |
HYPERION_HOME=/scratch/essps3/Oracle/MiddlewareHome/EPMSystem11R1/common/EssbaseRTC-64/11.1.2.0 export HYPERION_HOME |
In the .profile file, set the Time Zone parameter to indicate the time zone of your region/ location.
Table 19: Time Zone Settings
Description |
Example Value |
Time Zone |
TZ=Asia/Calcutta |