This section includes the procedures for the various upgrade scenarios supported by OFS MRMM Release 8.1.1.0.0.
Topics:
· Upgrade from a MRMM Release 8.1.0.1.0 to MRMM Release 8.1.1.0.0
· Install OFS MRMM Application Pack v8.1.1.0.0 on an Existing OFSAA Instance
The possible upgrade scenarios and a high-level sequence of steps to complete the upgrade are summarized in this section.
Scenario |
Upgrade Instructions |
|---|---|
Upgrade from OFS MRMM Release 8.1.0.1.0 to OFS MRMM Release 8.1.1.0.0 |
1. Update the Silent.props file present in the Release 8.1.1.0.0 pack. 2. Trigger the Release 8.1.1.0.0 installation. 3. Update the .profile file. |
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.
1. Backup the following environment files from their respective directories:
§ OFS_MRMM_PACK.xml
§ OFS_MRMM_SCHEMA_IN.xml
§ OFSAAI_InstallConfig.xml
§ Silent.props
2. See the OFS Analytical Applications Technology Matrix for the hardware and software required to upgrade to OFS MRMM 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 and Configuration Guide.
You are upgrading the application pack from OFS MRMM Release 8.1.0.1.0 to Release 8.1.1.0.0.
1. Download the OFS MRMM Application Pack Release 8.1.1.0.0 installer (Bug Number: 32457594) from My Oracle Support.
2. Copy the archive file to your OFSAA server in Binary mode.
NOTE:
The archive files are different for RHEL/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:
If you receive 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_MRMM_81100_<OperatingSystem>.zip.
8. Extract the contents of the Oracle Financial Services Market Risk Measurement and Management Application Pack 8.1.1.0.0 in the Download Directory installer archive file using the command:
unzip <name of the file to be unzipped>
9. Give execute permission to the archive file. Navigate to the path where the directory OFS_MRMM_PACK exists and execute the command:
chmod -R 755 OFS_MRMM_PACK
10. Identify a
directory for installation and set the same in the user .profile
file as below:
FIC_HOME=< OFSAA Installation Directory >
export FIC_HOME
11. Execute the user .profile
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 as required.
1. Navigate to the OFS_MRMM_PACK/appsLibConfig/conf directory. The Silent.template available in this path is populated with default values.
2. Ensure to modify the template in the directory. Create a copy of this file and rename the copy as Silent.props.
3. 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.
4. Configure the Silent.props file as mentioned in the following table. Open the Silent.props file and edit only the following parameters.
NOTE:
Retain the same values in silent.props as in version 8.1.0.1.0.
Property Name |
Description of Property |
Permissible values |
Comments |
|---|---|---|---|
LOG_MODE |
Specify Log Mode |
1
= Debug Mode |
Password
will be printed in the log file |
SEGMENT_1_CODE |
Specify the MRMM Segment Code. |
User Input |
Enter the Segment name in UPPERCASE. |
APPFTP_LOG_PATH |
Specify
the Infodom Maintenance log path(to be created) for the new Infodom |
User Input |
|
DBFTP_LOG_PATH |
Specify
the Infodom Maintenance log path(to be created) for the new Infodom |
User Input |
|
UPLOAD_MODEL |
Specify whether you want to perform Model Upload. |
0
= If you have already performed Model Upload and want to skip
model upload process |
|
MODEL_TYPE |
Specify whether you want to use the released data model or customized data model for model upload process. |
#
0 = If you want to upload the released data model |
|
DATAMODEL |
Specify
the path (DM_DIRECTORY) and file (DATAMODEL) name for the customized
data model |
User Input |
|
ETL_APPSRC_TYPE |
Please specify if you want to create new ETL App or Src pair or use an existing one. |
0
= If you want to create a new ETL App or Src pair |
|
ETL_SRC_1_DESC |
ETL Market Risk Trade source description. |
STAGE_MR_TRADE |
Please
give description for the ETL App or Src pair. |
ETL_SRC_2_DESC |
ETL Market Risk Reference source description. |
STAGE_MR_REFERENCE |
Please
give description for the ETL App or Src pair. |
ETL_SRC_3_DESC |
ETL Market Risk Processing source description. |
MR_PROCESSING |
Please
give description for the ETL App or Src pair. |
ETL_SRC_4_DESC |
ETL Market Risk Processing source description. |
STAGING |
Please
give description for the ETL App/Src pair. |
ETL_SRC_1_NAME |
ETL Market Risk Trade source name. |
STAGE_MR_TRADE |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_2_NAME |
ETL Market Risk Reference source name. |
STAGE_MR_REFERENCE |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_3_NAME |
ETL Market Risk Processing source name. |
MR_PROCESSING |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_4_NAME |
ETL Market Risk Processing source name. |
STAGING |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
To trigger the installation, follow these steps:
1. Navigate to the path OFS_MRMM_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.
Figure 40: Silent Mode of Installation

