4.1 Installer and Installation Prerequisites
This section describes the Installer and Installation prerequisites.
The following table provides the list of prerequisites required before beginning the installation for OFS BD application. If requirements are not met, the Environment Check utility will notify you.
Table 4-1 Pre-requisite Information
| Category | Sub_Category | Expected Value |
|---|---|---|
| Environment Settings | User Permission | User to have 755 permission on the directory identified for
installation (FIC_HOME).
Note: User to have 755 permission on the .profile file. Provide BDF_HOME in .profile pointing to Installation Directory (FIC_HOME) |
| - | Java Settings |
JAVA_TOOL_OPTIONS="
Djdk.util.zip.disableZip64ExtraFieldValidation=true" export
JAVA_TOOL_OPTIONS
Note: Ensure that the absolute path to JRE/bin is set at the beginning of PATH variable. For example,
Ensure that no SYMBOLIC links to JAVA installation are not set in the PATH variable. |
| - | Enable unlimited cryptographic policy for Java | For more information, see the section Enabling Unlimited Cryptographic Policy in OFS Analytical Applications Infrastructure Administration Guide. |
| - | Oracle Database Settings |
Oracle Database Server TNS_ADMIN must be set in.profile file pointing to appropriate tnsnames.ora file. Enable Transparent Data Encryption (TDE) and/ or Data Redaction** Note: For more information, see unresolvable-reference.html#GUID-CC7B6A33-46F1-4FDF-9E44-758A1C00DAEE. OFSAA Processing Server Set ORACLE_HOME in.profile file pointing to appropriate Oracle DB Client installation. PATH in .profile file must be set to include appropriate $ORACLE_HOME/bin path. Entry (with SID/ SERVICE NAME) must be added in the tnsnames.ora file on the OFSAA server. |
| OS/File System Settings | OS Level Settings | You must set your locale to UTF-8 locale (LANG, NLS_ LANG to be set
in.profile). Specifying a locale depends on your data and the operating
system installed on your system.
For example, For Linux OS: export LANG=en_US.utf8 You can determine the locale on your system using the locale -a command export, NLS_LANG=AMERICAN_ AMERICA.AL32UTF8 |
| - | File Descriptor Settings | Greater than 15000 |
| - | Total Number of Process Settings | Greater than 4096 |
| - | tmp space | Prior to installation, ensure that sufficient free temp space (minimum 1 GB free) is available in /tmp directory of unix server hosting OFSBD. |
| - | Port Settings | Default port numbers to be enabled on the system are 6500, 6501, 6505, 6507, 6509, 6510, 6666, 9999, and 10101. |
| - | Staging Area/Metadata Repository | A directory to hold the application metadata artifacts and
additionally act as staging area. The directory must exist on the same
system as the OFSAA Infrastructure (can be configured on different
mount). However, the owner of the installation directory mentioned above
must have RWX (read, write, and execute) permissions on this
folder.
Set 775 permission on this folder. Note: This directory is also referred as FTPSHARE folder. |
| - | Installation Directory | A directory where the product files will be installed. Assign User permission to 755 on the installation directory. |
| - | Temporary Directory | Default temporary directory where installation files are stored for a
short period of time to support faster installation.
Note: If NOEXEC is enabled, the extraction of files by the installer into the /tmp directory is prevented and the binaries will not execute in the directory, which will fail the installation. |
| - | Download Directory | A directory where the product installer file will be downloaded/copied. Ensure user permission is set to 755 on the Download directory. |
| - | OS Locale |
To check the locale installed, execute the following command: |
| - | Database Instance Settings |
For an Oracle Database installation, set your Oracle NLS_LANG environment variable to an appropriate UTF-8 character set. For example, setenv NLS_LANG AMERICAN_ AMERICA.AL32UTF8 Note: For more information on other database tunable parameters required for OFS BD, see Tunable Database Parameters Ensure that the OLAP_USER role is available in the database. |
| Web Application Server | WebSphere/ WebLogic/ Tomcat | Web application server must be installed and profile/domain created.
You are prompted to enter the WebSphere Profile path, WebLogic Domain
path, or Tomcat Deployment path during OFSAAI
installation.
Note: For more information about WebSphere Profile and WebLogic Domain creation, see Configure the Web Server. |
| Web Server | Apache HTTP Server/Oracle HTTP Server/IBM HTTP Server | This is an optional requirement. HTTP Server Installation to be
available. You are prompted to enter the Web server IP/Hostname and Port
details during installation.
Note: For more information on Web server installation, see Configure the Web Server. |
| Operating System | Solaris 11 | Upgrade to Oracle Solaris 11.3 with SRU09 or higher. See Updating to Oracle® Solaris
11.3 to upgrade to SRU09 if you have a lower SRU version.
Additionally, install the required runtime libraries.
For more information, see Installing Only the Runtime Libraries on Oracle Solaris 11. |
| Backup Tables | Table Names | Before starting the installation and post installation, ensure there
are no Backup tables created manually with table names suffixed with
_BKP or _TEMP.
Note: Table names with _BKP and _TEMP that are created outside the application will cause installation/patch application to fail. |
Note:
You cannot install the OFS FSDF application on an existing OFS BD installation, within the same infodom/schema.