- Installation Guide
- OFS ALM Release v8.1.2.2.0
- Installing this Release
2.2 Installing this Release
Note:
If you are installing OFS PCD Release 812 on the same Infodom (in an integrated environment) where OFS ALM, OFS FTP, and OFS BSP are installed, then the following order of installation is mandated:- OFS PCD
- OFS ALM
- OFS FTP
- OFS BSP
If you have already installed OFS PCD and planning to install the remaining applications, then you must apply the OFS PCD one-off patch 34985659.
- Log in to My Oracle Support and search for 34804698 under the Patches & Updates tab.
- Download the OFS ALM 8.1.2.2.0 ML Release archive file and copy to your OFSAA
server in Binary mode.
Note:
There are different archive files for different operating systems such as AIX, Solaris, and RHEL/OEL. - Stop all the OFS AAI services. For more information, see the Stopping Infrastructure Services section in the Oracle Financial Services Asset Liability Management Installation and Configuration Guide.
- Log in to the OFSAA server as a non-root user and navigate to the $FIC_HOME directory.
- Assign WRITE permission to the files/directories such as commonscripts,
EXEWebService, ficapp, ficweb, and ficdb using the command:
chmod -R 775 *
- If you have the Unzip utility, skip to the next step or 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.2.2.0 ML.- Uncompress the unzip installer file using the 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. - Assign EXECUTE permission to the utility using the
command:
chmod 751 unzip_<os>
For example,
chmod 751 unzip_aix
- Uncompress the unzip installer file using the command:
- Extract the contents of the 8.1.2.2.0 ML archive file using one of the
following commands:
unzip_<os> -a <name of the file to be unzipped>
OR
unzip –a <name of the file to be unzipped>
Note:
The “-a
” option is mandatory to unzip the archive file. For example: For AIX operating system,unzip_aix -a p 34804698_81220_AIX64.zip
- Update the parameters in the
params.conf
file present in theOFS_ALM_PACK/appsLibConfig/conf
directory. The update instructions are present in the file itself. Set UPLOAD_MODEL parameter to 1 to upload the Data Model.Note:
Model Upload Process: Input values required are 0 or 1.- 1 indicates Trigger Model Upload
- 0 indicates Skip Model upload process
If the value is 1, then choose a type of Model Upload from the following:- 0 indicates Released Data Model
- 1 indicates the Customized Data Model
If the value of the Model upload type is 1, then provide the inputs for the Data Model name and the path of the Data Model.
- Navigate to the
/OFS_ALM_PACK
directory to assign EXECUTE permission to the ML patch installer script using the command:chmod 755 OFSAAIUpdate.sh
- Complete the patch upgrade using the command:
./OFSAAIUpdate.sh
- Verify if the ML patch is applied successfully by checking the following log
files:
OFS_ALM_installation.log
file in/OFS_ALM_PACK/OFS_ALM/logs
directoryOFS_ALMBI_installation.log
file inOFS_ALM_PACK/OFS_ALMBI/logs
directoryOFSAAIUpdate.log
file in/OFS_ALM_PACK/logs
directory
You can ignore error codes ORA-00001, ORA-02292, ORA-00955, and ORA-02260 in the log file. For any other errors, contact My Oracle Support.
Note:
For upgrade on Hive Infodom, you may encounter an exception "PL/SQL: ORA-00942: table or view does not exist". You can ignore this error. - After successful installation of the ML, follow these steps:
- Execute .profile using the following command:
. $HOME/.profile
- Clear the application cache. Navigate to the following path depending on
the configured web application server and delete the 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>
- WebSphere:
<WebSphere installation directory>/AppServer/profiles/<Profile name>/temp/<Node name>/server1/<Application name>/<.war file name>
- Tomcat:
- Execute .profile using the following command:
- Delete the existing EAR or WAR file available in the
$FIC_HOME/ficweb
directory. - Install the OFSAAIRunner package. This is an optional step and applicable only if you have installed Oracle R Enterprise Edition (ORE). For more information, see Installing OFSAAIRunner package with enhancements for OFS AAI 8.1.2.2.0.
- Restart all the OFSAAI services. For more information, see the Starting Infrastructure Services section in the Oracle Financial Services Asset Liability Management Installation and Configuration Guide.
- Generate the application EAR or WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying the EAR or WAR file, see the Post Installation Configurations section in the Oracle Financial Services Asset Liability Management Installation and Configuration Guide.
- Configure the document upload settings. See the Configure Document Upload Settings section in the Oracle Financial Services Asset Liability Management Installation and Configuration Guide for more information.