This section describes the necessary software settings, installation of mandatory patches and procedures you must perform before proceeding to install the Oracle Financial Services Analytical Applications Reconciliation Framework Pack.
Topics:
· Oracle Database Instance Settings
· Web Application Server Settings
· Create the Installation, Download, and Metadata Repository Directories
· Configure the OS File System Settings and Environment Settings in the .profile File
· Apply Pre-install Mandatory Patches
· Download the OFS Analytical Applications Reconciliation Framework Pack Installer
Sl. No. |
Pre-installation Activity |
|---|---|
1 |
Install all the prerequisite hardware and software as per the Tech Stack. |
2 |
Verify the System Environment using the Environment Check Utility. |
3 |
Configure the Database Instance settings. |
4 |
Install and configure the web application server. |
5 |
Configure the HTTP settings on the webserver. |
6 |
Create the Installation, Download, and Metadata Repository Directories: · Installation directory · Temporary directory · Staging Area/Metadata Repository Download directory |
7 |
Configure the following Operating System and File System settings: · File Descriptor · Total number of processes · Port(s) · .profile file permissions · Add FTP/SFTP configuration for file transfer |
8 |
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 |
9 |
Apply pre-install mandatory patches. |
10 |
Download the installer kit. |
11 |
Extract the installer kit. |
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 (if using WebSphere) or domain (if using WebLogic) is created.
Description |
Example Value |
|---|---|
WebSphere/ WebLogic/ Tomcat |
You will be prompted to enter the WebSphere Profile path, the WebLogic Domain path, or the Tomcat Deployment path during OFSAAI installation. NOTE: See Configure the Web Server for information on creating WebSphere Profile and WebLogic Domain. |
This is an optional requirement. If you have installed an HTTP Server, then configure the appropriate HTTP server settings:
Description |
Example Value |
|---|---|
Apache
HTTP Server/ Oracle HTTP Server/ |
Configure the HTTP Server and note down the IP or Hostname and Port details as you will be prompted to enter these details during the installation. NOTE: See Configure the Web Server for more details. |
This is an optional section and is required only if you intend to install OFSAA Big Data Processing. See the OFSAA Technology Matrix for the software required for Data software Hadoop Distribution on the Oracle Financial Services Analytical Applications Reconciliation Framework Pack Release 8.1.0.0.0.
1. Install CDH. For installation information, see the Cloudera documentation at https://www.cloudera.com/.
2. Ensure that the Hadoop client is already installed and configured in the .profile file before proceeding with the Big Data installation (Stage and Results on Hive). For more information, see the Pre-installation steps for the Stage and Results on Hive mode of the Big Data Installation section.
3. 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.
4. Copy the ofsaa-hive-udf.jar file from the installer kit (OFS_DM_PACK/OFS_AAAI_PACK/fichome/utility/DMT/UDF/lib) to the HiveAuxDir of the cluster. For more information, see Managing User-Defined Functions (UDFs) with HiveServer2.
To install OFSAA Reconciliation Framework, create the following directories:
· OFSAA Download Directory (Optional): This is the directory where the downloaded installer or patches can be copied. You can copy the OFSAA Application Pack Installer File (archive). Assign 755 permission to this directory.
· Temporary Directory: The default temporary directory where the installation files are stored for a short time to support faster installation. Configure adequate space on the /tmp directory. It is recommended that you allocate more than 10 GB space. Assign 755 permission to this directory with NOEXEC option disabled.
· For installation on UNIX OS, your UNIX administrator must give you the required read-write permissions for the /tmp directory and disable the NOEXEC option.
NOTE:
If the NOEXEC option is enabled, the extraction of files by the installer into the /tmp directory is prevented and the binaries will not execute in the directory, which will fail the installation.
· OFSAA Installation Directory (Mandatory): Create an installation directory where the product binaries are installed. Set the variable FIC_HOME in the .profile file to point to the OFSAA Installation Directory. Assign 755 user permission to the installation directory.
· OFSAA Staging/Metadata 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
· Is not a subdirectory inside the OFSAA 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 parameter other than the ones mentioned in the following subsections.
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 a value 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. |
Topics:
· Oracle Database Server and Client Settings
· TNS entries in the TNSNAMES.ORA file for Non-TCPS and TCPS
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 section in the OFS Analytical Applications Infrastructure Administration Guide. |
Description |
Example Value |
|---|---|
In the .profile file, set TNS_ADMIN to the appropriate tnsnames.ora file. |
TNS_ADMIN=$HOME/tns |
In the .profile file, set ORACLE_HOME 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 |
Non-TCPS
Description |
Example Value |
|---|---|
Ensure that an entry (with SID or 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_DM_SCHEMA_IN.xml file.
TCPS
Description |
Example Value |
|---|---|
Ensure that an entry (with SID or 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 and 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_DM_SCHEMA_IN.xml file, which also includes prefix without underscore. For example, DEVOFSAAATM.
In the .profile file, set the following parameters for Oracle Wallet if you want to run the installer in the TCPS mode:
· OFS_ORA_WAL_ENABLED=TRUE
· export OFS_ORA_WAL_ENABLED
NOTE:
Installation in TCPS mode with Oracle Wallet requires Config and Atomic Schema credentials in Oracle Wallet along with certificates.
If you do not configure this variable, the system defaults to OFS_ORA_WAL_ENABLED=FALSE.
In the .profile file, set the following parameters only if you want to use Oracle Hyperion Essbase OLAP features.
Description |
Example Value |
|---|---|
ARBORPATH to an appropriate Oracle Essbase Client installation. |
PATH=$PATH:$ARBORPATH/bin |
ESSBASEPATH 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 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.
Description |
Example Value |
|---|---|
Time Zone |
TZ=Asia/Calcutta |
You must apply the following mandatory patches before proceeding to install the product. See the Readme packaged with the patches for further instructions on how to install them.
Patch ID |
Description |
|---|---|
31498038 |
Download and install patch 31498038 from My Oracle Support. NOTE: If you want to install the OFSAA Reconciliation Framework Pack before any other OFSAA application, install this patch as a post-installation patch. See Post-installation Mandatory Patches. |
31545589 |
Schema creator patch Extract the SchemaUtil.jar file from this patch and copy it to the path: OFS_DM_PACK/schema_creator/lib. You can find this patch on My Oracle Support. |
31654438 |
Download and install patch 31654438 from My Oracle Support. |
To download the OFS Analytical Applications Reconciliation Framework 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.
2. Enter Oracle Financial Services Analytical Applications Reconciliation Framework in the search field and click Search.
3. From the list of displayed results, click the Select button corresponding to the software you want to download.
4. Download the installer archive and copy it in Binary mode to the download directory that exists in the OFSAA Reconciliation Framework Pack installation setup.
NOTE:
You can download the ERwin data model patch.
5. Log in to My Oracle Support, search for the 33663417 Mandatory Patch in the Patches & Updates Tab and download it.
ATTENTION:
On the 10th of December 2021, Oracle released 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.
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_<os>.Z and copy it in Binary mode to the directory that is included in your PATH variable.
Uncompress the unzip installer file with the command:
uncompress unzip_<os>.Z
NOTE:
If an error message "uncompress: not found [No such file or directory]" is displayed, contact your UNIX administrator.
2. Assign execute (751) to the file with the following command:
chmod 751 unzip_<OS>
For example: chmod 751 unzip_sparc
3. Extract the contents of the Oracle Financial Services Analytical Applications Reconciliation Framework Pack Release 8.1.0.0.0 installer archive file in the download directory with the following command:
unzip OFS_DM_8.1.0.0.0_<OS>.zip
4. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
5. Navigate to the download directory and assign execute permission to the installer directory with the following command:
chmod -R 750 OFS_DM_8.1.0.0.0_<OS>