11.4.4 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:
   1. 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>

   2. 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 Liquidity_Risk_Management_Pack.rpd and Liquidity_Risk_Management_Pack.catalog files from the OBIEE environment.

      1. Navigate to the following RPD and catalog 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_LRM_DASHBOARDS/12.2.1.4.0/datamodel directory containing the Liquidity_Risk_Management_Pack.rpd in the datamodel directory and archived.
         • Liquidity_Risk_Management_Pack.catalog, Bank of Thailand.catalog, BNM.catalog, Deposit Insurance.catalog and HKMA LMR.catalog files in the $FIC_HOME/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog directory.
      2. Modify the connection pool and set the properties.
      3. Any customizations performed on the older rpd and web catalog files must be manually carried over to the newer ones post-deployment.
      4. Clear OBIEE cache, if enabled.
      5. For more information on deploying RPD and webcatalog files, see the RPD and Catalog Deployment 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:
   1. Navigate to $FIC_WEB_HOME/webroot/WEB-INF folder.
   2. Open the web.xml file in a text editor.
   3. 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 or WAR file and redeploy the application onto your configured web application server. See Create and Deploy the EAR or 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.2.0.0 Installation and Configuration Guide for details.
7. Resave the hierarchies HLRM454, HLRM0482, HLRM0471, HLRM205.
8. To configure OBIEE or OAS, follow the steps mentioned in the OBIEE Server Configuration for Upgrade section.