1 Building Application for Setup
The process of building EAR files includes the following steps:
- Obtain the fcubs.properties (Refer Property File Creation) file generated by the GUI Installer which is saved in the required path.
- fcubs.properties file will be used for building the ear. This will be created as part of the initial property file creation
- env.properties file parameters gets updated during every property file creation (like FCUBS, Gateway, Scheduler etc). After Property file creation, proceed with respective EAR build and then proceed with other components property file creations and build.
- Run the respective EAR bat (Windows) or respective EAR.sh (Linux) file.
- The command window closes after the EAR is generated
- The EAR will be generated in the EAR destination path provided during property file creation
- JS and UIXML will also be generated in the EAR destination path if external JS/UIXML is selected during property file creation.
- The external path for JS/UIXML and EAR destination path can be referred in env.properties file
- Manually copy the JS/UIXML generated in the EAR destination path, to external JS/UIXML path
Maintain the following Application Type accordingly for building
respective EARs:
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.
Table 1-1 Standalone
| Product Type | Application Type | EAR Name | BAT/sh file to be run | Property file to be used |
|---|---|---|---|---|
| ROFC | FCUBS | Any Distinct Name | ROFCEarRun.bat or ROFCEarRun.sh | fcubs.properties |
| GW-Integrated | INTEGRATED | Any Distinct Name | ROFCGatewayEarRun.b at or ROFCGatewayEarRun.s h | GW_WS_Prop.properties |
| GW-Individual | INDIVIDUAL | Not Required | ROFCGatewayEarRun.b at or ROFCGatewayEarRun.s h | GW_WS_Prop.properties |
| GW-REST | INDIVIDUAL | Any Distinct Name | ROFCGatewayRestEar Run.bat or ROFCGatewayRestEar Run.sh | GW_REST_Prop.properties and GW_RESTEJB_Prop.properties |
| GW-MDB | GATEWAY | Any Distinct Name | GWMDBEarRun.bat GWMDBEarRun.sh | GW_MDB_Prop.properties |
| GW-HTTP | GATEWAY | Any Distinct Name | GWHTTPEarRun.bat GWHTTPEarRun.sh | GW_HTTP_Prop.properties |
| GW- EJB | GATEWAY | Any Distinct Name | GWEJBEarRun.bat or GWEJBEarRun | GW_ EJB_Prop.properties |
| Scheduler | SCHDLR | Any Distinct Name | SchedulerEarRun.bat or SchedulerEarRun.sh | Scheduler.properties |
| ODT | ODT | Any Distinct Name | ODTWarRun.bat or ODTWarRun.sh | ODT.properties |
- Goto \INSTALLER\SOFT path and execute the EarRun bat file for EAR build. For Example : EarRun.bat :- ROFCEarRun.bat (ROFCEarRun.sh for running in Linux machine) for ROFC and so on. EAR file will be generated in the mentioned destination path. Similarly for all the EAR Build follow the same steps.
- For Gateway EAR, execute GatewayEarRun.bat (GatewayEarRun.sh)
- For EJB, MDB and HTTP gateways , run the respective bat files i.e. GWEJBEarRun.bat (GWEJBEarRun.sh), GWMDBEarRun.bat (GWMDBEarRun.sh) and GWHTTPEarRun.bat (GWHTTPEarRun.sh).
- For ODT, execute ODTWarRun.bat in Windows (ODTWarRun.sh in Linux) after building odt.properties.
- For STAND ALONE SCHEDULER, execute SchedulerEarRun.bat in Windows (SchedulerEarRun.sh in Linux) for ROFC, execute TRSchedulerEarRun.bat in windows (TRSchedulerEarRun.sh in Linux) for OBTR, execute TFSchedulerEarRun.bat in windows (TFSchedulerEarRun.sh in Linux) for OBTF.After this deploy the EAR in the application console.
Note:
ExtAdapter.(JAR or WAR) is generated for ROFC in case of ELCM_INSTALLED, S(Standalone) and C(Co-deployed) OBCLExtAdapter. (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.