Chapter 3: Configuring Real-Time Data Services

Configuring Adaptive Server to communicate with TIBCO Rendezvous Server

If you are running TIBCO Rendezvous Server and you want it to communicate with Adaptive Server, you must configure a connection bridge between the two so that Adaptive Server can read messages from and write messages to Rendezvous Server.

Creating a connection bridge between Adaptive Server and TIBCO Rendezvous Server

In the tibems.conf file, enable the tibrv_transports parameter:
```
tibrv_transports = enabled
```
Add the transport in transports.conf file, where:
- RV – is the name of the RV transport.
- type – is the type of external messaging system. Options are tibrv or tibrvcm.
- service – is the RV service port. The default is 7500.
- network – is the subnet for the host.
- daemon – is the default daemon for Rendezvous Server.
  
  You must include the path to Rendezvous Server in the PATH variable before you restart tibjmsd, the server processes that run the TIBCO messaging server.
In this example, the RV transport called RV1 is an external messaging system type tibrv that uses service port 7500 on subnet 10.22.102.0. Its daemon tcp:bigcrunch:7223, and its entry in the transports.conf file is:
```
[RV1]
type = tibrv
service = 7500
network = 10.22.102.0
daemon = tcp:bigcrunch:7223
```
Restart tibjmsd.
Add an import or export property to the create topic command. In this example, messages published to topic.rv1 are automatically sent to the RV subject named topic.rv1, and messages sent to through RV to the RV subject named topic.rv1 can be read from topic topic.rv1:
```
create topic topic.rv1 import=rv1,export=rv1
```
Add the import property to create queue command. In this example, messages sent to through RV to the RV subject named queue.rv1 can be read from queue queue.rv1:
```
create queue queue.rv1 import=rv1
```

View this book as PDF