![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
For example, you could assign the value 7474 to the global variable RvDaemon. You can then use the variable in a Rendezvous Transport resource. At deploy time you can override the default value as needed.
• A project folder called defaultVars is available but not exposed in BusinessEvents Studio Explorer, so that you can share the global variables using source control software. It is not used for other purposes.You can export global variables to a project library and import the library into other projects (see Working with Project Libraries).
•
• From the top menus, select Window > Show View > Other > TIBCO BusinessEvents > Global Variables.
− From the toolbar, click the Global Variables Editor button.
− From the top menus, select Project > Edit Global Variables.
3. Do any of the following. (See Table 3, Global Variable Reference for a guide to the fields):
− To add a variable, click Add Variable and complete the fields.
− To add a variable group, click Add Group.
−
Using Groups Groups are used for organizing variables. Variable groups are especially useful if multiple developers share a project using a version control system. When referencing a variable that is in a group, use the complete path, for example %%mygroup/mysubgroup/myvariable%%. (Because the complete path is used, the name of a variable in a group can be the same as the name of a variable in a different group.)
4. Save the resource. Groups and references to the defaultVars.substvar file appear in the defaultVars project folder.
Table 3 Global Variable Reference For deployment with TIBCO BusinessEvents Monitoring and Management You can only override global variables if both the Deployment settable and Service Settable checkboxes are checked.For deployment with TIBCO Administrator If checked, the variable is visible and settable when deploying using TIBCO Administrator. The values set at that time are saved in the project that TIBCO Administrator creates from the provided EAR file. For deployment with TIBCO BusinessEvents Monitoring and Management You can only override global variables if both the Deployment settable and Service Settable checkboxes are checked.For deployment with TIBCO Administrator If both Deployment Settable and Service Settable are checked, the value of the global variable can be set differently for each deployable instance.Note Even if Service Settable is checked, the variable is included in the EAR only when the Include all service level global variables option is selected when building the enterprise archive file. Optional. For String and Integer types, allows you to provide a range of allowed values. The constraint field for Strings is an enumeration, for example, one, two, three. The constraint field for Integers is for a range, for example, 1-100. To use a global variable in the rule editor, use one of the System.getGlobalVariableAs* functions. For example:System.getGlobalVariableAsString("myvars/Hostname", "Localhost")Where myvars/Hostname is the name of the variable group and variable, and Localhost is an optional literal value to use if the variable is not found.To use a global variable in Debugger, add it as a VM argument. Prefix the variable with -V, as shown:-VVariable_Group/Variable_Name=
−
− At the command line, using the --propVar option, or using the -p option to specify a property file where the override properties are defined. See Starting a TIBCO BusinessEvents Engine at the Command Line in TIBCO BusinessEvents Administration.
•
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |