2.2 Environment Property File Configuration

This topic explains the Environment Property File Configuration.

Figure 2-3 Environment Property File

Description of "Figure 2-3 Environment Property File"

Note:

A single property file will be used for both DB Compilation and EAR build. Hence all the properties will be located in a single property file. Some properties may not be applicable during a certain setup, and those should not be modified (should be left with default values).

Refer the table, to view the properties available in the Environment Property File.

Table 2-2 Environment Property File

Properties	Description
Config Path	Absolute path to the folder containing the config files are to be provided. This is located under \INSTALLER\SOFT\config\Application
Java_Home	Provide the home folder path of JDK 1.8.
Oracle_Home	Provide the home folder path of Oracle Client or Database.
Varedited	This property should not be changed. This is an internal property required by the installer to identify if any changes are required in env.properties.
Source and Destination Path	Specify the destination directory. Here the destination path should be the same as the source file path.
FCUBS_PROPERTIES_PATH	Path where the fcubs property file is located .
GW_PROPERTIES_PATH	Provide the Gateways Properties Path.
APPLICATION_TYPE	Application Type is maintained as per the Application Name selected in the GUI Installer.
EXTERNAL PROPERTY PATH	If this is selected during installation, the corresponding path will be displayed here, and the value of the parameter EXTERNAL PROPERTY FILE REQUIRED will be ‘Y.’
EXTERNAL JSUIXML PATH	If this is selected during installation, the corresponding path will be displayed here, and the value of the parameter EXTERNAL JSUIXML REQUIRED will be ‘Y’.
EAR_NAME	Specify a name for the Application to be created.
EAR DESTINATION PATH	This is the local path where the built EAR will be saved. This gets updated automatically as per the path provided during the installation process.
CONTEXT_NAME	Specify a name for the Application Context.
FCHome	Provide the FCHome Path. This will be the source path for DB setup/EAR build.
USER_NAME	Give the Schema Name.
PASSWORD	Here Password should be encrypted. As Schema details provided by the GUI Installer, the env.properties file generates with the encrypted Password.
Schema	Give the Instance Name. Note: The path is maintained with ‘\\’ as it is maintained only for WINDOWS. ‘\’ slash will consider as an escape character, so ‘\\’ slash is given in windows.

On the launch of GUI Installer for creating the property file, the env properties file gets generated, which is present in \INSTALLER\SOFT\GUI\logs path will be copied to \INSTALLER\SOFT\logs path. This method is followed for EAR creation, and Back-end build as it is done by the Silent Installer.

If OBCL needs to install as Co-deployed along with ROFC, then the OBCL folder from OBCL_OSDC.zip should be placed parallel to the ROFC folder in the ROFC_OSDC.zip.

If ELCM needs to install as Co-deployed along with ROFC, then the ELCM folder from ELCM_OSDC.zip should be placed parallel to the ROFC folder in the ROFC_OSDC.zip. INFRA inside ELCM should be moved and merged with CORE INFRA.

If PAYMENTS needs to install as Co-deployed along with ROFC, then the PAYMENTS folder from the PAYMENTS OSDC zip should be placed parallel to the ROFC folder in the ROFC_OSDC.zip.

INFRA inside PAYMENTS should be moved and merged with CORE INFRA.