1 Building Application for Setup
The process of building EAR files includes the following steps:
- Obtain the fcubs.properties (Refer OBTF_Installer_Property_File_Creation document) 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 OBTF, 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.
Table 1-1 Standalone
| Product Type | Application Type | EAR Name | BAT/sh file to be run | Property file to be used |
|---|---|---|---|---|
| TF | OBTF | Any Distinct Name | TFEarRun.bat or TFEarRun.sh | fcubs.properties |
| GW-Integrated | INTEGRATED | Any Distinct Name | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_Prop.properties |
| GW-Individual | INDIVIDUAL | Not Required | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_Prop.properties |
| GW-REST | INDIVIDUAL | Any Distinct Name | TFGatewayRestEarRun. bat or TFGatewayRestEarRun. Sh | GW_REST_Prop.properties and GW_RESTEJB_Prop.properties |
| GW-Individual | INDIVIDUAL | Not Required | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_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 | GATEWAY | Any Distinct Name | TFSchedulerEarRun.bat or TFSchedulerEarRun.sh | Scheduler.properties |
| ODT | ODT | Any Distinct Name | ODTWarRun.bat or ODTWarRun.sh | ODT.properties |
Co-Deployment:
Co-Deployment with FCUBS: Refer: FCUBS_EAR_Building.pdf
prerequisite:
- Inside OBTF release or patchset "ADAPTERS", "WS" folders to be merged with the same folders present in FCUBS release or patchset.
- Similarly inside release or patchset "OBTF" folder to be copied parallel to "ROFC" folder in FCUBS release or patchset.
Note:
In case of OBTF co-deployment with other product processors (without FCUBS) *.bat/*.sh of both OBTF and product processors also to be run.| Product Type | Application Type | EAR Name | BAT/sh file to be run | Property file to be used |
|---|---|---|---|---|
| TF | OBTF | Any Distinct Name | TFEarRun.bat or TFEarRun.sh | fcubs.properties |
| GW-Integrated | INTEGRATED | Any Distinct Name | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_Prop.properties |
| GW-Individual | INDIVIDUAL | Not Required | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_Prop.properties |
| GW-REST | INDIVIDUAL | Any Distinct Name | TFGatewayRestEarRun. bat or TFGatewayRestEarRun. Sh | GW_REST_Prop.properties and GW_RESTEJB_Prop.properties |
| GW-Individual | INDIVIDUAL | Not Required | TFGatewayEarRun.bat or TFGatewayEarRun.sh | GW_WS_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 |
Co-Deployed with FCUBS: SchedulerEarRun.bat or SchedulerEarRun.sh Co-Deployed with other product processor: TFSchedulerEarRun.bat
or TFSchedulerEarRun.sh and<Product_Procesor> SchedulerEarRun.bat or <Product_Procesor> SchedulerEarRun.sh |
Scheduler.properties |
| 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.
- Go to \INSTALLER\SOFT path and execute the <Product Type>EarRun bat file for EAR build.
For Example: <Product Type>EarRun.bat:- TFEarRun.bat (TFEarRun.sh for running in Linux machine) for OBTF 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 <Product Name>GatewayEarRun.bat (<Product Name>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 TFSchedulerEarRun.bat in Windows (TFSchedulerEarRun.sh in Linux).
Note:
Please ensure the necessary resources are created in the application server as mentioned in the OBTF_Resources_To_ Be_Created.docx