This section provides detailed steps to upgrade the OFS BSP Application Pack.
Topics:
· Upgrade from Release 8.0.8.x.0 of OFS BSP on AIX or Solaris x86 Operating System
· Upgrade an Already Installed Application Pack From 8.0.8.0.0 or Later
· Install a New Application on an Existing OFSAA Instance from the Same Pack
· Install a New Application Pack on an Existing OFSAA Instance
Release 8.1.x.x.x of OFSAA supports the following upgrade scenario as explained in the following table:
ATTENTION:
Always ensure you run the upgrade installer only on the cloned environment.
Table 17: Upgrade Scenario
Scenario |
Upgrade Instructions |
|---|---|
Upgrade from OFS BSP 8.1.0.0.0 |
1. Run the Environment Check Utility tool and ensure that the hardware and software requirements are installed as per the OFS Analytical Applications Technology Matrix. 2. Update the Silent.props file present in the Release 8.1.1.0.0 pack. 3. Trigger the Release 8.1.1.0.0 installation. |
Upgrade from OFS BSP Release v8.0.8 on AIX or Solaris x86 Operating System |
Release v8.1.0.0.0 of OFS BSP is not certified for AIX and Solaris x86 Operating Systems. If you are currently running OFSAA v8.0.x on AIX or Solaris x86 Operating Systems and plan to upgrade to Release v8.1.0.0.0, then you must migrate from AIX or Solaris x86 to Linux or Solaris SPARC. See the MOS Doc ID 2700084.1 for details. |
Upgrade an Already Installed Application Pack From 8.0.8.0.0 or Later Example: You are using an application pack in release 8.0.8.0.0 and now want to upgrade it to Release 8.1.0.0.0. |
1. Run the Environment Check Utility tool and ensure that the hardware and software requirements are installed as per the OFS Analytical Applications Technology Matrix. 2. Clone your existing environment to the 8.1.0.0.0 OFS Analytical Applications Technology Matrix. 3. Update the Silent.props file present in the Release 8.1.0.0.0 pack. 4. Update the OFS_BSP.PACK.xml file to enable ONLY the existing installed applications. 5. Trigger the installation. |
Release v8.1.1.0.0 of OFS BSP is not certified for AIX and Solaris x86 Operating Systems. If you are currently running OFSAA v8.0.x on AIX or Solaris x86 Operating Systems and plan to upgrade to Release v8.1.1.0.0, then you must migrate from AIX or Solaris x86 to Linux or Solaris SPARC. See the MOS Doc ID 2700084.1 for details.
Before you plan to install/upgrade any of your application packs to Release 8.1.0.0.0, ensure that all the application packs in your current OFSAA instance are available in the Release 8.1.0.0.0 version. Contact My Oracle Support for more information about the release version details.
ATTENTION:
The minimum supported version is 8.0.8.0.0. If upgrading from a release before 8.0.8.0.0, then first upgrade to 8.0.8.0.0 or later. After this step, you can upgrade to 8.1.1.0.0 or later.
1. Backup the following environment files from the OFS_BSP_PACK>/schema_creator/conf directory:
§ Database
§ OFS_BSP_PACK.xml
§ OFS_BSP_SCHEMA_IN.xml
§ OFSAAI_InstallConfig.xml
2. See the OFS Analytical Applications Technology Matrix for the hardware and software required to upgrade to OFS AAI 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.
4. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
ATTENTION:
You must apply the OFS AAI patch 32530173 in case of Pack-on-Pack v8.1.1.0.0 installation. Do not apply this patch, if you have already applied it as part of another application pack’s installation.
You are upgrading the application pack from Release 8.1.0.0.0 or later to Release 8.1.1.0.0.
Clone your existing environment to the 8.1.1.0.0 Tech Stack. For more information, see the OFSAA Cloning Reference Guide for:
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_BSP_PACK/appsLibConfig/conf directory.
2. Open the Silent.props file and edit only the following parameters:
Table 18: Parameters for the Silent.props File
Property Name |
Description of Property |
Permissible Values |
Comments |
|---|---|---|---|
UPLOAD_MODEL |
To perform the Model Upload. |
0: No 1: Yes |
Mandatory |
MODEL_TYPE |
The released data model or a customized data model. |
0: Released 1: Customized |
Mandatory only if you want to upload the data model. |
DATAMODEL |
The path for the customized data model. |
Not Applicable |
Mandatory only if you want to upload the customized data model. |
DM_DIRECTORY |
The file name for the customized data model. |
Not Applicable |
Mandatory only if you want to upload the customized data model. |
APPFTP_LOG_PATH |
Infodom Maintenance log path (to be created) for the new Infodom for applayer |
Not Applicable |
# Mandatory if this an App Layer Installation and if you want to create a new infodom # That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0 |
DBFTP_LOG_PATH |
Infodom Maintenance log path (to be created) for the new Infodom for DBLayer |
Not Applicable |
# Mandatory if this an App Layer Installation and if you want to create a new infodom # That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0 |
Update the OFS_BSP_PACK.xml file. Enable only the existing installed applications.
The OFS_PACK_PACK.xml file holds details on the various products that are packaged together in the OFS BSP Applications Pack.
This section details the various tags/ parameters available in the file and the values that must be updated. Prior to installing the OFS BSP Applications Pack, it is mandatory to update this file.
To configure the OFS_BSP_PACK.xml file, follow these steps:
1. Navigate to the OFS_BSP_PACK>/conf directory.
2. Open the OFS_BSP_PACK.xml file in a text editor.
3. Configure the OFS_BSP_PACK.xml file as mentioned in the following table.
Figure 21: Sample OFS_BSP_PACK.xml File
Table 19: OFS_BSP_PACK.xml File Parameters
Tag Name |
Attribute Name |
Value you must enter |
Comments |
|---|---|---|---|
APP_ID
|
ENABLE |
· YES for existing applications that you want to upgrade. |
Set this attribute-value to YES for every APP_ID which you want to install or upgrade. |
1. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
2. Enter the following command in the console to execute the application pack installer.
./setup.sh SILENT
3. The installer proceeds with the Pre-Installation Checks.
4. Enter the OFSAA Processing Tier FTP/SFTP password value and proceed, when prompted in the command prompt.
Figure 22: OFSAA Processing Tier FTP/SFTP Password Prompt
5. The process displays the OFSAA License. Enter Y and proceed.
Figure 23: Accept the OFSAA License Agreement
6. The OFS AAI installation begins.
Figure 24: OFS AAI Installation
Data Model Upload may take several hours to complete.
7. The OFSAA Infrastructure installation performs a post-install check automatically on the successful installation of the product.
Figure 25: Installation In Progress
Congratulations! Your installation is complete.
See the following logs files for more information:
· Pack_Install.log file in the OFS_BSP/logs/ directory.
· Infrastructure installation log file(s) located at OFS_BSP_PACK/OFS_AAI/logs/ directory
· OFS_BSP_installation.log file in the OFS_BSP_PACK/OFS_BSP/logs directory
· Model Upload log files at the location specified for the parameters APPFTP_LOG_PATH and DBFTP_LOG_PATH in the Silent.props file.
You are upgrading the application pack from Release 8.0.8.0.0 or later to Release 8.1.0.0.0.
Clone your existing environment to the 8.1.0.0.0 Tech Stack. For more information, see the OFSAA Cloning Reference Guide for:
Update the Silent.props file present in the Release 8.1.0.0.0 pack.
Most parameters in the Silent.props file for 8.1.0.0.0 have default values. Before triggering the installation, ensure that you review them thoroughly and update as required.
1. Navigate to the OFS_BSP_PACK/appsLibConfig/conf directory.
2. Open the Silent.props file and edit only the following parameters:
Table 20: Parameters for the Silent.props File
Property Name |
Description of Property |
Permissible Values |
Comments |
|---|---|---|---|
UPLOAD_MODEL |
To perform the Model Upload. |
0: No 1: Yes |
Mandatory |
MODEL_TYPE |
The released data model or a customized data model. |
0: Released 1: Customized |
Mandatory only if you want to upload the data model. |
DATAMODEL |
The path for the customized data model. |
Not Applicable |
Mandatory only if you want to upload the customized data model. |
DM_DIRECTORY |
The file name for the customized data model. |
Not Applicable |
Mandatory only if you want to upload the customized data model. |
APPFTP_LOG_PATH |
Infodom Maintenance log path (to be created) for the new Infodom for applayer |
Not Applicable |
# Mandatory if this an App Layer Installation and if you want to create a new infodom # That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0 |
DBFTP_LOG_PATH |
Infodom Maintenance log path (to be created) for the new Infodom for DBLayer |
Not Applicable |
# Mandatory if this an App Layer Installation and if you want to create a new infodom # That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0 |
Update the OFS_BSP_PACK.xml file. Enable only the existing installed applications.
The OFS_PACK_PACK.xml file holds details on the various products that are packaged together in the OFS BSP Applications Pack.
This section details the various tags/ parameters available in the file and the values that must be updated. Prior to installing the OFS BSP Applications Pack, it is mandatory to update this file.
To configure the OFS_BSP_PACK.xml file, follow these steps:
1. Navigate to the OFS_BSP_PACK>/conf directory.
2. Open the OFS_BSP_PACK.xml file in a text editor.
3. Configure the OFS_BSP_PACK.xml file as mentioned in the following table.
Figure 26: Sample OFS_BSP_PACK.xml File
Table 21: OFS_BSP_PACK.xml File Parameters
Tag Name |
Attribute Name |
Value you must enter |
Comments |
|---|---|---|---|
APP_ID
|
ENABLE |
· YES for existing applications that you want to upgrade. |
Set this attribute-value to YES for every APP_ID which you want to install or upgrade. |
1. Log in to OFSAA Infrastructure Config Schema and execute the following SQL query:
ALTER TABLE CONFIGURATION MODIFY PARAMNAME VARCHAR2 (100 CHAR);
2. Enter the following command in the console to execute the application pack installer.
./setup.sh SILENT
3. The installer proceeds with the Pre-Installation Checks.
4. Enter the OFSAA Processing Tier FTP/SFTP password value and proceed, when prompted in the command prompt.
Figure 27: OFSAA Processing Tier FTP/SFTP Password Prompt
5. The process displays the OFSAA License. Enter Y and proceed.
Figure 28: Accept the OFSAA License Agreement
6. The OFS AAI installation begins.
Figure 29: OFS AAI Installation
Data Model Upload may take several hours to complete.
7. The OFSAA Infrastructure installation performs a post-install check automatically on the successful installation of the product.
Figure 30: Installation In Progress
Congratulations! Your installation is complete.
See the following logs files for more information:
· Pack_Install.log file in the OFS_BSP/logs/ directory.
· Infrastructure installation log file(s) located at OFS_BSP_PACK/OFS_AAI/logs/ directory
· OFS_BSP_installation.log file in the OFS_BSP_PACK/OFS_BSP/logs directory
· Model Upload log files at the location specified for the parameters APPFTP_LOG_PATH and DBFTP_LOG_PATH in the Silent.props file.
Follow the steps mentioned in the Post Upgrade Steps section.
The following steps need to be carried out after you complete the upgrade procedure:
· Remove ContextDocLoader from the web.xml File
To remove the ContextDocLoader from the web.xml file, follow these steps:
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>
------------------------------------------------------------------------------------------------------
4. Create and deploy the EAR/WAR file.
After completing the upgrade process, verify data for the correct schema name (OWNER) and Tablespace (OUTPUT_TABLESPACE) values in the FSI_DB_INFO table in the atomic schema.