Configurations to be reviewed when changing the machine name where the TIBCO Business Events (BE) servers (Inference, Query, Cache, Rule Management Server) are running.
Article ID: KB0085808
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
If you are going to change the name of the machine(s) where the BE servers are running then please review the following configurations before doing so.
1. If you have configured Cache based object management (Cache + Memory or Cache Only) for your BE servers then you need to review the cluster discovery settings of server .tra files. If you are using hostname in discovery configuration (multicast or well-known-addresses) then modify the following properties accordingly.
- java.property.tangosol.coherence.wkan (well-known-addresses)
- java.property.tangosol.coherence.localhost (multicast or well-known-addresses with mulitple network cards)
2. If you have enabled RMI functionality in your inference engines then you would need to check the following RMI property.
- be.engine.cluster.rmi.host
3. If you have any BE Rule Management Servers running with remote connectivity enabled then change the following property in the be-rms.tra file:
- tibco.clientVar.RMS/hostname
Environment:
============
o TIBCO BusinessEvents 3.0.1
o All OS
Issue/Introduction
Feedback
