This Maintenance Release of the Oracle Insurance Data Foundation Application Pack includes all enhancements and bug fixes that are done since the OIDF Application Pack v8.1.1.0.0 release.
Topics:
· Pre-installation Requirements
· Applying this Maintenance Release
NOTE:
The schemas or domains for OIDF are referred to as OFS_OIDF.
These are the pre-installation requirements for the OIDF Application Pack v8.1.1.1.0 release:
NOTE:
Before installing OIDF Application Pack v8.1.1.1.0, if Data Management Release v8.0.5.0.0 Application Pack (full installer) is already installed on the system, then execute the following statements in the Atomic schema:
· DROP INDEX DIM_DATES_CALENDAR_DATE;
· DROP INDEX DIM_KI_GROUP_LRI;
· Oracle Insurance Data Foundation (OIDF) Application Pack v8.1.1.0.0 Minor Release patch ID 32347735 plus other prerequisite OIDF patches (download from My Oracle Support (MOS)) must be installed and configured on your machine. For more information, see the Preparing for Installation section in the Oracle Insurance Data Foundation Application Pack Installation and Configuration Guide Release 8.1.1.0.0.
NOTE:
The erwin files for OIDF Application Pack v8.1.1.1.0 is available on My Oracle Support (MOS) in patch 32865324.
· Enable the unlimited cryptographic policy. By default, JCE Policy JAR files are available for the Java versions mentioned in the following link and for later versions:
https://bugs.java.com/view_bug.do?bug_id=JDK-8170157
For the Java versions, where unlimited cryptographic policy is disabled by default, follow these steps:
a. Download the JCE Policy related jar files local_policy.jar and US_export_policy.jar.
— For Oracle Java, download the local_policy.jar and US_export_policy.jar files from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html.
— For IBM Java, download the local_policy.jar and US_export_policy.jar files from https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=jcesdk.
b. Copy (or replace) the downloaded JCE Policy related jar files local_policy.jar and US_export_policy.jar to the /jre/lib/security directory of the Java installation directory used for OFSAAI and the web application servers.
NOTE:
For information about the hardware and software requirements, see the Oracle Financial Services Analytical Applications (OFSAA) Technology Matrix Release 8.1.1.0.0.
This section provides information about installing this Maintenance Release.
NOTE:
This Maintenance Release patch is applicable only for an RDBMS mode of installation.
Topics:
· Downloading OIDF Application Pack
· Installing the OIDF Application Pack
· Post-installation Activities
To download and extract the release contents, follow these steps:
NOTE:
Enable the unlimited cryptographic policy. By default, JCE Policy JAR files are available for Java.
1. Log in to My Oracle Support (MOS). In the Patches & Updates tab, search for patch ID 32605417.
2. Download the OIDF Application Pack v8.1.1.1.0 archive file and copy it to your OFSAA server in the Binary mode.
NOTE:
The archive files are different for different operating systems such as AIX, Solaris, and RHEL or Oracle Linux.
3. Stop all the OFSAAI Services. For more information, see the Stop the Infrastructure Services section in the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.1.0.0.
4. 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 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.
5. Log in to the OFSAA Server as a non-root user.
6. Execute the following command:
chmod -R 750 $FIC_HOME
7. Assign the WRITE permission to the files and folders such as commonscripts, EXEWebService, ficapp, ficweb, and ficdb by using the following command:
chmod -R 775 *
8. If you have an Unzip utility, skip to the next step. Download the Unzip utility (OS-specific) unzip_<os>.Z and copy it in the Binary mode to the directory that is included in the PATH variable, in the $HOME path or directory in which you copied the OIDF Application Pack v8.1.1.1.0 installer.
a. Extract the unzip installer file using the following command:
uncompress unzip_<os>.Z
NOTE:
If you notice an error message: “uncompress: not found [No such file or directory]” when the package is not installed, contact your UNIX administrator.
b. Give the EXECUTE permission to the file using the following command:
chmod 751 OFS_OIDF_8.1.1.1.0_<OperatingSystem>.zip
9. Extract the contents of the OIDF v8.1.1.1.0 archive file using the following command:
unzip_<os> -a <name_of_the_file_to_be_unzipped>
NOTE:
Rename or remove the existing OFSAA Application Pack folder from the OFSAA server before extracting the contents from the release archive (.zip).
For example: When this release is extracted from the archive, it creates a folder named OFS_OIDF_PACK. Rename or remove any existing folder with the same name, which exists in the path where the release archive is copied.
-a option in this step is mandatory to unzip the archive file.
For example:
unzip_aix -a OFS_OIDF_8.1.1.1.0_<OperatingSystem>.zip
This section provides pre-installation activities required for the installation of the OIDF Application Pack v8.1.1.1.0 release.
Topic:
You must upload the configuration file params.conf before triggering the installation. The params.conf file is present in the /OFS_OIDF_PACK/appsLibConfig/conf/ directory.
The following are the input parameters for the params.conf file:
· Model Upload Process
§ The required input value is 0 or 1.
— 0 is an indication to skip the model upload process.
— 1 is an indication to trigger the model upload process.
§ If the value is 1, then select the type of the model for the model upload process:
— 0 indicates the Released Data Model.
— 1 indicates a Customized Data Model.
If the value is 1, then provide the inputs for the Data Model Name and the Path of the Data Model.
To install the OIDF Application Pack v8.1.1.1.0 release, follow these steps:
1. Assign the EXECUTE permission to the Maintenance release archive file. Navigate to the./OFS_OIDF_PACK directory and execute the following command:
chmod 750 OFSAAIUpdate.sh
2. Execute the OFSAAIUpdate.sh file using the following command:
./OFSAAIUpdate.sh
3. Verify if the release is applied successfully by checking the log file generated in the installation folder. The log file such as OFS_OIDF_installation.log is stored in the /OFS_OIDF_PACK/OFS_OIDF/logs/ directory. You can ignore the ORA-00001, ORA-00955, ORA-02260, ORA-01031, and ORA-01430 errors in the log file. For any other errors, contact My Oracle Support.
The following sections provide information about the post-installation activities for the OIDF Application Pack v8.1.1.1.0 release.
Topics:
· Platform-related Post-installation Activities
· OIDF Related Post-installation Activities
After OIDF Application Pack is successfully installed, to perform the OFSAAI related post-installation activities, follow these steps:
1. Clear the application cache.
2. Navigate to the following directory depending on the configured web application server and delete the following files:
§ Tomcat:
<Tomcat installation folder>/work/Catalina/localhost/<Application name>/org/apache/jsp
§ WebLogic:
<Weblogic installation location>/domains/<Domain name>/servers/<Server name>/tmp/_WL_user/<Application name>/<auto generated folder>/jsp_servlet
§ Websphere:
<Websphere installation directory>/AppServer/profiles/<Profile name>/temp/<Node name>/server1/<Application name>/<.war file name>
3. Add umask 0027 in the .profile file of the UNIX account, which manages the webserver to ensure restricted access permissions.
4. Perform any necessary additional configuration mentioned in the Additional Configuration section in the Oracle Insurance Data Foundation Application Pack Installation and Configuration Guide Release 8.1.1.0.0.
5. Apply the OFSAAI Mandatory Patch 33663417.
See the Readme that is packaged with the Patch for instructions about installing the Patch.
6. Generate the application EAR or WAR file, and redeploy the application on the configured web application server. For more information on generating and deploying the EAR or WAR file, see the Create and Deploy the EAR/WAR Files section in the Oracle Insurance Data Foundation Application Pack Installation and Configuration Guide Release 8.1.1.0.0.
7. After the successful installation of the OIDF Application Pack v8.1.1.1.0 Release, restart all the OFSAAI services. For more information, see the Start the Infrastructure Services section in the Oracle Financial Services Advanced Analytical Applications Infrastructure Installation Guide Release 8.1.1.0.0.
This section provides the post-installation procedures for the OIDF Application Pack v8.1.1.1.0 release.
Topic:
All the seeded batches in the OIDF Application Pack are automatically assigned to the SYSADMN user during the installation process. To see batches in the Batch Maintenance menu, execute the following queries in the Config schema of the database.
Syntax:
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromUser','toUser','infodom');
end;
OR
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromuser','touser');
end;
· 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 you specify this parameter, the ownership of the batches of that infodom is changed.
For example:
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('SYSADMN','OIDFOP','OFSOIDFINFO’);
end;