ATTENTION |
Before you begin the installation, configure and execute the following files: Configure the OS File System Settings and Environment Settings in the .profile File Configure OFS_HM_PACK.xml File |
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 the Data Redaction section, under Data Security and Data Privacy chapter in the OFS Analytical Applications Infrastructure Administration Guide. |
Prerequisite Patches
You must install the patches mentioned in the following table:
Table 24: Mandatory Patches
One-off Patch |
Description |
| 31545589 | This is a mandatory one-off patch if you are installing pack on pack. |
| 31654438 | This is a mandatory one-off patch if you are installing pack on pack. |
| 31605076 | Access to features owing to the additional license functionality that gets installed through the OFS AAI Extension Pack. |
To install the OFS HM Application Pack, follow these steps:
Log in to the system as a non-root user.
Identify a directory for installation and set the same in the user .profile file as follows:
FIC_HOME=<OFSAA Installation Directory>
export FIC_HOME
Execute the user .profile file.
Navigate to the OFS_HM_PACK directory.
Execute the schema creator utility with –s option.
Navigate to the path OFS_HM_PACK/conf/OFS_HM_PACK.xml, and enter YES in the enable tag for OFS_AAI and OFS_AAAI.
Installation is achieved through the properties file (Silent.props) that must be updated with proper values, before attempting to install using silent mode. Edit the parameters in the Silent.props file and specify the parameters as per the requirements.
The following table lists all the properties that must be specified:
Table 2: Parameters for the Silent.props File
Property Name |
Description of Property |
Permissible values |
Comments |
LOG_MODE |
Specify Log Mode |
1 = Debug Mode 0 = General Mode [Passwords will not be printed in the log file] |
Password will be printed in the log file. The default value is 0. |
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 the model upload process. |
The default value is 1. |
MODEL_TYPE |
Specify whether you want to use the released datamodel or customized datamodel for the model upload process. |
0 = If you want to upload
the released datamodel. |
The default value is 0. |
DATAMODEL
|
Specify the path (DM_DIRECTORY)
and file (DATAMODEL) name for the customized datamodel. |
User Input |
|
SEGMENT_1_CODE |
Specify the HM Segment Code. |
User Input |
|
OBI_HOST |
Specify the Host Name of the OBIEE Server |
User Input |
This field should NOT be left blank. If OBIEE is not configured at the moment, ensure that you provide dummy value in this field |
OBI_PORT |
Specify the Port Number of the OBIEE Server |
User Input |
This field should NOT be left blank. If OBIEE is not configured at the moment, ensure that you provide dummy value in this field. |
OBI_CONTEXT |
Specify the Context Name of the OBIEE Server |
User Input |
This field should NOT be left blank. If OBIEE is not configured at the moment, ensure that you provide dummy value in this field. |
ETL_APPSRC_TYPE |
Specify if you want to create a new ETL App or Src pair or use an existing one. |
0 = If you want to create
a new ETL App or Src pair. |
If HM is being installed on an existing application value to be set as 1. And if HM is being newly installed the value to be set at 0. |
ETL_SRC_1_DESC |
ETL Staging source description. |
Describe the ETL Src. Mandatory if you want to create new ETL Src if you have specified ETL_APPSRC_TYPE= 1. |
|
ETL_SRC_2_DESC |
ETL Processing source description. |
Describe the ETL Src. Mandatory if you want to create new ETL Src if you have specified ETL_APPSRC_TYPE= 1. |
|
ETL_SRC_1_NAME |
ETL Staging source name. |
User Input |
Specify the ETL Source Name into ETL Area Definitions to be deployed. |
ETL_SRC_2_NAME |
ETL Processing source name. |
User Input |
Specify the ETL Source Name into ETL Area Definitions to be deployed. |
Enter the following command in the console to execute the application pack installer with the Silent option.
./setup.sh SILENT
The installer proceeds with Pre-Installation Checks.
Enter the OFSAA Processing Tier FTP or SFTP password value and proceed, when prompted in the command prompt.
Table 23: Console Prompt: Enter the OFSAA Processing Tier FTP/SFTP Password
Console Prompts |
User Inputs |
Please enter OFSAA Processing Tier FTP or SFTP password |
Enter the password to access the processing tier in the application server. |
The process displays the OFSAA License. Enter Y and proceed.
The installer installs the AAI application.
After the platform is installed, the OFS HM installation begins.
After Data Model Upload is complete, verify the installation logs in the log directories mentioned in the Verify the Log File Information section.
After successful HM pack installation, the WAR file is generated and all the servers are verified and the installation complete message is displayed.
The OFSAA Infrastructure installation performs a post-install health check automatically on the successful installation of the product.
On completion of the installation, verify the installation log files mentioned in the Verify the Log File Information section.
NOTE |
Perform steps mentioned in the Post-Installation section. |