Project Tasks : Building an Enterprise Archive (EAR File)

Building an Enterprise Archive (EAR File)
You can build an enterprise archive file using a TIBCO BusinessEvents Studio dialog, and also using a command-line utility (see Building an Enterprise Archive (EAR File) at the Command Line for details).
Do not store the EAR file in a project folder  Doing so includes the prior EAR file when you build the EAR file again, needlessly increasing the size.
Deployment Options
For deployment options see Chapter 8, Deploying and Managing Engines with MM and Chapter 10, Deployment Using TIBCO Administrator and at the Command Line in TIBCO BusinessEvents Administration. For testing purposes, you may find it useful to refer to the section Starting a TIBCO BusinessEvents Engine at the Command Line in that guide.
Building an EAR File in TIBCO BusinessEvents Studio
When testing project before development, you may want to build the EAR as explained here, and run the project at the command line.
1.
If you see a message asking you to save all project resources, click Yes. It means an unsaved resource editor is open.
2.
3.
Click Apply to save the configuration details.
(To revert to the version already saved, click Revert.)
4.
Click OK to build the archive.
Before TIBCO BusinessEvents packages the EAR file, it generates the Java code in a temporary directory. After the files are packaged in the EAR file, then the temporary files and directory are deleted.
You can choose to keep the generated Java files, for example to troubleshoot some problem with an EAR file. To do so, uncheck the Delete Temporary Files checkbox, and specify where to store the Java files in the Compilation Directory field.
If you uncheck the Delete Temporary Files checkbox, specify the directory where you want to save the Java files generated during the process of building the EAR file.