3. The OFS MRMM installation begins.
4. After Data Model Upload verify the installation logs in the following location: OFS_MRMM_PACK/OFS_MRMM/logs
The OFSAA Infrastructure installation performs a post-install check automatically on the successful installation of the product.
Congratulations! Your installation is complete.
See the following logs files for more information:
· Verify the log files in the locations mentioned in section Verify the Log File Information.
· Verify the Model Upload log file available in the ftpshare/<INFODOM>/logs directory.
· Verify if the Data Model is uploaded successfully by checking the log file generated as per the directory or path mentioned in the Silent.props file.
NOTE:
You can ignore warnings in the installation log. In case of any issues, contact Oracle Support.
For pack on pack installation, you can ignore the warnings and following errors that might be logged in the installation log:
· Object already exists
· Unique constraint violated
Download the mandatory OFSAAI One-off patch (ID: 32548944) from My Oracle Support (MOS) and apply the patch.
After successful installation, follow these steps:
1. Secure your OFSAA Infrastructure. For more information, see the OFSAA Security Guide in the OHC Documentation Library.
2. 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>
3. Deploy the RPD and catalog file (or files).
NOTE: Ensure that OBIEE 12.2.1.4.0 or OAS 5.5.0 is up and running.
· Take a backup of the deployed MRMM_BI.rpd and MRMM_BI.catalog files from the OBIEE environment.
a. Navigate to the folder $FIC_HOME/MRMM_BI/RPD/ which contains MRMM_BI.rpd and $FIC_HOME/MRMM_BI/catalog/ which contains MRMM_BI.catalog and copy the files in the server where the BI client tools are installed:
b. Modify the connection pool and set the properties.
c. Any customizations performed on the older rpd and web catalog files must be manually carried over to the newer ones post-deployment.
d. Clear OBIEE cache, if enabled.
e. For more information on deploying RPD and web catalog files, see OBIEE Configuration - Deploy OFS MRMM Analytics.
4. Add umask 0027 in the .profile of the UNIX account which manages the web server to ensure restricted access permissions.
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 or WAR files.
6. After the successful installation, restart all the OFSAAI services. See the Stop the Infrastructure Services and Start the Infrastructure Services section for details.
NOTE:
· For enabling the Right to be Forgotten, see Right to be Forgotten.
· For enabling Data Redaction, see the Data Redaction section. For more details, see Data Redaction section, under Data Security and Data Privacy chapter in the OFS Analytical Applications Infrastructure Administration and Configuration Guide.
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/OracleBIPresentationServicesComponent/coreapplication_obips1> directory.
b. Edit the instanceconfig.xml file.
c. Insert the following code within the 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 the 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.
You have already installed an application pack from release 8.1.1.0.0 and now you want to install another application pack from Release 8.1.1.0.0. For example, OFS ALM Pack is already installed and now you want to install OFS MRMM Pack.
NOTE:
You must check the Compatibility Matrix to see if the new application to be installed is compatible with the installed applications.
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_MRMM_SCHEMA_OUTPUT.xml) is generated as a result of the schema creation process.
1. Edit the file OFS_MRMM_PACK/schema_creator/conf/OFS_MRMM_SCHEMA_IN.xml in a text editor. See Configure OFS_MRMM_SCHEMA_IN.xml for values to modify in the XML file.
2. Execute the utility with -s option.
For example: ./osc.sh -s
3. Configuring the OFSAAI_InstallConfig.xml file is not required.
The OFS_MRMM_PACK.xml file contains details on the various products that are packaged in the OFS MRMM 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 OFS MRMM, it is mandatory to update this file.
To configure the OFS_MRMM_PACK.xml file, follow these steps:
1. Navigate to the OFS_MRMM_PACK/conf directory.
2. Open the OFS_MRMM_PACK.xml file in a text editor.
3. Configure the OFS_MRMM_PACK.xml file as mentioned in the following table.
Figure 41: Sample OFS_MRMM_PACK.xml File

