8       Upgrade

This section includes the procedures for the various upgrade scenarios supported by Oracle Insurance Accounting Analyzer Release 8.1.1.0.0.

Topics:

·        Upgrade Scenarios

·        Mandatory Patches

·        Prepare for Upgrade

·         Install a New Application Pack on an Existing OFSAA Instance

Upgrade Scenarios

This section details the upgrade scenarios for the Oracle Insurance Accounting Analyzer application.

NOTE:   

Always ensure you run the upgrade installer only on the cloned environment.

NOTE:   

If you are adding an additional application, you must run the schema creator utility.

Mandatory Patches

The patch in the following table must be installed after completing all the upgrade steps.

Prepare for Upgrade

Before you plan to install or upgrade any of your application packs to Release 8.1.1.0.0, ensure that all the application packs in your current OFSAA instance are available in the Release 8.1.1.0.0 version. Contact My Oracle Support for more information about the release version details.

NOTE:   

Ensure to revert any customized data model changes done without performing data model upload before upgrading.

ATTENTION:   

The minimum supported version is 8.1.0.1.0. If upgrading from a release before 8.1.0.1.0, then first upgrade to 8.1.0.1.0. After this step, you can upgrade to 8.1.1.0.0.

1.     Backup the following environment files from their respective directories:

§       Database schema

§       OFS_IIA_PACK.xml

§       OFS_IIA_SCHEMA_IN.xml

§       OFSAAI_InstallConfig.xml

2.     See the OFS Analytical Applications Technology Matrix  for the hardware and software required to upgrade to Oracle Insurance Accounting Analyzer Release 8.1.1.0.0.

3.     Enable unlimited cryptographic policy for Java. For more information, see the Enabling Unlimited Cryptographic Policy section in the OFS Analytical Applications Infrastructure Administration Guide.

4.     Clone your environment.

There is a consistent need for a faster and effective approach to replicating an existing OFSAA instance for further project developments, that is, setting up OFSAA instances that are exact copies of the current OFSAA instance. For more information, see the Clone your Existing Environment section.

Clone Your Existing Environment

Initializing the Upgrade

Update the OFS_IIA_PACK.xml File

Update the Silent.props File in Release 8.1.1.0.0 Pack

Trigger the Installation

Verify the Log File Information for Upgrade

Post Installation Steps for Upgrade

Clone Your Existing Environment

Clone your existing environment to the 8.1.1.0.0 OFS Analytical Applications Technology Matrix. For more information, see the OFSAA Cloning Reference Guide.

Initializing the Upgrade

To initialize the upgrade, follow these steps:

1.     Log in to My Oracle Support and search for 32506459 under the Patches & Updates tab.

2.     Copy the archive file to your OFSAA server in Binary mode.

NOTE:   

The archive files are different for every operating system like Solaris, and RHEL, or Oracle Linux.

3.     Log in to the OFSAA Server with user credentials that were used to install OFSAA.

4.     Shut down all the OFSAAI Services. See the Stop the Infrastructure Services and Start the Infrastructure Services section in the OFS AAI Release 8.1.1.0.0 Installation and Configuration Guide for details.

5.     Execute the command:

chmod -R 750 $FIC_HOME

6.     If you have Unzip utility, skip to the next step. Download the Unzip utility (OS-specific) and copy it in Binary mode to the directory that is included in your PATH variable, typically $HOME path or directory in which you have copied the 8.1.1.0.0 installer.

Uncompress the unzip installer file using the command:

uncompress unzip_<os>.Z

NOTE:   

In case you notice an error message “uncompress: not found [No such file or directory]” when the package is not installed, contact your UNIX administrator.

7.     Give execute permission to the file using the command:

chmod 751 OFS_IIA_81000_<OperatingSystem>.zip.

8.     Extract the contents of the Oracle Financial Services Insurance Accounting Analyzer 8.1.1.0.0 in the Download Directory installer archive file using the command:

unzip_<os> -a <name of the file to be unzipped>

NOTE:   

The above “-a” option is mandatory to unzip the archive file.

