Why do EMS-based TIBCO Administrator domains spawn an RVD process? What is the best way to configure this RVD parameter? When can configuration changes be made?
Article ID: KB0091298
Updated On:
| Products | Versions |
|---|---|
| TIBCO Administrator | - |
| Not Applicable | - |
Description
Resolution:
EMS-based TIBCO Administrator domains spawn an RVD process. This RVD process is used for the interprocess communication between TIBCO Hawk and AMI applications, which includes the deployment management code in TIBCO Runtime Agent.
By default, the Domain Utility configures the AMI RVD to use “7474; tcp:7474”. This can be changed by manually editing the property ami_rvd_session in <TIBCO_HOME>/tra/domain/<domain-name>/hawkagent.cfg.
This modification should be done at domain creation time.
Note: - Please do not change this property when applications have already been deployed in with TIBCO Administrator. Otherwise, the status of previous deployments will be lost.
EMS-based TIBCO Administrator domains spawn an RVD process. This RVD process is used for the interprocess communication between TIBCO Hawk and AMI applications, which includes the deployment management code in TIBCO Runtime Agent.
By default, the Domain Utility configures the AMI RVD to use “7474; tcp:7474”. This can be changed by manually editing the property ami_rvd_session in <TIBCO_HOME>/tra/domain/<domain-name>/hawkagent.cfg.
This modification should be done at domain creation time.
Note: - Please do not change this property when applications have already been deployed in with TIBCO Administrator. Otherwise, the status of previous deployments will be lost.
Issue/Introduction
Why do EMS-based TIBCO Administrator domains spawn an RVD process?
What is the best way to configure this RVD parameter?
When can configuration changes be made?
Feedback
Yes
No
Powered by
