To build the application for setup using the installer, follow the steps given below.

1. Double-click ‘FCUBSInstaller.bat’ batch file to launch Oracle Banking Trade Finance Installer. The following screen is displayed. Select Utilities option, configuration mode as “Application Root” and click ‘Next’ button.
   
   
   Description of the illustration 1.3_prerequisites.png
   
   
2. Select ‘Approot object Conversion” in Utility Screen and click Next as shown below:
   
   
   Description of the illustration 1.3_s2_approot-object-conversion.png
   
   
3. In the Approot object conversion screen, enter application name and Approot Schema details.

   Options of conversion include:

   • Shared Application
   • Shared Application and User Authentication
   • Shared Application and Shared Data – Default
   • Shared Application and Shared Data – Custom

Shared Application

1. When ‘Shared Application’ is selected, there will not be any common data and only application is shared.
2. After selecting the radio button, user will have to input the Application name and the Application root schema details where the conversion has to be applied and click on ‘Test Connection’.
3. When Application name is not inputted, error will be displayed to input the same. User has to make sure that application name is the one mentioned in pre-requisites with installation done for version 1.0.
4. Once the Connection is successful, ‘Finish’ button will be enabled and the object conversion will be completed at this step.
5. Execution will take few minutes and post completion, a dialog box displays ‘Compilation Success’ message in the front end.

   Application_Installation.sql

   
   
   
   Description of the illustration 1.3_s3_shared-application.png
   
   

   Application_PDB_Creation.sql

Shared Application and User Authentication

1. When ‘Shared Application and User authentication’ is selected, only user authentication related data will be shared along with a shared application,
2. After selecting the radio button, user will have to input the Application name and Application root schema details where the conversion has to be applied and click on ‘Test Connection’.
3. When Application name is not inputted, error will be displayed to input the same. User has to make sure that application name is the one mentioned in pre-requisites with installation done for version 1.0.
4. Once the Connection is successful, ‘Finish’ button will be enabled and the object conversion will be completed at this step.
5. Execution will take few minutes and post completion, a dialog box displays ‘Compilation Success’ message in the front end.
   
   
   Description of the illustration 1.3_s3_shared_user-authentication.png
   
   

   Application_Template_PDB_Creation.sql

Shared Application & Shared Data - Default

1. When Shared Application & Shared Data - Default is selected, all the function groups listed will be installed in the application root.
2. After selecting the Radio button, user will have to input the Application name and Application root schema details where the conversion has to applied and click on ‘Test Connection’.
3. When Application name is not inputted, error will be displayed to input the same. User has to make sure that application name is the one mentioned in pre-requisites with installation done for version 1.0.
4. Once the Connection is successful, ‘Finish’ button will be enabled and the object conversion will be completed at this step.
5. Execution will take few minutes and post completion, a dialog box displays ‘Compilation Success’ message in the front end.
   
   
   Description of the illustration 1.3_s3_shared-application-default.png
   
   

Shared Application & Shared Data - Custom

1. When Shared Application & Shared Data – Custom is selected, all the function groups listed will be installed in the application root.
2. After selecting the Radio button, user will have to input the Application name and Application root schema details where the conversion has to applied and click on ‘Test Connection’.
3. When Application name is not inputted, error will be displayed to input the same. User has to make sure that application name is the one mentioned in pre-requisites with installation done for version 1.0.
4. Once the Connection is successful, ‘Next’ button will be enabled to take through the steps of movement of function ids to pdbs.
5. After selecting the Radio button, user will have to input the Application name and Application root schema details where the conversion has to applied and click on ‘Test Connection’.
6. Once the Connection is successful, ‘Finish’ button will be enabled to continue with the next steps of object conversion.

   Approot_AppSeed_sync.sql

   
   
   
   Description of the illustration 1.3_s3_shared-application-custom.png
   
   

   Approot_PDB_Sync.sql

7. In the Next Screen, user can opt-out the entities which are not required to be the candidates of approot and those function ids will be moved to PDB.
8. There will be two multiblocks available.
   1. First multiblock will list the details of function groups which are the Approot candidates.
   2. Second multiblock will list the function ids corresponding to each of the function group in the first block.
9. Second multiblock will have the check box ‘Move to PDB’ against each function ID.
   
   
   Description of the illustration 1.3_s9_move-pdb.png
   
   
10. User can select more than one function group and the respective function ids will also be appended to the second multiblock against the function group on click of ‘View Details’ button.
11. Once the selection is completed, ‘Next’ button has to clicked to move to the next screen where the complete list of function ids.
12. The dependent function ids of the selected functions opted to move to PDB will be listed in the below section.

    fn_error_handler.sql

    
    
    
    Description of the illustration 1.3_s12_pdb.png
    
    
13. Object conversion can be completed by clicking on the Finish button.
14. Execution will take few minutes and post completion, a dialog box displays ‘Compilation Success’ message in the front end.