For example: unzip_aix -a OFS_AAAI_81000_<OperatingSystem>.zip

9.     Give execute permission to the archive file. Navigate to the path where the directory OFS_IIA_PACK exists and execute the command:

chmod –R 755 OFS_IIA_PACK

10.  Execute the user .profile

11.  Navigate to the path /OFS_IIA_PACK/schema_creator/conf and modify the file OFS_IIA_SCHEMA_IN.xml by providing the existing values to the parameters JDBC_URL, JDBC_DRIVER, Host, Setupinfo name, schema names (config and atomic), password, default tablespace, Infodom, Quota as per the previous version.

12.  Navigate to the path/OFS_IIA_PACK/schema_creator/bin, and execute the  osc.sh file using the following command:

./osc.sh -s

NOTE:   

Steps 11 and 12 are required to generate the file OFS_IIA_SCHEMA_OUTPUT.xml.

Update the OFS_IIA_PACK.xml File

Update the OFS_IIA_PACK.xml File. Enable only the existing installed applications.

The OFS_IIA_PACK.xml file contains details on the various products that are packaged in the Oracle Insurance Accounting Analyzer application pack. This section provides information about the various tags and parameters available in the file and the values that you must update. Before installing Oracle Insurance Accounting Analyzer, it is mandatory to update this file.

To configure the OFS_IIA_PACK.xml file, follow these steps:

1.     Navigate to the OFS_IIA/conf directory.

2.     Open the OFS_IIA_PACK.xml file in a text editor.

3.     Configure the OFS_IIA_PACK.xml file as mentioned in the following table.

Update the Silent.props File in Release 8.1.1.0.0 Pack

Update the Silent.props file present in the Release 8.1.1.0.0 pack. Most parameters in the Silent.props file for 8.1.1.0.0 have default values. Before triggering the installation, ensure that you review them thoroughly and update them as required.

1.     Navigate to the OFS_IIA/appsLibConfig/conf directory.

2.     Edit the Silent.props file and specify the parameters as per the requirements.

SILENT installation is achieved through a properties file (Silent.props) that must be updated with proper values, before attempting to install using the silent mode. The following table lists all the properties that need to be specified.

3.     Configure the Silent.props file as mentioned in the following table. Open the Silent.props file and edit only the following parameters.

Trigger the Installation

To trigger the installation, follow these steps:

1.     Navigate to the path OFS_IIA_PACK/bin, and enter the following command in the console to execute the application pack installer with the Silent option.

./setup.sh SILENT

2.     The installer proceeds with the Pre-Installation Checks.

3.     Enter the OFSAA Processing Tier FTP/SFTP password value and proceed, when prompted in the command prompt.

The process displays the OFSAA License. Enter Y and proceed.

4.     The OFS Insurance Accounting Analyzer installation begins.

5.     Data Model Upload may take several hours to complete. You can check the installation logs in the following location: OFS_IIA/OFS_IIA/logs

The OFSAA Infrastructure installation performs a post-install check automatically on the successful installation of the product.

Secure your OFSAA Infrastructure. For more information, see the Security Guide in the OHC Documentation Library.

6.     Execute the update_dq_batches_optional_params.sql script, which is available in the $FIC_HOME/Post_AAI_Migration directory.  

Congratulations! Your installation is complete.

Verify the Log File Information for Upgrade

See the following logs files for more information:

·        Verify if the release is applied successfully by checking the log file generated in the locations mentioned in the section Verify the Log File Information.

·        You can also verify the OFSAAI log files from the OFS_IIA_PACK/OFS_AAAI_PACK/logs directory.

·        Verify the Model Upload log file available in the ftpshare/<INFODOM>/logs directory.

·        Verify if the release is applied successfully by checking the log file generated in the OFS_IIA_PACK/OFS_IIA/logs installation directory. You can ignore ORA-00001, ORA-00955, ORA-02260, ORA-01430, ORA-02298 errors in the log file. In case of any other errors, contact Oracle Support.

You can ignore the ORA-00001 error in the log file available in the path OFS_IIA_PACK/schema_creator/logs.

NOTE:   

