1 Build EAR files

This topic describes the process of building EAR files.

The process of building EAR files includes the following steps:

  • Load property file
  • Copy sources
  • Compile sources
  • Build sources

Follow the steps given below to build the application for setup using the Installer:

  1. Double-click FCUBSInstaller.bat batch file to start Oracle FLEXCUBE Universal Installer.
    The Oracle FLEXCUBE Universal Installer is displayed.

    Figure 1-1 Oracle FLEXCUBE Universal Installer


    Description of Figure 1-1 follows
    Description of "Figure 1-1 Oracle FLEXCUBE Universal Installer"

  2. Select Oracle FLEXCUBE Investor Servicing from the lists of Oracle FLEXCUBE options.
    The available options for installation are displayed.

    Figure 1-2 Option for Installation


    Description of Figure 1-2 follows
    Description of "Figure 1-2 Option for Installation"

  3. Click Next to choose Oracle FLEXCUBE component for installation.
  4. Choose Build Application.

    Figure 1-3 Choose Build Application


    Description of Figure 1-3 follows
    Description of "Figure 1-3 Choose Build Application"

  5. Specify Oracle FLEXCUBE components for installation.
    Refer to the table for Oracle FLEXCUBE components.

    Table 1-1 Oracle FLEXCUBE components

    Field Description
    Operating System

    Specify the operating system in which you are building the Application. Choose the appropriate one from the drop-down list.
    Application Server

    Specify the application server in which you are building the Application. Choose the appropriate one from the drop-down list.
    File Separator Style

    Specify the file separator as per the OS.
  6. Enter the source path in FC Home and specify the SMS schema details for patch installation.
    This is the schema on which the DB setup was done earlier. It should be validated and only those versions in FCHOME that are lesser /equal to than version mentioned in the DB will be chosen.

    Figure 1-4 SMS SChema Details


    Description of Figure 1-4 follows
    Description of "Figure 1-4 SMS SChema Details"

  7. Download the Web-sdk related javascript files for Oracle Digital Assistant (ODA) from the link (https://www.oracle.com/downloads/cloud/amce-downloads.html).
    The web-sdk.js file is downloaded.
  8. Place the web-sdk.js file inside FCIS OSDC folder location in the path, INFRA\FCJNeoWeb\Web-Content\script\JS.
    Refer FCIS Property File Setup and FCIS Oracle Digital Assistant Integration Guidefor the detailed information on Chatbot integration and properties.
    ODA instances are created and chat server url and channel id are readily available. Now ChatBot needs to be enabled while creating property file for FCIS Application.
  9. Click Test Connection to test the connection with the Application server.
    On successful connection, the following message is displayed.

    Figure 1-5 Information Message on Successful Connection


    Description of Figure 1-5 follows
    Description of "Figure 1-5 Information Message on Successful Connection"

  10. Click Next to specify the patch list details.
  11. On the Build Process screen, specify the following details.
    Refer to the Build Process table.

    Table 1-2 Build Process

    Field Description
    Destination Directory

    Specify the destination folder where EAR will be built.
    Application Name

    Specify the name of the application.
    Application Context Neoweb

    Specify the NeoWeb context name.
    Application Context WebTab

    Specify the WebTab context name.

    Figure 1-7 Application and Destination Details


    Description of Figure 1-7 follows
    Description of "Figure 1-7 Application and Destination Details"

  12. Specify the Property File path.
    Refer to the details of Property File table.

    Table 1-3 Property File

    Field Description
    Centralized Property File

    Specify the location of the centralized property file. You can use the Directory button to browse and select the directory.

    The property file is required for EAR building.
    Symmetric Key

    Specify the symmetric key details.
    Exclude Property File

    Check this box to exclude the property file.

    By checking this box, you can include a property file from the runtime path.

    If you check this box, you need to specify the location of the property file in the field Load from Runtime Path.

    Load from Runtime Path

    If you have checked the box Exclude Property File, you need to specify the runtime path from where the Installer will pick up the property file.

    It is mandatory to load the property file.

    Figure 1-8 Property File Details


    Description of Figure 1-8 follows
    Description of "Figure 1-8 Property File Details"

  13. Specify the runtime path in the field Load from Runtime Path, from where the Installer will pick up the property file.
    If you do not load a property file, the Installer will display the following error message.

    Figure 1-9 Load Property File Message


    Description of Figure 1-9 follows
    Description of "Figure 1-9 Load Property File Message"

  14. Click Ok and load the property file to continue.
    This is a READ ONLY screen and shows the plugins included in the installation.
    Once the property file is loaded, the Plugin screen is displayed.

    Figure 1-10 Plugin Screen


    Description of Figure 1-10 follows
    Description of "Figure 1-10 Plugin Screen"

  15. Click Next after loading the property file to continue.
  16. Select the languages you wish to include in the installation.
    The following screen is displayed.

    Figure 1-11 Language list during Installation


    Description of Figure 1-11 follows
    Description of "Figure 1-11 Language list during Installation"

  17. Select the Include Static Files in EAR to include the static files in EAR file. It can be unselected only for Weblogic Application server. If you do not check this box, the Installer will not include the static files in the EAR file. The files would be consolidated into a folder called JS_UIXML under the destination folder. For details, read the information below.

    Note:

    You have to manually copy the static files present in the JS_UIXML folder of the Destination Directory mentioned during build process to a specific folder in the Application server. This will reduce the time required for building EAR file. Copy the static files into a specific folder in the application. Later, specify the folder location in the field Runtime Path on Server.

    Figure 1-12 Include Static Files


    Description of Figure 1-12 follows
    Description of "Figure 1-12 Include Static Files"

  18. Click Next.
    The Oracle FLEXCUBE Installer copies the files to the destination folder.

    Figure 1-13 Status of Files being Copied


    Description of Figure 1-13 follows
    Description of "Figure 1-13 Status of Files being Copied"

  19. Click Copy.
    The Installer starts building the EAR/WAR files after the files are copied.
  20. Click Next and you can view the status of sources being built.

    Figure 1-14 Status of Files being Built


    Description of Figure 1-14 follows
    Description of "Figure 1-14 Status of Files being Built"

  21. Select the Application Server Clustered, if the EAR created is to be deployed in an application server running in a clustered mode.
    If the EAR created is to be deployed in the SOA enabled Application server then check box needs to be checked.
  22. The Installer creates the EAR/WAR files in the Destination Directory.
    The EAR file will be available in the selected EAR file location (Destination Directory) after the successful build process.
  23. If you have opted for BPEL, then FCBPELCIS.jar file will also be available in the EAR file location. In case of decentralized or hybrid setup, EAR files for the Host and WAR file for the Branch will be available in EAR file location.