Organizing HATS Web applications
By default, all HATS Web applications are stored in one enterprise archive file, such as HATS_EAR8. When you export your applications and deploy them on WebSphere® Application Server, the HATS .ear file contains a Web archive (.war) file with the resources to run each application, as well as one copy of the HATS runtime executable code. If you prefer, you can organize your applications differently, either each in its own .ear file, or in some other combination.
- Disk space
- If you create each application in its own .ear file, it has its own copy of the HATS runtime code. The runtime code is approximately 25 MB; multiply that by the number of applications you have to see how much disk space is consumed on your runtime system for all of your applications.
- Deployment
- If you redeploy a HATS .ear file, you are redeploying all the applications in that .ear file, even if some of the applications are unchanged.
- Logging and tracing
-
Logging and tracing are controlled at the level of the .ear file, not at the individual HATS application level. If each HATS application is in its own .ear file, you can control its log and trace settings independently of any other applications. If you have several HATS applications in one .ear file, log and trace settings apply to all HATS applications in the .ear file. Messages for all HATS applications in the .ear file are inserted into the same log file, and trace information for all HATS applications is inserted into the same trace file.
You can add an additional optional keyword, traceLogDirectory, to the runtime.properties file. This enables you to specify a particular directory for the output files. The file is located in the was_dir/installedApps/ear_name directory for a HATS enterprise application.
- License tracking
- License tracking is also controlled at the level of the .ear file, not at the individual HATS application level. If each HATS application is in its own .ear file, license tracking is done independently of other applications. If you have several HATS applications in one .ear file, license tracking is performed for all HATS applications in the .ear file. Information about license usage is kept for all HATS applications in the .ear file, and is inserted into the same license usage file.