Ignore all the warnings in the installation log. For any issues contact Oracle Support.

·        Verify if the Data Model is uploaded successfully by checking the log file generated as per the directory/path mentioned in Silent.props for the

·        Verify the Update.log file located at $FIC_HOME/utility/UpdateConstraints/logs directory which is created by the Update Constraint utility.

§       Execution status information of the utility is available against each Information domain. For success, “Update successful” message is displayed. If it is successful, verify the following references for new constraint names:

—    ftpshare/<INFODOM>/erwin/fipxml/<INFODOM>_DATABASE.xml

—    Constraint scripts under ftpshare/<INFODOM>/erwin/scripts/table

—    Constraint scripts under ftpshare/<INFODOM>/scripts

§       Object registration tables for constraints, REV_TAB_CONSTRAINTS,     REV_TAB_REF_CONSTRAINTS, REV_TAB_CONSTRAINT_COLUMNS.

§       Oracle Data Dictionary in the respective Atomic Schemas for each Infodom.

§       If you encounter errors in the Update.log file, identify and troubleshoot the failed Infodoms. Once you have completed the troubleshooting, execute the standalone utility for the failed Infodoms. For more information on executing the update constraints utility, see the Update Constraints Utility section, in the OFS AAAI Applications Pack Installation Guide0.

Post Installation Steps for Upgrade

Perform the following post-installation steps:

1.     Secure your OFSAA Infrastructure. For more information, see the OFSAA Security Guide in the OHC Documentation Library.

2.     After successful installation, follow these steps:

a.     Clear the application cache. Navigate to the following path depending on the configured web application server and delete the files.

§       Tomcat:
<Tomcat installation directory>/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 directory>/jsp_servlet

For WebLogic version 12.2.x.x, delete the directory named .WL_internal present in the <WebLogic installation location>/user_projects/domains/< Domain name >/applications/<context_name>.ear/META-INF/ directory, if it exists.

§       WebSphere:
<WebSphere installation directory>/AppServer/profiles/<Profile name>/temp/<Node name>/server1/<Application name>/<.war file name>

b.     Deploy the RPD and catalog file(s)

Note: Ensure that OBIEE 12.2.1.4.0 or OAS 5.5.0 is up and running.

Take a backup of the deployed IFRS17.rpd and IFRS17.catalog files from the OBIEE environment.

i.       Navigate to the respective folders. Copy the RPD and required Catalog files (as per the license agreement) in the server where the BI client tools are installed:

—    $FIC_HOME /OFS_IIA_DASHBOARDS/12.2.1.4.0/directory containing the IFRS17.rpd in the data model folder and archived

ii.     Modify the connection pool and set the properties.

iii.   Any customizations performed on the older rpd and web catalog files must be manually carried over to the newer ones post-deployment.

iv.   Clear OBIEE cache, if enabled.

v.     For more information on deploying RPD and webcat files, see the Deploying RPD and Web catalog Files section.

3.     Add umask 0027 in the .profile of the UNIX account which manages the WEB server to ensure restricted access permissions.

4.     Follow these steps to remove ContextDocLoader from the web.xml file:

a.     Navigate to $FIC_WEB_HOME/webroot/WEB-INF folder.

b.     Open the web.xml file in a text editor.

c.     Search for ContextDocLoader parameter and remove the following servlet entry:

<servlet> 

<servlet-name>context</servlet-name>

<servlet-class>com.ofs.fsapps.commonapps.core.summary.common.ContextDocLoade

r</servlet-class>

<load-on-startup>1</load-on-startup>

</servlet>

5.     Generate the application EAR/WAR file and redeploy the application onto your configured web application server. See Create and Deploy the EAR/WAR Files, for more information on generating and deploying the EAR/WAR files.

6.     Restart all the OFSAAI services. See the Stop the Infrastructure Services and Start the Infrastructure Services sections in the OFS AAI Release 8.1.1.0.0 Installation and Configuration Guide for details

7.     Verify the log files in the locations mentioned in the section Verifying the Log Files. You can also verify the OFSAAI log files from OFS_IIA_PACK/OFS_AAAI_PACK/logs directory.

