3 Applying This Maintenance Level Release

To apply this ML release, follow these steps:

  1. Load the .profile and make sure that $FIC_HOME corresponds to the proper environment where the patch application is required.
  2. Start the OFSAAI Services.
  3. Download and copy the 39694032_GENERIC.zip file (in Binary mode) to the server where OFSAAI is installed.
  4. Navigate to the <USER_PATCH_DIR> directory and extract the contents of the patch archive file using the following command:

    unzip -a <name of the archive file to be unzipped>

    For example: unzip -a 39694032_GENERIC.zip

    Note:

    <USER_PATCH_DIR> is the directory containing the <patch>.zip file copied in step 3. "-a" option is mandatory to unzip the patch. In case, you notice an error message: “unzip: not found [No such file or directory]” when the package is not installed, contact your UNIX Administrator.
    The list of files available when you unzip the folder is as follows:
    • validateXMLInputs.jar
    • SolSetup.jar
    • server_profile.sh
    • replace_placeholders.sh
    • OFS_CRR_mapping.tsv
    • OFS_CRR_installer_files.zip
    • jakartaee-migration-1.0.8-shaded.jar
    • jakarta_conversion.sh
    • install.sh
    • generate_resolved_properties.sh
    • OFSCRR_8.1.2.12.0_Readme.htm
  5. Navigate to the <USER_PATCH_DIR>/39694032/bin directory and grant 755 permission using the following command: $ chmod 755 *
  6. Update the parameter ##RR_UPLOAD_MODEL## in the <USER_PATCH_DIR>/39694032/conf/ PatchConfig.xml file to 1.
  7. Update the variables ##OFS_RRS_DATA_TBSP## and ##OFS_RRS_INDEX_TBSP## in PatchConfig.xml. These attributes correspond to the Data and Index Tablespace values found in OFS_CRR_SCHEMA_OUTPUT.xml, which was generated during the installation process. Additionally, the ##EXECUTE_PRE_AND_POST_SCRIPTS## attribute controls the execution of pre- and post-scripts during installation:
    • Setting the value to 1 executes the pre- and post-scripts.
    • Setting the value to 0 skips their execution.
    For CRR 8.1.2.12, it is mandatory to set this attribute to 1 to ensure pre- and post-scripts are executed.
  8. Navigate to <USER_PATCH_DIR>/39694032/conf/ params.conf directory and provide the following place holder values.
    • WEBSERVER_TYPE=
    • WEBSERVER_VERSION=
  9. Install the patch by executing the install.sh command as follows: $ ./install.sh.

    Note:

    • While applying a patch, you might get the following warning in your Putty session, but you can ignore this.
    • WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$ 1 (file:/../<FICHOME>/ficapp/common/FICServer/lib/jaxb-impl.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
    • WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
    • WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    • WARNING: All illegal access operations will be denied in a future release
  10. Check if the ML release is applied successfully by verifying the patch install logs under the <USER_PATCH_DIR>/39694032/logs directory. Contact My Oracle Support in case of any errors.
  11. After the patch is installed successfully, re-create the OFSAA EAR/WAR file and re-deploy a new EAR/WAR file on the web application server.
  12. Restart the OFSAA App server and the Webserver.

    For more information on the application configuration, see Administration Guide on OHC.