1.2 Standalone Setup

During the war, FCJNeoWeb is the primary application, and it generates files. The UI automatically populates the War Name while creating property files.
Maintain the following Application Type accordingly for building respective EARs:

Table 1-1 Standalone

Product Type Application Type EAR Name BAT/sh file to be run Property file to be used Folder Location in Destination Path
OFCL OBCL Any Distinct Name CLEarRun.bat or CLEarRun.sh fcubs.properties WAR file in build folder
GW-Integrated INTEGRATED Any Distinct Name CLGatewayEarRun.bat or CLGatewayEarRun.sh GW_WS_Prop.properties WAR file in gatewayBuild folder OFCLWeb
GW-Individual INDIVIDUAL Not Required CLGatewayEarRun.bat or CLGatewayEarRun.sh GW_WS_Prop.properties WAR file in gatewayBuild folder OFCLWeb
GW-REST INDIVIDUAL Any Distinct Name CLGatewayRestEarRun.bat or CLGatewayRestEarRun.sh GW_REST_Prop.properties and GW_RESTEJB_Prop.properties Individual: WAR file in gatewayBuild folder

Integrated: EAR file in Destination folder

GW-MDB GATEWAY Any Distinct Name GWMDBEarRun.bat GWMDBEarRun.sh GW_MDB_Prop.properties WAR file in GWMDBuild folder
GW-HTTP GATEWAY Any Distinct Name GWHTTPEarRun.bat GWHTTPEarRun.sh GW_HTTP_Prop.properties WAR file in GWHTTPBuild folder
Scheduler SCHDLR Any Distinct Name SchedulerEarRun.bat or SchedulerEarRun.sh Scheduler.properties WAR file in buildScheduler folder
ODT ODT Any Distinct Name ODTWarRun.bat or ODTWarRun.sh ODT.properties -
This table shows the BAT/sh scripts that need to be run individually for each EAR creation. The env.properties will have the appropriate application type set.
  1. To set up the OBCL WAR build, you need to execute the CLEarRun.bat file found in the \INSTALLER\SOFT directory on Windows, or the CLEarRun.sh file on Linux.
    The mentioned source path will generate a WAR file with the following folder structure.

    Figure 1-3 War Build - Folder Structure


    Description of Figure 1-3 follows
    Description of "Figure 1-3 War Build - Folder Structure"

    Note:

    As per the latest Installer changes, all the .jar files will be copied to the FCJNeoWeb.war\WEB-INF\lib folder.

    Figure 1-4 FCJNeoWeb library folder


    Description of Figure 1-4 follows
    Description of "Figure 1-4 FCJNeoWeb library folder "

    When EXT_JSUIXML is chosen, it will create the JS_UIXML folder in parallel to the build folder. You should manually copy this folder to the Deployment Path specified in env.properties.

  2. To run Gateway WAR, execute CLGatewayEarRun.bat (CLGatewayEarRun.sh)
  3. To run EJB, MDB and HTTP gateways, execute the respective bat files that is GWEJBEarRun.bat (GWEJBEarRun.sh), GWMDBEarRun.bat (GWMDBEarRun.sh) and GWHTTPEarRun.bat (GWHTTPEarRun.sh).
  4. To run ODT, execute ODTWarRun.bat in Windows (ODTWarRun.sh in Linux) after building odt.properties.
  5. To run STAND ALONE SCHEDULER, execute SchedulerEarRun.bat in Windows or SchedulerEarRun.sh in Linux. After this deploy the EAR in the application console.
    The mentioned source path will generate a WAR file with the following folder structure.

    Figure 1-5 Build Scheduler - Folder Structure


    Description of Figure 1-5 follows
    Description of "Figure 1-5 Build Scheduler - Folder Structure"

    Note:

    As per Installer changes, Scheduler war will be generated with FCJSchedulerWeb.war name, and all the .jars files are copied to the FCJSchedulerWeb.war\WEB-INF\lib folder,

    Figure 1-6 FCJSchedulerWeb library folder


    Description of Figure 1-6 follows
    Description of "Figure 1-6 FCJSchedulerWeb library folder"

    Note:

    ExtAdapter.(JAR or WAR) is generated for ROFC in case of ELCM_INSTALLED, S(Standalone) and C(Co-deployed) OBCLExtAdapter is embedded with FCJNeoWeb.war, (JAR or WAR) is generated for OBCL in case of ELCM_INSTALLED S(Standalone) and C(Codeployed) both OBCLExtAdapter. (JAR or WAR) and ExtAdapter.(JAR or WAR) is generated for OBCL and ROFC CoDeployed in case of ELCM_INSTALLED S(Standalone) and C(Co-deployed). In case of Oracle Banking Corporate Lending, OBCLCalcEngine WAR file is generated along with EAR. This WAR file is required to be deployed as standalone component for RFR (Risk Free Rates) calculations.

    Note:

    Ensure the necessary resources are created in the application server as mentioned in the Resources To Be Created document.

Parent topic: Building Application for Setup