You need to setup the database-related configuration for the installation of the Oracle Banking Branch. It is recommended to create a different schema for each application.

1. On the Homepage, specify CSDNGUIM in the text box, and click the next arrow.

   Note:

   Ensure that the user has roles for the screen.
   The Next Gen UI Products Maintenance screen is displayed.

   Figure 15-1 Next Gen UI Products Maintenance

   
   

   
   Description of "Figure 15-1 Next Gen UI Products Maintenance"

   
   
2. On the Next Gen UI Products Maintenance screen, and update the Oracle Banking Microservices Architecture Product URL.

   Note:

   For more information on the screen, refer to the FLEXCUBE Universal Banking Documentation Library.
   A new Function ID NGTELLER is released as static data.
3. Make sure that the user roles are maintained for the new Function ID.
4. Once the roles are maintained, click Next Gen UI on the toolbar.
   The Next Gen UI Dashboard will be displayed with the list of products.
5. Click Retail product.

   Note:

   Ensure the same user id is maintained for the retail product and it has necessary roles.
   The Plato Teller Dashboard is displayed.
6. Configure Oracle Banking Microservices Architecture as follows:
   1. Update the SECURITY_CONFIG table in the PLATO_SECURITY schema. For information on the entries, refer to the table below:

      Note:

      In addition, SSL should be enabled in the Oracle Banking Branch application.

      Table 15-1 Configurations for Oracle Banking Microservices Architecture

      Key	Value
      INTEGRATION_ENABLED	true
      INTEGRATION_CALLBACK_URL	https://FCUBShostname:FCUBSport/FCJNeoWeb/ValidationService/FCNonceValidation/validate
      IS_SSO_CONFIGURED	true
      AUTO_TOKEN_REGENERATE_MODE	true

   2. Update the hostname and port number of FLEXCUBE Universal Banking in the integration callback URL.