Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 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).
For deployment using TIBCO Administrator, the configuration Name field value must match the project name  The project does not deploy if they are different. The actual EAR file name, however, can differ from the configuration name.
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.
Modifying Ignored Resources List  Certain files (and folder names) are excluded from the EAR. To maintain the list of exclusions, in TIBCO BusinessEvents Studio, select Window > Preferences > TIBCO BusinessEvents > Code Generation >Ignored Resources. See Setting Preferences for more on this topic.
EAR File Encoding
Default Encoding
The default encoding of the EAR files generated by TIBCO BusinessEvents Studio is ISO8859-1. This is also the default encoding of TIBCO Administrator. To upload an EAR file to TIBCO Administrator, the EAR file encoding must match the TIBCO Administrator encoding.
To Change the Default EAR File Encoding
To change the default EAR file encoding, define a global variable named MessageEncoding and set its value to the desired encoding. For example, UTF-8.
Options for Deploying the EAR
For deployment options see Chapter 5, Deploying and Managing Engines with MM and Chapter 8, Deploying With TIBCO Administrator 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 TIBCO BusinessEvents Administration.
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.
By default, EAR files are built in memory. The compiler does not use the file system during code generation. Instead, the Studio JVM is used to load all the Java classes and resources into memory until the build process is completed. However, you can choose to use the file-system based compiler to build EAR files.
1.
In TIBCO BusinessEvents Studio, select the menu Window > Preferences to open the Preferences dialog.
2.
Select TIBCO BusinessEvents > Code Generation on the left panel and then set the Compilation Mode to File System.
When using the Studio Tools utility to build an EAR file, set the option -lc to use the file-system based legacy compiler.
When building an EAR file in memory for a large project, the JVM may run out of PermGenSpace and/or heap space. In such cases, edit the BE-HOME/studio/eclipse/studio.ini and BE-HOME/studio/bin/studio-tools.tra file to set appropriate values for the JVM settings. By default the heap size is set to -XX:MaxPermSize=256m.
 
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.
Note  For deployment using TIBCO Administrator, the configuration Name field value must match the project name. The project does not deploy if they are different. The actual EAR file name, however, can differ from the configuration name.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved