Why are the variables TIBCO_DOMAIN, TIBCO_DEPLOYMENT, TIBCO_COMPONENT_INSTANCE in rulebase not got substituted when deployed to a domain?
Article ID: KB0085786
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Resolution:
The variables substitution will only work if you deploy the rulebase on an instance or service (called deployed on instance level). It will not work when you deploy it on agent (called deploy on agent level). You can refer to TIBCO Administrator document -> TIBCO Administrator User’s Guide -> Chapter 8 Setting Deployment Options -> Adding a Custom Rulebase to a Process or Service on deploying rulebase on instance or service level.
You can also refer to TIBCO Hawk document -> Plug-in For TIBCO Administrator -> Chapter 4 Monitoring Console about the variable substitution when using the Monitoring Console to deploy the rulebase. Please notes, the variable substitution will work if you deploy targeted to application, not machine.
The variables substitution will only work if you deploy the rulebase on an instance or service (called deployed on instance level). It will not work when you deploy it on agent (called deploy on agent level). You can refer to TIBCO Administrator document -> TIBCO Administrator User’s Guide -> Chapter 8 Setting Deployment Options -> Adding a Custom Rulebase to a Process or Service on deploying rulebase on instance or service level.
You can also refer to TIBCO Hawk document -> Plug-in For TIBCO Administrator -> Chapter 4 Monitoring Console about the variable substitution when using the Monitoring Console to deploy the rulebase. Please notes, the variable substitution will work if you deploy targeted to application, not machine.
Issue/Introduction
Why are the variables TIBCO_DOMAIN, TIBCO_DEPLOYMENT, TIBCO_COMPONENT_INSTANCE in rulebase not got substituted when deployed to a domain?
Feedback
Yes
No
Powered by
