This section provides information for Post-installation required for the OFSBCE Release 8.1.0.0.0.
Topics:
· OFSAA Infrastructure Patch Installation
· Verify the Log File Information
· Stop the Infrastructure Services
· Create and Deploy the EAR/WAR Files
· EAR/WAR File - Build Once and Deploy Across Multiple OFSAA Instances
· Start the Infrastructure Services
· Configure Internet Explorer Settings
· Access the OFSAA Application
· View OFSAA Product Licenses after the Installation of Application Pack
· Configure the excludeURLList.cfg File
· Configure Big Data Processing
· Map the Application User(s) to User Group
· Change the ICC Batch Ownership
· Excel Upload Mapping and Template
· Add TNS entries in the TNSNAMES.ORA File
· Configure Transparent Data Encryption (TDE) and Data Redaction in OFSAA
· Implement Data Protection in OFSAA
NOTE |
See the Post-Installation section in the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.0.0.0 to complete these procedures. For additional configuration information, see the Additional Configuration section. |
Oracle strongly recommends installing the latest available patch set to be up-to-date with the various releases of the OFSAA product.
After the installation of OFSBCE Application Pack 8.1.0.0.0:
· Apply the 31605076 one-off patch. See the ReadMe packaged with the patch for further instructions about how to install the patch.
· Apply the OFSAAI Mandatory Patch 33663417.
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 whenever any New or Upgrade or an Incremental Installation Release is applied, the OFSAAI Mandatory Patch 33663417 for Log4J must be reapplied. |
For the Patch download information, see the Download the Mandatory Patches Section in Pre-installation for a new installation.
See My Oracle Support (MOS) for more information about the latest release.
See the following logs files for more information:
· Pack_Log.log file in the OFS_IBCE_PACK/logs/ directory.
· Infrastructure installation log files in the OFS_IBCE_PACK/OFS_AAI/logs/ directory.
· BCE installation log files in the OFS_IBCE_PACK/OFS_IBCE/logs/ directory.
See the Stop the Infrastructure Services section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the Create and Deploy the EAR/WAR Files section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the EAR/WAR File - Build Once and Deploy Across Multiple OFSAA Instances section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the Start the Infrastructure Services section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the Access the OFSAA Application section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the OFSAA Landing Page section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
In an integrated environment, where you have multiple applications installed on the same domain or infrastructure, OFSAAI allows you to see the other licensed applications through the UI. For more information, see the View OFSAA Product Licenses after Installation of Application Pack in the Oracle Financial Services Advanced Analytical Applications Infrastructure User Guide Release 8.1.0.0.0.
See the section Configure the excludeURLList.cfg File in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
This section is not applicable if you have enabled Financial Services Big Data Processing during the installation of OFSBCE 8.1.0.0.0 full installer. Follow instructions in this section if you intend to enable Big Data Processing.
Topics:
· Copy the Jar Files to the OFSAA Installation Directory
· Copy the KEYTAB and KRB5 Files in OFSAAI
1. Download the supported Cloudera HIVE JDBC Connectors and copy the following jars files to the $FIC_HOME/ext/lib/ and $FIC_WEB_HOME/webroot/WEB-INF/lib/ directory. For the latest supported versions, see OFSAA Technology Matrix v8.1.0.0.0.
§ hive_service.jar
§ hive_metastore.jar
§ HiveJDBC4.jar
§ zookeeper-3.4.6.jar
§ TCLIServiceClient.jar
2. Copy the following jars files from the <Cloudera Installation Directory>/jars/ directory based on the CDH version to the $FIC_HOME/ext/lib/ and $FIC_WEB_HOME/webroot/WEB-INF/lib/ directories.
§ CDH v5.13.0:
— commons-collections-3.2.2.jar
— commons-configuration-1.7.jar
— commons-io-2.4.jar
— commons-logging-1.2.jar
— hadoop-auth-2.6.0-cdh5.13.0.jar
— hadoop-common-2.6.0-cdh5.13.0.jar
— hadoop-core-2.6.0-mr1-cdh5.13.0.jar
— hive-exec-1.1.0-cdh5.13.0.jar
— httpclient-4.3.jar
— httpcore-4.3.jar
— libfb303-0.9.3.jar
— libthrift-0.9.3.jar
— slf4j-api-1.7.5.jar
— slf4j-log4j12-1.7.5.jar
§ CDH v6.3.0:
— commons-collections-3.2.2.jar
— commons-configuration2-2.1.1.jar
— commons-io-2.6.jar
— commons-logging-1.2.jar
— hadoop-auth-3.0.0-cdh6.3.0.jar
— hadoop-common-3.0.0-cdh6.3.0.jar
— hive-exec-2.1.1-cdh6.3.0.jar
— httpclient-4.5.3.jar
— httpcore-4.4.6.jar
— libfb303-0.9.3.jar
— libthrift-0.9.3.jar
— slf4j-api-1.7.25.jar
— slf4j-log4j12-1.7.25.jar
A Keytab is a file containing pairs of Kerberos principals and encrypted keys (these are derived from the Kerberos password). The krb5.conf file contains Kerberos configuration information, including the locations of KDCs and admin servers for the Kerberos realms of interest, defaults for the current realm, and Kerberos applications, and mappings of hostnames onto Kerberos realms.
If the Authentication is configured as KERBEROS_WITH_KEYTAB for the Hive database, then you must use the Keytab file to login to Kerberos. The Keytab and Kerberos files must be copied to $FIC_HOME/conf and $FIC_WEB_HOME/webroot/conf of the OFSAAAI installation directory.
Generate the application EAR/WAR file and redeploy the application onto your configured web application server.
Restart the Web application server and the OFSAAAI Application Server. For more information, see the Start the Infrastructure Services section.
Create the application users in the OFSAA setup before use.
For details, see the User Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide Release 8.1.0.0.0.
User UserGroup Map facilitates you to map user(s) to a specific user group, which in turn is mapped to a specific Information Domain and role. Every user group mapped to the Information Domain needs to be authorized. Else, it cannot be mapped to users.
User UserGroup Map screen displays details such as User ID, Name, and the corresponding Mapped Groups. You can view and modify the existing mappings within the User UserGroup Maintenance screen.
Starting with the OFSAA 8.1 release, with the installation of the OFS BCE Application, preconfigured Application user groups are seeded. These user groups are unique to every OFSAA Application Pack and have application roles pre-configured.
You can access the User UserGroup Map by expanding the Identity Management section within the tree structure of the LHS menu.
Table 33: Seeded User Groups
Name |
Description |
BCE Admin |
A user mapped to this group will have access to all the menu items for the entire OFSBCE Application. The exclusive menu’s which are available only to this group users are Application Preference and Global Preference under Settings Menu. |
All the seeded Batches in the OFS BCE application are automatically assigned to the SYSADMN user during installation. To see the batches in the Batch Maintenance menu, you must execute the following query in the Config Schema of the database:
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromUser','toUser','infodom');
end;
OR
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromUser','toUser');
end;
Where:
· fromUser indicates the user who currently owns the batch
· toUser indicates the user to whom the ownership must be transferred
· infodom is an optional parameter. If specified, the ownership of the batches pertaining to that Infodom will be changed.
This section provides steps about the ExcelUpload.
1. Copy the ExcelUpload directory present in the path $FICHOME/CIRCA/.
2. In the ExcelUpload directory, change the directory name from infodom to the respective infodom name.
3. Copy the ExcelUpload directory to the ftpshare/STAGE directory.
4. Create the STAGE directory in the path <TOMCAT_HOME>.
5. Copy the ExcelUpload directory to the STAGE directory in the path <TOMCAT_HOME>.
See the Add TNS entries in the TNSNAMES.ORA File section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the Configure Transparent Data Encryption (TDE) and Data Redaction in OFSAA section in the OFSAAI Release 8.1.0.0.0 Installation and Configuration Guide for details.
See the Oracle Financial Services Data Foundation Application Pack Data Protection Implementation Guide Release 8.1.x for details.