Tag Name |
Attribute Name |
Value you must enter |
Comments |
|---|---|---|---|
APP_ID |
ENABLE |
· YES for applications you want to install. · NO for applications that are already installed. |
Set this attribute-value to YES for every APP_ID which you want to install or upgrade. |
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 as required.
1. Navigate to the OFS_MRMM_PACK/appsLibConfig/conf directory. The Silent.template available in this path is populated with default values.
2. Ensure to modify the template in the directory. Create a copy of this file and rename the copy as Silent.props.
3. 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.
4. Configure the Silent.props file as mentioned in the following table. Open the Silent.props file and edit only the following parameters.
Property Name |
Description of Property |
Permissible values |
Comments |
|---|---|---|---|
LOG_MODE |
Specify Log Mode |
1
= Debug Mode |
Password
will be printed in the log file |
SEGMENT_1_CODE |
Specify the MRMM Segment Code. |
User Input |
Enter the Segment name in UPPERCASE. |
APPFTP_LOG_PATH |
Specify
the Infodom Maintenance log path(to be created) for the new Infodom |
User Input |
|
DBFTP_LOG_PATH |
Specify
the Infodom Maintenance log path(to be created) for the new Infodom |
User Input |
|
UPLOAD_MODEL |
Specify whether you want to perform Model Upload. |
0
= If you have already performed Model Upload and want to skip
model upload process |
|
MODEL_TYPE |
Specify whether you want to use the released data model or customized data model for model upload process. |
#
0 = If you want to upload the released data model |
|
DATAMODEL |
Specify
the path(DM_DIRECTORY) and file(DATAMODEL) name for the customized
data model |
User Input |
|
ETL_APPSRC_TYPE |
Please specify if you want create new ETL App or Src pair or use an existing one. |
0
= If you want to create a new ETL App or Src pair |
|
ETL_SRC_1_DESC |
ETL Market Risk Trade source description. |
STAGE_MR_TRADE |
Please
give description for the ETL App or Src pair. |
ETL_SRC_2_DESC |
ETL Market Risk Reference source description. |
STAGE_MR_REFERENCE |
Please
give description for the ETL App or Src pair. |
ETL_SRC_3_DESC |
ETL Market Risk Processing source description. |
MR_PROCESSING |
Please
give description for the ETL App or Src pair. |
ETL_SRC_4_DESC |
ETL Market Risk Processing source description. |
STAGING |
Please
give description for the ETL App/Src pair. |
ETL_SRC_1_NAME |
ETL Market Risk Trade source name. |
STAGE_MR_TRADE |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_2_NAME |
ETL Market Risk Reference source name. |
STAGE_MR_REFERENCE |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_3_NAME |
ETL Market Risk Processing source name. |
MR_PROCESSING |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
ETL_SRC_4_NAME |
ETL Market Risk Processing source name. |
STAGING |
Specify the ETL Application and Source Name in the ETL Area Definitions to be deployed. |
To trigger the installation, follow these steps:
1. 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 Pre-installation Checks.
Figure 42: Silent Mode Installation

3. The OFS MRMM installation begins.
Figure 43: OFS MRMM Silent Mode Installation
4. After Data Model Upload verify the installation logs in the following location: OFS_MRMM_PACK/OFS_MRMM/logs
Do not close the console until the installation is complete.
Figure 44: Silent Mode Installation in Progress
Figure 45: Silent Mode Installation Complete

Congratulations! Your installation is complete.
Verify the log files in the locations mentioned in section Verify the Log File Information.
Follow the steps mentioned in the Post Installation Steps section.