Gateway MDB Application

  1. Start Oracle Universal Banking Solution Installer.
  2. Select Gateway MDB application type, and click Next.

    Figure 2-13 Provide Environment Details



  3. Enter the Required details in the Screen. Specify the EAR name, valid Application Server Path, Source, and EAR destination path and click Next button.

    Figure 2-14 Gateway Property File Creation



  4. On the Gateway Property File Creation screen, select Gateway MDB to create configuration files for the application.
  5. Click Next, the installer displays the Multi Entity screen.
  6. On the Multi Entity Names screen, specify the fields.

    Table 2-6 Multi Entity Names - Field Description

    Field Description
    MultiEntity Required Select the MultiEntity Required check box for enabling the multi-entity deployment. This will enable + and - for capturing the entity name.
    + Click + to add a new row for capturing the new entity name.
    - Select the entity name and click -, the deletion of the existing entity name will be done.
    Entity Name Enter the entity name as a single word. For example, ENTITY1
  7. On the Multi Entity Names screen, click Next.

    Figure 2-16 Property File Creation



  8. On the Property File Creation screen, specify the fields.

    Table 2-7 Property File Creation - Field Description

    Field Description
    SSO Required Check this box to enable single sign-on (SSO). If you check this box, specify the SSO Key.
    SSO Key Specify the SSO key. If you have checked the box SSO Required, it is mandatory to specify the SSO key. If you have checked the box SSO Required, then the Installer will skip the following two screens and will directly navigate to the Modifying the Gateway properties screen.
    External Password Required Check this box to allow user login using MSAD/LDAP password irrespective of the user ID. By default, this check box is unchecked. However, you can change this.

    Note:

    If you check this box, the user ID can be either MSAD/LDAP user ID or the Payments user ID, and the password can be MSAD/LDAP server password only.
    If you do not check this box, then the installer skips the following screen and directly navigates to the Modifying Gateway Properties screen.

    Figure 2-17 Property File Creation


    Screen

    External User Login Required Check this box to enable user login using MSAD/LDAP user ID.

    Note:

    If you check this box, the user can log in with MSAD/LDAP server user ID as well as using Payments user ID. If you do not check this box, the user can login using Payments user ID only.
    By default, this check box is unchecked. However, you can change this.

    Figure 2-18 Property File Creation


    Screen

    Note:

    The field ‘Authentication Type’ is enabled if one of the above check boxes is checked:
    Authentication Type Select the authentication type from the drop-down list. This is the type of external server that is used. Select one of the following options -
    • MSAD (Microsoft Active Directory)
    • LDAP (Lightweight Directory Access Protocol)
    The default option is MSAD. However, it can be changed.
  9. On the Property File Creation screen,click Next.

    Figure 2-19 Property File Creation



  10. Specify the following LDAP server details.

    Table 2-8 LDAP server details.

    Field Description
    LDAP Server URL Specify the URL to access the LDAP server where the external user ID and password are maintained.
    LDAP SSL Enabled Check this box if the LDAP server is SSL enabled. If you check this box, then specify the SSL port also in the field LDAP SERVER URL. By default, this check box is unchecked. However, you can change this.
    Security Authentication Type Depending on the authentication mechanism supported by the LDAP server, select one of the following -
    • Simple
    • Strong

    Note:

    • Different servers support different authentication mechanisms.
    • By default, the security authentication type is Simple, however, you can change this.
    Domain Name Specify the domain name.
    LDAP Server Timeout Specify the LDAP server timeout in milliseconds. This must be a positive integer value. For example, specify 1000, 10000 or 5000. If it is zero or less, it indicates that no read timeout is specified. Then the wait for the response infinite until it is received. By default, the LDAP server timeout is zero, however, you can change this.
  11. Click Next.

    Figure 2-20 Property File Creation



  12. On the Property File Creation screen, specify the details.

    Table 2-9 Property File Creation - Field Description

    Field Description
    XSD Path Specify the path to the XSD file. The file name is not required. File separator must be /. There must be a / at the end. All the relevant XSD files must be manually copied to this location.
    For example,
    • For Windows - D:\Kernel11.1\GW_MDB\XSD\
    • For Linux - /Kernel11.1/GW_MDB/XSD/
    Logger File Specify the path to the gw_ejb_logger.properties file with the file name. The file must be manually copied to the specified location.
    For example,
    • For Windows - D:\Kernel11.1\GW_MDB\config\gw_mdb_logger.properties
    • For Linux - /Kernel11.1/GW_MDB/config/gw_mdb_logger.properties
    Debug Path Specify the path to the folder where the application creates the logs. There must be a / at the end. You need to manually create the folder structure.
    For example,
    • For Windows - D:\Kernel11.1\GW_MDB\log\
    • For Linux - /Kernel11.1/GW_MDB/log/
  13. Click Next.

    Note:

    The Installer creates two files viz. gw_ejb_logger.properties and GW_EJB_Prop.properties in the path provided to save the files.

    Figure 2-21 Property File Creation



    Table 2-10 Property File Creation - Field Description

    Field Description
    DataSource The JDBC data source is an object bound to the JNDI tree and provides database connectivity through a pool of JDBC connections.
    POSS Datasource Check this box if POSS is required. If you check this box, specify the POSS Datasource name in the field below this.
    OPSS CSF Available Indicates whether OPSS-CSF is installed or not.

    Note: Select this only if Oracle Platform Security Services - Credential Store Framework (CSF) is installed as per the guidelines in the pre-requisite document. It is recommended that you install CSF for safeguarding application-specific security credentials.

    Distributed Schema If the schema is distributed, select Yes. If the schema is not distributed, select No.

    Note: The Installer creates two files viz. gw_ejb_logger.properties and GW_EJB_Prop.propertie in the path provided to save the files.

    Security Key for Encryption Specify the security key for the encryption. Here, in this case, it is Oraclefinancialsolutions.
  14. Click Next.

    Figure 2-22 Gateway Property File Creation



  15. On the Gateway Property File Creation screen, specify the details.

    Table 2-11 Gateway Property File Creation - Field Description

    Field Description
    Connection Factory Specify the connection configuration parameters to create connections for JMS clients.

    For example, MDBQCF

    Request Queue Specify the request queue. This is the point-to-point destination type used for asynchronous peer communication.

    For example, MDB_QUEUE

    Response Queue Specify the response queue name.

    For example, MDB_QUEUE_RESPONSE

    DL Queue Specify the dead letter queue name.

    For example, MDB_QUEUE_DLQ

    Secure Queue Check this box if the Caller ID and Caller Password values have to be entered.

    The Installer creates two files viz. gw_mdb_logger.properties and GW_MDB_Prop.properties in the path provided to save the files.

  16. Click Next.

    Figure 2-23 Property Installation



    The property file will be created in a temporary folder.
  17. Click Property File to view the created property file.
  18. Click Save to save the created property file in the desired location.
  19. Click Continue to continue the installation process with gateway application type.
  20. Click Next to navigate to the installer home screen.