1 Building Application for Setup

The process of building EAR/WAR for various application types files includes the following steps:

1. The process of building EAR/WAR 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 Treasury Management Installer Property File Creation document
   2. fcubs.properties file will be used for building the WAR. 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 OBTR, Gateway, Scheduler, etc.). After Property file creation, proceed with respective EAR/WAR build and then proceed with other components property file creations and build.
   4. Run the respective .bat (Windows) or respective .sh (Linux) file.
   5. The command window closes after the EAR/WAR is generated.
   6. The EAR/WAR will be generated in the EAR/WAR destination path provided during property file creation.
   7. JS and UIXML will also be generated in the EAR/WAR destination path if external JS/UIXML is selected during property file creation.
   8. The external path for JS/UIXML and EAR/WAR destination path can be referred to in the env.properties file.
   9. Manually copy the JS/UIXML generated in the EAR/WAR destination .path, to external JS/UIXML path.
2. Maintain the following Application Type accordingly for building respective EAR/WAR's.

   Table 1-1 EAR/WAR Creation

   Product Type	Application Type	EAR Name	BAT/sh file to be run	Property file to be used	Folder Location in Destination Path
   TR	OBTR	Any Distinct Name	TREarRun.bat or TREarRun.sh	fcubs.properties	WAR file in 'build' folder
   GW-Integrated	INTEGRATED	Any Distinct Name	TRGatewayEarRun.b at or TRGatewayEarRun.sh	GW_WS_Prop.properties	EAR file in Destination folder
   GW-Individual	INDIVIDUAL	Not Required	TRGatewayEarRun.b at or TRGatewayEarRun.sh	GW_WS_Prop.properties	WAR file in 'gatewayBuild' folder
   GW-REST	INDIVIDUAL	Any Distinct Name	TRGatewayRestEar Run.bat or TRGatewayRestEar Run.sh	GW_RESTEJB_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	TRSchedulerEarRun.bat or TRSchedulerEarRun.sh	Scheduler.properties	WAR file in 'buildScheduler' folder
   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 <product Type>EarRun bat file for EAR build.
   For Example, <product type>EarRun.bat:- TREarRun.bat (TREarRun.sh for running in Linux machine) for TR and so on.
5. EAR file will be generated in the mentioned destination path. Similarly, all the EAR Build follow the same steps.
   1. For Gateway EAR, execute <Product Name>GatewayEarRun.bat (<Product Name>GatewayEarRun.sh)
   2. For MDB and HTTP gateways , run the respective bat files i.e. GWMDBEarRun.bat (GWMDBEarRun.sh) and GWHTTPEarRun.bat (GWHTTPEarRun.sh).
6. For ODT, execute ODTWarRun.bat in Windows (ODTWarRun.sh in Linux) after building odt.properties.
7. For STAND ALONE SCHEDULER, execute TRSchedulerEarRun.bat in Windows (TRSchedulerEarRun.sh in Linux).
8. After this, deploy the EAR/WAR in the application console.

   Note:

   Please ensure the necessary resources are created in the application server as mentioned in the Resources to be Created document.