2 Build Application for Setup

This topic explains the process for building EAR's for various application types.

  1. The process of building EAR files includes the following steps:
    1. Obtain the fcubs.properties file generated by the GUI Installer, which is saved in the required path.
      For more information, refer to FCUBS_Property_File_Creation
    2. fcubs.properties file will be used for building the ear. This will be created as part of the initial property file creation.
    3. env.properties file parameters get 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.
    4. Run the respective EAR.bat (Windows) or respective EAR.sh (Linux) file.
    5. The command window closes after the EAR is generated.
    6. The EAR will be generated in the EAR destination path provided during property file creation.
    7. JS and UIXML will also be generated in the EAR destination path if external JS/UIXML is selected during property file creation.
    8. The external path for JS/UIXML and EAR destination path can be referred to in the env.properties file.
    9. Manually copy the JS/UIXML generated in the EAR destination .path, to external JS/UIXML path.
  2. Maintain the following Application Type accordingly for building respective EAR's.

    Table 2-1 EAR Creation

    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.prop erties
    GW-Individual INDIVIDUAL Not Required ROFCGatewayEarRun.b at or ROFCGatewayEarRun.s h GW_WS_Prop.ppro perties
    GW-REST INDIVIDUAL Any Distinct Name ROFCGatewayRestEar Run.bat or ROFCGatewayRestEar Run.sh GW_RESTEJB_Pro p.properties
    GW-MDB GATEWAY Any Distinct Name GWMDBEarRun.bat GWMDBEarRun.sh GW_MDB_Prop.pro perties
    GW-HTTP GATEWAY Any Distinct Name GWHTTPEarRun.bat GWHTTPEarRun.sh GW_HTTP_Prop.pr operties
    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
  3. The env.properties will have the appropriate application type set.
  4. Go to \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.
  5. EAR file will be generated in the mentioned destination path. Similarly, all the EAR Build follow the same steps.
  6. For Gateway EAR, execute <Product Name>GatewayEarRun.bat (<Product Name>GatewayEarRun.sh)
  7. 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).
  8. For ODT, execute ODTWarRun.bat in Windows (ODTWarRun.sh in Linux) after building odt.properties.
  9. For STAND ALONE SCHEDULER, execute SchedulerEarRun.bat in Windows (SchedulerEarRun.sh in Linux).
  10. After this, deploy the EAR in the application console.

    Note:

    Please ensure the necessary resources are created in the application server as mentioned in the Resources_To_ Be_Created