1. GUI Installer
   • Located under \INSTALLER\GUI
   • GUI Installer is required for below activities:
     • Property File Creation
     • Basic Setup
     • Environment Property file configuration
2. Silent Installer
   • Located under \INSTALLER\GUI
   • Silent Installer will be required for below activities:
     • Database Setup
     • EAR Building

1. Following steps to set the variables:
   • export JAVA_HOME=JAVA_HOME path
   • export PATH=JAVA_HOME/bin:$PATH
   • export ORACLE_HOME=ORACLE_HOME path
   • export PATH=ORACLE_HOME/bin:$PATH
2. Now traverse to the path where FCUBSInstaller.sh file is present in the server.
3. Give access rights to the file and Run “./FCUBSInstaller.sh” file.
4. Provide the necessary home path to set and launches the Installer.
5. Run the “./FCUBSInstaller.sh” file in any graphical desktop sharing system like TigerVNC.

Description of the illustration fcubsinstaller.png

The Installation can be done in different ways and Source Structure should be maintained as below:

Below are the sequence of steps to be followed during Environment Setup:

1. Property File Creation: (Refer: OBTF_Installer_Property_File_Creation.pdf)
   • Two property files are generated
     • "fcubs.properties", i.e. required for application EAR building.
     • "env.properties", i.e. common property required for environment setup.
2. Maintaining environment property file: (Refer next section)

   Modification of the generated “env.properties”, if required, is to be done in this step.

3. Database Setup: (Refer: OBTF_DB_Setup.pdf)

   Database setup involves DDL Load, Object Compilation and Static Data Compilation. This is done using the silent installer.

4. Basic Setup: (Refer: OBTF_DB_Setup.pdf)

   Post INC Load, basic setup has to be done. Basic Setup is done using GUI Installer.

5. Application EAR build: (Refer: OBTF_EAR_Building.pdf)

   OBTF Application and Gateway EAR building can be done using the silent installer.

Figure 1-1 Environment Property File Configuration

Description of "Figure 1-1 Environment Property File Configuration"

CONFIGPATH:

Absolute path to the folder containing the configuration files, is to be provided. Configuration files are located under \INSTALLER\SOFT\config\Application

JAVA_HOME

Absolute path to the home folder of JDK 1.8 is to be provided.

APPSERVER_HOME

Absolute path to the home folder of Application Server.

ORACLE_HOME

Absolute path to the home folder of Oracle Database Client is to be provided.

SOURCE_PATH and EAR_DESTINATION_PATH

Specify the destination directory. Here destination path should be same as the source file path

FCUBS_PROPERTIES_PATH

Absolute path where the fcubs.properties file, is to be provided.

GW_PROPERTIES_PATH

Absolute path to the Gateway Properties file is to be provided.

APPLICATION_TYPE

Application Type is maintained as per the Application Name selected in the GUI Installer.

EAR_NAME

Specify a name for the Application to be created.

CONTEXT_NAME

Specify a name for the Application Context

EXTERNAL_JSUIXML_REQUIRED

This field explains whether JS and UIXML folders are external or integrated within ear file.

It Holds values as ‘Y’ or ‘N’. EXTERNAL_JSUIXML_REQUIRED=Y indicates that JS and UIXMLs are not within the ear file generated.

EXTERNAL_JSUIXML_PATH

This path is mandatory if EXTERNAL_JSUIXML_REQUIRED=Y. JS and UIXMLs generated during ear file creation should be placed in the path given.

WEBLOGIC_HOME

Absolute path to the home folder of weblogic.

PATCHSET_INSTALLATION

Parameter value will be ‘N’ for console and ‘Y’ for patchset installation.

EXTERNAL_PROPERTY_PATH_REQUIRED:

This field explains whether property file is external or integrated within ear file.

EXTERNAL_PROPERTY_PATH

This path is mandatory if EXTERNAL_PROPERTY_PATH_REQUIRED =Y.

SYMMETRIC_KEY

This key is used for encryption logic.

The below parameters stores SMS Schema details:

HOST_SMS: Host name of SMS Schema will be stored in encrypted format.

SCHEMA_NAME_SMS: Schema name will be encrypted and stored

PASSWORD_SMS: Encrypted form of password will be saved against this parameter.

SERVICE_NAME_SMS: Encrypted form of Service name.

PORT_SMS: Contains Port number of SMS Schema.

CONNECTING_STRING_SMS: Encrypted connected String of SMS Schema.

ENTITY_NOS: It stores the number of Entity Schemas required.

The below parameters stores Entity Schema details. This information will be captured for all the entities with respective entity name as suffix.

HOST_ENTITY_ID1: Host name of Entity Schema will be stored in encrypted format.

SCHEMA_NAME_ENTITY_ID1: Entity Schema name will be encrypted and stored.

PASSWORD_ENTITY_ID1: Encrypted form of password will be saved against this parameter.

SERVICE_NAME_ENTITY_ID1: Encrypted form of Service name.

PORT_ENTITY_ID1: Contains Port number of first Entity Schema.

CONNECTING_STRING_ENTITY_ID1: Encrypted connected String of Entity Schema

COMPILE_IN_ALL_ENTITIES:

This parameter holds value as ‘Y’ or ‘N’. If ‘N’ then necessary objects will be compiled in all the entities mentioned.

Note:

Paths have to be maintained with ‘/’ separator as it is maintained only for WINDOWS. ‘\’ slash is considered as an escape character so ‘/’ slash is given in windows.

In the process of property file creation, when Save is clicked at the end, Property file is saved in \INSTALLER\GUI\LOGS.

On launch of GUI Installer for creating the property file , the env properties file gets generated which is present in \INSTALLER\SOURCE\logs path need to be manually 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 PAYMENTS needs to install as Co-deployed along with OBTF then PAYMENTS folder from PAYMENTS OSDC zip should be placed parallel to OBTF folder in the OBTF OSDC zip.

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

Following are the examples to execute for EAR Run, Gateway EAR Run and DB Compile for both Windows and Linux.

For Queues and Queue Connection Factory, please refer to the Resources to be created document.