Precedence of Global Variables

A variable value set at the instance level overrides the same variable value set at the service level. Similarly, a variable value set at the service level overrides the same variable set at the application level.

The rules for resolving global variable values are as follows:

•

If the variable value is set at the instance level and the value is different than the variable value set in the EAR file or the variable is not deployment configurable, the value set at the service instance level is written to the TRA file of the deployed service instance and used at run time.

•

If the value at the service instance level is the same as the value inside the EAR file, but the value set at the service level is different, that value at the service level is written to the repository of the application, not to the TRA file of the deployed service instances. At run time, the service instance gets the value from the repository of the application.

•

If the variable value set at the service instance level and the variable value set at the service level are the same as the value in the EAR file, but the value set at the application level is different, that value at the application level is written to the repository of the application, not to the TRA file of the deployed service instances. At run time, the service instance gets the value from the repository of the application.

•

If the values of the variable at all the three levels, application, service, and service instance, are the same as the one in the EAR file, value at the application level is written to the repository of the application, not to the TRA file of the deployed service instances. However, if the variable is not deployment configurable, the default value will be written to the TRA file of the deployed service instances.

See "Changing Global Variables at Deployment" in TIBCO Administrator Admin User’s Guide for more details and examples of the rules.