2 Installer Prerequisite Setup

The Overview of this document is to share you the knowledge on how Installer is designed both in windows as well as in Linux.

Note:

Install Oracle DB Client 19C

Maintain JAVA Latest Version :: JDK 17 +

Application Server :: Weblogic Latest Version - 14.1.2.0.0

Two installer modes has to be used during setup of environment:

1. GUI Installer –

   Located under \INSTALLER\SOFT\GUI - Run ‘./FCUBSInstaller.bat file’

   GUI Installer will be required for below activities:

   • Property File Creation
   • Basic Setup
   • Environment Property file configuration
2. Silent Installer –

   Located under \INSTALLER\SOFT

   Silent Installer will be required for below activities:

   • Database Setup
   • WAR Build
3. In Linux – For creating the property file
   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.

      Figure 2-1 Application Places System

      
      

      
      Description of "Figure 2-1 Application Places System"

      
      
      Source Structure :

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

      The PM_OSDC.zip can be used without any modifications

4. Environment Setup Steps:
   Below are the sequence of steps to be followed during Environment Setup:
   1. Property File Creation: (Refer: Installer_Property_File_Creation.doc)
      Two property files will get generated

      • "fcubs.properties" required for application (WAR).
      • "env.properties" common property required for database compilation and Application WAR file generation.
   2. Populating environment property file: (Refer next section)

      The env properties file which got generated in \INSTALLER\SOFT\GUI\logs path need to be manually copied to \INSTALLER\SOFT\logs path.

      The FCUBS_PROPERTIES_PATH in env properties should be manually edited after copying (whole path with filename should be specified).

   3. Database Setup: (Refer: Installer_DB_Setup.doc)

      Database setup involves DDL Load, Object Compilation and Static Data Compilation.

   4. Basic Setup: (Refer: Installer_DB_Setup.doc)

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

   5. Application WAR build: (Refer: Installer_WAR_Building Document)

      Payments Application and Gateway WAR build can be done using the silent installer

   6. Services Installation Guide: (Refer: obpm_Servicss_Installation_Guide)
   Environment Property file configuration:

   Figure 2-2 Environment Property file configuration

   
   

   
   Description of "Figure 2-2 Environment Property file configuration"

   
   

   Config Path	Absolute path to the folder containing the config files are to be provided. This is located under \INSTALLER\SOFT\config\Application
   JDK Path	Provide Home folder path of JDK 17
   Oracle Home	Provide home folder path of Oracle Client or Database
   Source Path	Specify 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.
   EAR_NAME	Specify a name for the Application to be created.
   CONTEXT_NAME	Specify a name for the Application Context.

   BAT/SH files that be used for build and resulting artifact names that will be generated are as mentioned below:

   Component Selection	Script File	Artifact Output
   Application + Scheduler Embedded	Standalone: PMEarRun.bat..sh Co-deployed: GenericEarRun.bat/.sh	FCJNeoWeb.war (Scheduler embedded) SMWeb.war (For Standalone SMS Service) FCJPlatoReST.war
   Application without Scheduler	Standalone: PMEarRun.bat..sh Co-deployed: GenericEarRun.bat/.sh	FCJNeoWeb.war (No Scheduler) SMWeb.war (For Standalone SMS Service) FCJPlatoReST.war
   Standalone Scheduler	GenericSchedulerEarRun.bat/.sh	FCJSchedulerWeb.war
   GW-MDB	GWMDBEarRun.bat/.sh	GWMDB.war

   Recommended deployment model for OBPM: Application + Standalone Scheduler

   For Queues and Queue Connection Factory, refer to the ResourcesList.xls.