Migrating from Earlier Versions : Legacy Locations Used in Migration

Legacy Locations Used in Migration
Determining the TIBCO Repo URL for BusinessEvents
When applications are started outside of a TIBCO Administrator domain, the TIBCO repo URL is the file location of the project EAR file. You add a property to the engine property file, be-engine.tra to specify the location:
tibco.repourl location of EAR file
When TIBCO Administrator is used to deploy a BusinessEvents application, the tibco.repourl property is added to the generated TRA file (see Location of TIBCO Administrator-Generated Property File).
The value of this property is the URL of the project repository. The URL format depends on the deployment transport used. Supported formats for the URL are tibcr, http, https, and file (local).
You can use a tibcr:// URI to identify the server-based repository location. For full details about its allowable parameters, refer to TIBCO Adapter SDK™ documentation.
One way to determine the repo URL is to temporarily deploy the BusinessEvents EAR. The repo URL is in the deployed BusinessEvents instance TRA file. However, you must remove the escape characters (back-slashes). You must then undeploy the BusinessEvents instance after obtaining the tibco.repourl value.
Location of TIBCO Administrator-Generated Property File
When it deploys a BusinessEvents project, TIBCO Administrator reads the properties from the engine property file located in BE_HOME/bin/be-engine.tra and then incorporates the deploytime configuration values set in the TIBCO Administrator user interface. (Property values set in TIBCO Administrator override those set in the BE_HOME/bin/be-engine.tra file).
TIBCO Administrator then generates a property file for runtime use in this location:
TIBCO_HOME/tra/domain/domain_name/application/application_name/application_name.tra
After deployment, the generated file is used, and not the file in BE_HOME.