1.4 Gateway WebServices Application

This topic describes the steps to create the property file for the Gateway WebServices Application.

  1. Start Oracle FLEXCUBE Universal Installer.
    The Oracle FLEXCUBE Universal Installer is displayed.

    Figure 1-37 Oracle FLEXCUBE Universal Installer



  2. On Oracle FLEXCUBE Universal Installer screen, enter the following details.
    Refer to the table for JDK and Oracle Home path.

    Table 1-7 JDK and Oracle Home path

    Field Description
    JDK Path

    Provide Home folder path of JDK1.8.

    Oracle Home

    Provide home folder path of Oracle Client or Database.

    Application Server Home

    Provide home folder path of Application Server.

    Application Server Location

    Select location of the application server either local or remote.

  3. Click Next to select the option for installation.
  4. Select Oracle FLEXCUBE Gateway from the lists of Oracle FLEXCUBE options.
    The available options for installation are displayed.

    Figure 1-38 Select Oracle FLEXCUBE Gateway



  5. Click Next to choose Oracle FLEXCUBE component for installation.
  6. Select Property File.

    Figure 1-39 Oracle FLEXCUBE Component for Installation



  7. Specify the type of file separator (Eg: Linux or Windows). Choose the appropriate one from the drop-down list. You also need to specify the version of the selected operating system.
  8. Specify the application server in which you are creating the property file. Choose the appropriate one from the drop-down list.
  9. Click Next and select Gateway WebServices from the Gateway Application Type.
    The following screen is displayed:

    Figure 1-40 Gateway Application Type_Gateway WebServices



  10. Click Next.
    The following screen is displayed:

    Figure 1-41 Property File Creation



  11. Specify the location of the property file in the Load Property File manually when an existing file needs to be modified.
    If you are creating a new property file, leave the field blank.

    Note:

    Ensure that the folder structures used in the following steps are created before proceeding.
  12. Click Next.
    The following screen is displayed.

    Figure 1-42 Authentication Details maintained external to FLEXCUBE



  13. Specify the following details:
    1. 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. If you check this box, the user can login using MSAD/LDAP server password only. The user Id can be one of the following:
      • MSAD/LDAP user ID
      • FCIS user ID
      If you do not check this box, then the installer skips the following screen and directly navigates to the Modifying Gateway Properties screen.

      Figure 1-43 External to FLEXCUBE



    2. External User Login Required: Check this box to enable user login using MSAD/LDAP user ID. By default, this check box is unchecked. However, you can change this.

      Note:

      • If you check this box, the user can login with MSAD/LDAP server user ID as well as FCIS user ID.
      • If you do not check this box, the user can login using FCIS user ID only.
      The field Authentication Type is enabled if one of the above check boxes is checked.
    3. Authentication Type: Select the authentication type. This is the type of external server that is used.
      You can select one of the following options:
      • MSAD (Microsoft Active Directory)
      • LDAP (Lightweight Directory Access Protocol)

      Note:

      The default option is MSAD; however, you can change it. If you check the box, then the installer navigates to the following screen on clicking Next button.
  14. Click Next.
    The following screen is displayed.
  15. Specify the following details:
    1. XSD Path: Specify the path to the XSD file. File name is not required. File separator ‘/’ must be available at the end. All the relevant XSD files must be manually copied to this location.
      For Windows: D:\GW_WS\XSD\
      For Linux: /GW_WS/XSD/
    2. Logger File: Specify the path of gw_ejb_logger.properties file with the file name. The file must be manually copied to the specified location.
      For windows: D:\GW_WS\config\gw_ws_logger.properties
      For Linux: /GW_WS/config/gw_ws_logger.properties
    3. Debug Path: Specify the path to the folder where the application creates the logs. File separator ‘/’ must be available at the end. You need to manually create the folder structure.
      For windows: D:\GW_WS\log\
      For Linux: /GW_WS/log/
    4. Security Key for Encryption: Specify the security key for the Encryption, here in this case it is Oraclefinancialsolutions.
  16. Click Next.
    The following screen is displayed:
  17. Specify the following details:
    1. DataSource: The JDBC data source is an object bound to JNDI tree and provides database connectivity through a pool of JDBC connections.
    2. POSS Datasource: Check this box if POSS is required. If you check this box, you need to specify the POSS Datasource Name in the field below.
    3. Distributed Schema: Select Distributed Schema as Yes.
    4. MSG IN LOG Required: Select if message in logging is required as Yes or No.
    5. MSG OUT LOG Required: Select if message out logging is required as Yes or No.

    Note:

    The Installer creates two files viz. gw_ejb_logger.properties and GW_EJB_Prop.propeties in the path provided to save the files.
    Click Next. The following screen is displayed:

    Figure 1-46 Webservice Properties



  18. Specify the following details:
    1. EJB JNDI Name: This is the reference name of the EJB by which it has been deployed. This should be <EJB_APPLICATION_NAME>_GW_EJB_Bean.
      Example: GWEJB_GW_EJB_Bean
      If you build the EJB application with GWEJB name, this should be the name with which the EJB EAR file is built. If you select EJB Call Type as REMOTE, this should be EJB_APPLICATION_NAME #com.ofss.fcubs.gw.ejb.GWEJBRemote.
      Weblogic: GWEJB #com.ofss.fcubs.gw.ejb.GWEJBRemote
      Websphere: ejb/GWEJB/GWEJB.jar/GWEJB#com.ofss.fcubs.gw.ejb.GWEJBRemote
      If you build the EJB application with GWEJB name, this should be the name the EJB EAR file which is built.
    2. Application Server URL: Specify the URL of the application server where the webservice application is hosted.
      Weblogic: t3://10.10.10.10:7001
      Websphere: iiop://10.10.10.10:2815
    3. User Name: Specify the user name to access the application server where the EJB application is deployed.
      Eg: infra
    4. Password: Specify the password for the above user name.
    5. ELB Look Type: Select from the drop box, REMOTE/LOCAL.

      Note:

      When REMOTE is selected, it is mandatory that a ejb ear has to be built, a web service ear has to be built and both to be deployed.

      When LOCAL is selected, new option in EAR build is provided where gateway ejb and web services are packaged in the same project. That single is deployed will suffice the web services.

      Note:

      The Installer creates two files viz. gw_WS_logger.properties and GW_WS_Prop.properties in the path provided to save the files.
  19. Click Next.
    The following screen is displayed:

    Figure 1-47 Property Installation



  20. You can save the property file created in a temporary folder and continue with the installation process.
    1. Click Property File to view the created property file.
    2. Click Save to save the created property file in the desired location.
    3. Click Continue to continue the installation process with gateway application type.
    4. Click Next to navigate to the installer home screen.
This completes the property file creation for Gateway.