8.     To configure OBIEE or OAS, follow the steps mentioned in the BI Analytics - OBIEE Server Configuration Steps section.

OBIEE Server Configuration Steps

Perform the following OBIEE server configuration steps. You can ignore the steps if OBIEE is already configured in your setup.

1.     Perform the following OBIEE presentation server configuration steps

a.     Navigate to the  <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory.

b.     Edit the file instanceconfig.xml.

c.     Insert the following code within xml tag <Views> </Views>.

<Charts>

<MaxVisibleColumns>50000</MaxVisibleColumns>

<MaxVisiblePages>25000</MaxVisiblePages>

<MaxVisibleRows>10000000</MaxVisibleRows>

<MaxVisibleSections>50000</MaxVisibleSections>

<JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>

</Charts>

d.     Insert the following code within xml tag <Views> </Views>.

<Table>

<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

<DefaultRowsDisplayedInDownload>6500</DefaultRowsDisplayedInDownload>

<MaxCells>4000000</MaxCells>

<MaxVisibleRows>140000</MaxVisibleRows>

</Table>

<Narrative>

<MaxRecords>500000</MaxRecords>

<DefaultRowsDisplayed>25</DefaultRowsDisplayed>

</Narrative>

e.     Save the file, and restart the BI services.

NOTE:   

Take a backup of the instanceconfig.xml file before making any changes.

2.     Perform the following RPD changes, to set the Early Warning Indicators 1 and 2:

a.     Open the Repository in Online or Offline mode.

b.     Select Manage and then select Variables.

c.     Navigate to hierarchy Repository select Variables then select Static.

d.     Modify EARLYWARNIND1 and EARLYWARNIND2 variable values as required.

e.     Save and commit the changes to RPD.

Note: You must redeploy the RPD on the BI server if you have made changes in the offline mode.

3.     For OBIEE reporting, configure the following:

a.     Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIJH directory. 

b.     Modify the config.xml file.

c.     The increased parameter value for the following tag:

<XMLP>

<InputStreamLimitInKB>40000</InputStreamLimitInKB>

<ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing>

</XMLP>

<DVT>

<InputStreamLimitInKB>40000</InputStreamLimitInKB>

</DVT>

d.     Save the config.xml file.

e.     Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory. 

f.       Modify the instanceconfig.xml file.

g.     Increase the parameter value for tag if already exists or add the following code

<Charts>

<MaxVisibleColumns>50000</MaxVisibleColumns>

<MaxVisiblePages>25000</MaxVisiblePages>

<MaxVisibleRows>100000</MaxVisibleRows>

<MaxVisibleSections>50000</MaxVisibleSections>

<JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>

</Charts>

and

<Pivot>

<MaxCells>1920000</MaxCells>

<MaxPagesToRollOutInDelivery>10000</MaxPagesToRollOutInDelivery>

<MaxVisibleColumns>50000</MaxVisibleColumns>

<MaxVisiblePages>100000</MaxVisiblePages>

<MaxVisibleRows>10000000</MaxVisibleRows>

<MaxVisibleSections>50000</MaxVisibleSections>

<DefaultRowsDisplayed>100000</DefaultRowsDisplayed>

</Pivot>

under <Views> tag

h.     Save the instanceconfig.xml file.

i.       Restart the BI Services.

Install a New Application Pack on an Existing OFSAA Instance

You have already installed an application pack from release 8.1.x.0.0 and now you want to install another application pack from Release 8.1.1.0.0.

For example, OFS IIA Pack is already installed and now you want to install OFS ALM Pack.

Execute the Schema Creator Utility Only for the New Pack

If the Schema Creator Output file (OFS_IIA_SCHEMA_OUTPUT.xml) EXISTS

Update the OFS_IIA_PACK.xml File for the Newly Licensed Pack

Update the Silent.Props File of the Newly Licensed Pack

Trigger the Installation

Verify the Log File Information

Post Installation Steps

NOTE:   

You must check the Compatibility Matrix to see if the new application to be installed is compatible with the installed applications.

