How to configure IC 5.x and greater or IcRules to work with subnets.
Article ID: KB0091664
Updated On:
| Products | Versions |
|---|---|
| TIBCO InConcert | - |
| Not Applicable | - |
Description
Resolution:
Description: When using RV across subnets you must have an rvrd daemon but default
behavior for InConcert is to only use rvd. Hence even though rvrd is
running InConcert will start up an rvd session instead of using the rvrd
daemon.
I had to set the IC_TIBRV_SERVICE, IC_TIBRV_DAEMON and
IC_TIBRV_NETWORK environment parameters on the client
side where the IC Adapter (which uses the
IcClient.directInitialize call) uses these variables
to connect to rvrd.
The server side parameters were specified in
IcServer.cfg file, and connect to its rvrd. NOTE the IcRepDaemon
does not read the *.cfg files and must have explictly set environmental
variables.
One rvrd were configured to accept any neighbor on
local port 7510, and the second rvrd were configured
to have a local port of 7510. The port numbers are arbitrary.
Description: When using RV across subnets you must have an rvrd daemon but default
behavior for InConcert is to only use rvd. Hence even though rvrd is
running InConcert will start up an rvd session instead of using the rvrd
daemon.
I had to set the IC_TIBRV_SERVICE, IC_TIBRV_DAEMON and
IC_TIBRV_NETWORK environment parameters on the client
side where the IC Adapter (which uses the
IcClient.directInitialize call) uses these variables
to connect to rvrd.
The server side parameters were specified in
IcServer.cfg file, and connect to its rvrd. NOTE the IcRepDaemon
does not read the *.cfg files and must have explictly set environmental
variables.
One rvrd were configured to accept any neighbor on
local port 7510, and the second rvrd were configured
to have a local port of 7510. The port numbers are arbitrary.
Issue/Introduction
How to configure IC 5.x and greater or IcRules to work with subnets.
Environment
Product: TIBCO InConcert
Version: All
OS: All
--------------------
Feedback
Yes
No
Powered by
