1.2.1 Backend Setup using Silent Installer

Backend Setup has to be done using Silent Installer. DDL Compilation, Object Compilation, and Static Data Load will be taken care of as part of Backend Setup.

Before loading objects into the schema, fcubs.properties file creation must be performed with the required database details using the GUI installer (Refer to Treasury Management Installer Property File Creation document). After the property file is created, the env.properties file present in INSTALLER/SOFT/GUI/logs/ directory is automatically updated with the details provided while creating the property file.

The env.properties file present in INSTALLER/SOFT/GUI/logs/ will be automatically copied to INSTALLER/SOFT/logs/ directory as part of property file creation. Details from this env.properties are taken for further steps.

Run the <Product Processor> DBCompileRun.bat from the INSTALLER/SOFT directory. DDL Compilation, Object Compilation, and Static Data load will be done.

For Example: OBTR INSTALLATION

First load SMS objects first and then OBTR objects. i.e.

1. Run SMSDBCompileRun.bat in windows (SMSDBCompileRun.sh in Linux).

   Note:

   Before running DB Compilation of any sort, please make sure that System Date Time format and language are provided as English, or otherwise DB Compilation might fail due to improper log names.
2. After SMS object loading is completed, then initiate OBTR compilation Run TRDBCompileRun.bat in windows (TRDBCompileRun.sh in Linux).

Check for the Invalid Count and make sure that the Invalid count is ‘0’. Run Invalid Recompilation script (fast.sql), if required.

This is for KERNEL as well as cluster objects in the DB schema.

• Invalid Recompilation script