Execute the Schema Creator Utility Only for the New Pack

To execute the schema creator, follow these steps:

NOTE:   

While defining the schema details for the applications, provide the same schema details given in the previous installation. The output file (OFS_IIA_SCHEMA_OUTPUT.xml) is generated as a result of the schema creation process.

1.     Edit the file OFS_IIA/schema_creator/conf/OFS_IIA_SCHEMA_IN.xml in a text editor. See Configure OFS_IIA_SCHEMA_IN.xml for values to modify in the XML file.

2.     Execute the utility with -s option.

For Example: ./osc.sh -s

3.     Follow the steps given in the section If the schema creator output file (OFS_IIA_SCHEMA_OUTPUT.xml) EXISTS  section. 

4.     Configure OFSAAI_InstallConfig.xml File is not required.

If the Schema Creator Output file (OFS_IIA_SCHEMA_OUTPUT.xml) EXISTS

If the Schema Creator Output file (OFS_IIA_SCHEMA_OUTPUT.xml) is available, follow the steps mentioned in the following sections.

Update the OFS_IIA_PACK.xml file

Update the OFS_IIA_PACK.xml file. Enable only the new applications.

The OFS_IIA_PACK.xml file contains details on the various products that are packaged in the Oracle Insurance Accounting Analyzer application. This section provides information about the various tags and parameters available in the file and the values that you must update. Before installing Oracle Insurance Accounting Analyzer, it is mandatory to update this file.

To configure the OFS_IIA_PACK.xml file, follow these steps:

1.     Navigate to the OFS_IIA_PACK/conf directory.

2.     Open the OFS_IIA_PACK.xml file in a text editor.

3.     Configure the OFS_IIA_PACK.xml file as mentioned in the following table.

Update the OFS_IIA_PACK.xml File for the Newly Licensed Pack

The OFS_IIA_PACK.xml file holds details on the various products that are packaged together in OFS Insurance Accounting Analyzer.

Update the OFS_IIA_PACK.xml file. Enable only the existing installed applications.

This section provides information about the various tags and parameters available in the file and the values that you must update. Before installing OFS IIA, it is mandatory to update this file.

To configure the OFS_IIA_PACK.xml file, follow these steps:

1.     Navigate to the OFS_IIA/conf directory.

2.     Open the OFS_IIA_PACK.xml file in a text editor.

3.     Configure the OFS_IIA_PACK.xml file as mentioned in the following table.

Update the Silent.Props File of the Newly Licensed Pack

Update the Silent.props file in the Release 8.1.x pack ONLY for the newly licensed applications.

Most parameters in the Silent.props file for 8.1.1.0.0 have default values. Before triggering the installation, ensure that you review them thoroughly and update them as required.

1.     Navigate to the OFS_IIA/appsLibConfig/conf directory.

2.     Configure the Silent.props file as mentioned in the following table. Open the Silent.props file and edit only the following parameters: 

Trigger the Installation

To trigger the installation, follow these steps:

1.     Navigate to the path OFS_IIA_PACK/bin, and enter the following command in the console to execute the application pack installer with the Silent option.

./setup.sh SILENT

2.     The installer proceeds with the pre-installation checks and starts the upgrade installation process.

3.     Enter the OFSAA Processing Tier FTP/SFTP password value and proceed, when prompted in the command prompt.

4.     The process displays the OFSAA License. Enter Y and proceed.

5.     The OFS IIA installation begins.

6.     Data Model Upload may take several hours to complete. You can check the installation logs in the following location: OFS_IIA/OFS_IIA/logs

Do not close the console until the installation is complete.

7.     Verify the log files.

Verify the Log File Information

Verify the log files in the locations mentioned in the section Verify the Log File Information. Additionally, you can verify the OFSAAI log files from OFS_IIA_PACK/OFS_AAAI_PACK/logs directory.

Post Installation Steps

Follow the steps mentioned in the Post Installation Steps section.

View OFSAA Product Licenses after Installation of Application Pack

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 OFS Analytical Applications Infrastructure User Guide Release 8.1.1.0.0.