If you experience out of memory issues, or just want to debug function invocations or check consuming memory by Rendezvous daemon internals, you can enable undocumented profiling feature. 

You need to go to http://rvd_host:7580/profiling URL. On the page select the desired check-boxes and then press submit.

Daemons profiling data will be in the log, you can view it on the screen, however better to start rvd or rvrd with log parameters -logfile c:\logs\rvd.log -log-max-size 1024 -log-max-rotations 5and look at the log files.



For training on TIBCO mail us at [email protected]

The TIBCO Rendezvous (RV) messaging system must be installed on your local machine to configure a RepConnector connection with RV or RV Certified Messaging (CM) inbound/outbound types. To route the replication event to a TIBCO ActiveEnterprise (AE) subscriber, the TIBCO ActiveEnterprise SDK must be installed and configured with the customized wire-message format.

RepConnector supports RV and RVCM messaging with a local or remote RV daemon, and AE Certified Messaging (CM) with the local TIBCO SDK installation. This section describes some basic instructions and samples of the RV configuration. See Chapter 6, “Configuring RepConnector,” for information about configuring AECM connections..

Steps Running an rvd process on the local or remote machine.

If you run the rvd process on a remote machine, you must also run the rvrd process on the local machine to deliver the messages to the remote rvd process.

1. Navigate to the TIBCO Rendezvous installation bin directory. For example:

*On UNIX, enter:  cd /opt/tibco/tibrv/bin

*On Windows, enter: cd C:\TIBCO\TIBRV\bin

2. Invoke the rvd daemon process by entering: rvd

Steps Configuring the RV routing daemon

To deliver the message from the RepConnector connection to the remote RV daemon:

Note : You can skip this procedure if you use the local RV daemon for either the inbound or outbound messaging system.

1. Navigate to the TIBCO Rendezvous installation location bin directory.

* On UNIX, enter: cd /opt/tibco/tibrv/bin

* On Windows, enter: cd C:\TIBCO\TIBRV\bin

2. Invoke the rvrd daemon process.

* On UNIX, enter:  rvrd -store ./storefile
where ./storefile is the name of the local storage file for rvrd.

* On Windows, enter: rvrd -store .\storefile
where .\storefile is the name of the local storage file for rvrd.
Note : If you are configuring to use the routing daemon, supply the following:

* Service name for the local daemon
 
*Network value for the machine where the RV routing daemon process is running

* Daemon value for where the rvd process is running when you are defining the RepConnector connection




For training on TIBCO mail us at [email protected]

rvcache Command
Syntax :
rvcache -store filename
[-http [ip_address:]http_port]
[-https [ip_address:]https_port]
[-http-only]
[-https-only]
[-no-http]
[-idle]
[-sync interval]
[-merge shallow | deep]
[-memory-only]

Purpose
The program rvcache stores data from recent messages, indexed by subject name, and automatically sends the cached data to new listeners.
Remarks
Given a set of one or more subject names, rvcache listens for messages addressed to those subjects. Each time it receives such a message, it stores the message’s data content.
When a client program queries for a cached subject, rvcache sends a reply message with the current cached value.
Browser Administration Interface
To administer or configure rvcache, view http://rvcache_host:http_port with a web browser. When the program starts, it prints the actual HTTP administration port.
State
rvcache can run in either of two states—running or idle.
When running, rvcache listens to subjects, caches message values, and responds to queries.
When idle, rvcache does not operate; however, the browser administration interface is available for configuring parameters.
Initial Subject Configuration
The first time you run rvcache, you must configure its subjects and change its state to running. After that, rvcache reads the subject list from its file.
Storage
rvcache stores the data in process memory and in a disk file. The command line parameter -store specifies the name of the disk file; if the file exists when rvcache starts, then rvcache reads the file to initialize its configuration parameters and to populate its cache in process memory.
The command line parameter -sync specifies the interval at which to synchronize the file-based store with process-based store.
Steps as follows :

Certified Messaging :

Certified Messaging (CM) guarantees that
1. Message will be sent.
2. The order of the message will be same as sent.

The parameters for the CM transport:
Daemon
Service
Network
CMname
Ledger

CM which will allow persistant mechanism for the messages channeled using rendezvous.
——————————————————————————————–
RVCM configuration

tibrvcm.conf :This file defines the TIBCO Rendezvous certified messaging (RVCM) listeners for use by topics that export messages to a tibrvcm transport. The server preregisters these listeners when the server starts up so that all messages (including the first message published) sent by way of the tibrvcm transport are guaranteed. If the server does not preregister the RVCM listeners before exporting messages, the listeners are created when the first message is published, but the first message is not guaranteed. The format of this file is
transport listenerName subjectName

—————————————————————————————–

Difference between Reliable delivery and Certified delivery?

Reliable Delivery:
Ledger: None
Time Limit: Contains outbound messages for 60 seconds
Network Traffic: Minimal
File Storage: No file storage

Certified Delivery:
Ledger: The certified delivery library records outbound messages in a ledger, either within the program process storage, or in file storage.

Time Limit: The certified delivery library retains outbound messages in the ledger until either delivery is complete or the time limit (set by the program) expires.

Network Traffic:Additional network overhead to confirm delivery of each certified message.
File Storage: Optional file-based ledgers consume file storage for each message until delivery is complete (or the time limit expires).

———————————————————————————————————–

Why EMS-RV communication?

f you are doing migration of the projects ( in general, trading apps, most of the trading apps are using RV and other examples are TIBCO IM ) you can bridge messages to EMS or to RV and vice versa, and can do your migration very easily.

another good example of this scenario might be if you are using RV along the company and want to integrate an application that can communicate via JMS out of the box. Building a RV-JMS bridge might be much easier than developing the code to do that.

Message interaction between programs :

Three distinct kinds of interactions occur between programs  in Rendezvous environment.

Publish/Subscribe interactions.
Request/Reply interactions.
Multicast Request/Reply interactions.

Publish/Subscribe interactions:

These are driven by events. Communication is in one directions. The interaction consists of one multicast message, published once and received by all subscribers.

Example: Publishing the latest stock prices to hundreds of traders on a trading floor simultaneously.

Request/Reply Interactions

These interactions are driven by demand for data. The client requests data from a server, the server computes the individual response and returns it to the client. Communication flows in both directions. This consists of two point to point messages  : a request and a reply.
Example: transaction processing in ATM banking

Multicast Request/Reply Interactions

These interactions are also drive by demand for data. In Multicast request/reply, multiple servers can receive the request and respond. Communication is in both directions. Complete interaction consists of one multicast request message and any number of point-to-point messages
Example: Database query with multiple servers.

Remote RV communication :

Rendezvous uses ‘UDP’ protocol to communicate within the network locally. For communicating beyond the subnet or the network, it uses Remote RV’s (RVRD). RVRD uses ‘HTTP’ protocol for communicating outside the network. Each subnet can be divided into different IP addresses using different port no’s. This in turn leads to multicasting.

One of the machines in each subnet  on which RVRD is configured communicates with the other configured RVRD machine in the other subnet. In other words, these RVRD configured machines act as gateways in their respective subnets as each message is sent through these machines for any machine in the subnet to communicate with a machine in the different subnet.

-service “7500″ -network “113.193.125.221″ -daemon “tcp:7500″ “BW.Start” “hello world”



For training on TIBCO mail us at [email protected]

The following procedure explains how to configure the routing daemon between an NT host (JVR) and a Unix host (Cisco CNS PerfE).
We will use the following sample IP addresses:
•JVR host IP address: 128.1.13.105.
•Cisco CNS PerfEhost IP address: 172.1.15.110.
Windows NT Installation
On a Windows NT system, use the following steps:
Step 1 Make sure to uninstall any services registered for TIBCO.
Step 2 Run rvntscfg.exe to uninstall rvd, rva, etc.
Step 3 Install rvrd with the options:
-permanent -store c:\rvrd.db -logfile c:\rvrd.log
Step 4 Start the rvrd service. By default, it will start the service at port 7500 and the http port at 7580.
Step 5 Open the web interface for rvrd:
http://128.107.133.105:7580
Step 6 Add a routing entry as follows:
a. Click on Routers.
b. Enter the router name, JVRHOST and click Add.
c. For the route for JVRHOST, add a local network as follows:
     1. Click on Local Networks and add the network information:
          Network Name: JVRNetwork
          Service: 7500
          Network Specification: 128.107.133.105
     2. Click on Add Local Network. Double-click the newly added local network to specify the subject filtering,
          enter as appropriate or enter “>” to accept every subject,
     3. Click on Add for import and export.
Step 7 For the route for JVRHOST, add PERFEHOST as a neighbor:
     a. Click on Neighbors and add the network information:
          Neighbor Name: PERFEHOST
          Host IP Address: 172.29.146.110
          Remote port: 7510
          Local Port: 7510
     b. Click Add Active [all].
Alternatively, you can listen for messages from all Cisco CNS PerfEs just by selecting the top option and specifying the local port number as 7510.
This completes the rvrd configuration under Windows NT.
Unix Installation
On a Unix system, use the following steps:
Step 1 Make sure that Cisco CNS PerfE is stopped using stop.sh all.
Step 2 Make sure that all the processes (rvd, rva) are shut down.
Step 3 Make sure that the DAS_HOME environment variable is set:
           $> sh
           $> . $DAS_HOME/bin/env.sh
           $> rvrd -listen tcp:7500 -store $DAS_HOME/config/rvrd.cfg
From the web browser, go to http://172.29.146.110:7580 and administer rvrd on the Cisco CNS PerfE host as follows:
Step 4 Add a routing entry:
          Router name: PERFEHOST
Step 5 For the TIBCO router PERFEHOST, enter the local network as follows:
          Networkname: PERFENetwork
          Service: 7500
          Network Specification: 172.29.146.110
          Specify the subject appropriately or as >.
Step 6 For the route PERFEHOST, add JVRHOST as a neighbor:
     a. Click on Neighbors;
          Neighbor Name: JVRHOST
          Host IP Address: 128.107.133.105
          Remote port: 7510
          Local Port: 7510
     b. Click Add Active [all].
This completes the Unix/PerfE side rvrd configuration.


Now both daemons are configured appropriately to talk to the networks and they establish TCP connections on port 7510.




For training on TIBCO mail us at [email protected]

These are few tips/commands/concept which essential while working with tibco rv  for resolving day to day problems or issues.

How to send message from command prompt using tibrvsend ?
tibrvsend -network “190.231.54.20″ -service “5420″ -daemon “tcp:7500″ “TESTING”

How to receive message in command prompt using tibrvlisten ?
tibrvlisten -network “190.231.54.20″ -service “5420″ -daemon “tcp:7500″

How do you identify whether tibco rv  is running in your host or not ?
ps –ef | grep rvd (in linux) , for windows check rvd in task manager. ,if tibco rv is running then rvd must be a live process.

How do you identify which services are subscribed from localhost ?
netstat –g

How do you identify which services and clients are connected to your host via tibco rv ?
We can use tibco rv  admin webpage , which listens on some predefined port e.g. 7542 http://host:7540 and then we can get all the details

Can we specify which NIC card to use while specifying network parameter?
Yes , we can specify e.g. eth1;190.230.54.80 , if don’t give any NIC card name then it will bind to default eth0 card.

What will happen if same service e.g. 5480 tries to register with two network e.g. 190.230 and 192.230 ?
Tibco RV  will not allow that , it will throw exception while creating transport you can see that exception in tibco rv log via webpage.

What is the standard location for applications using TIBCO RV (Rendezvous)?
The latest TIBCO RV libraries will always be available through the following location:
• /opt/tibops/rv/lib
Previous versions of the libraries can be access through:
• /opt/tibops/RV//lib

How to change reliablity parameter ?
This is a startup parameter , you can see it by greping in ps –ef | grep rvd, for chaning it you need to disconnect all the application connected to that RVD and restart.



For training on TIBCO mail us at [email protected]

Tibco RV messagging
1) location transparency
2) platform independence
3) reliable and fast
4) comprehensive API
5) point to point delivery and publish/subscribe delivery.

Location transparency
———————–
Location transparency means for sending and receiving message on a multicast network you need not to aware of physical location of sender or receiver as long as you know the topic( also called subject in tibco world) , so its pretty simple Sender publish message on multicast topic in a network and all subscriber which have subscribed on that topic receives message without being knowing physical location of publisher.

Sender could be anywhere in the world e..g New york ,Tokyo , London , receiver can be anywhere e.g. London , Hongkong , Tokyo.

Platform independence
———————–
its doesn’t depend on platform , Sender can be running on unix box while receiver could be running on windows machine. most of the time GUI runs on windows and Server
runs on Linux and they exchange messages via tibco.

Reliable and Fast
—————--
TIbco RV makes best effort (not guaranteed) to deliver message to receiver
and its very fast usually used to send Market data etc but not used for sending Order or execution message because there is always chance of loosing such message.
generally we use  certified message to make guaranteed delivery of those message.

Comprehensive API
—————--
tibco rv comes with rich API in both C++ and Java language and can be plugged to application easily, API provides methods and classes for different modes of communication e.g. Point to Point , publish/subscribe , certified messaging etc.

Point to Point Deliver
———————–
Tibco can be used for point-2-point delivery (some times also called Request/Reply mode), it used “INBOX” topic for doing so , when  tvd sees INBOX topic instead of publishing that message into multicast network it makes direct connection to destination host and sends message.

Publish/Subscribe
——————-
This is achieved using “Subject” or “Topic” , receiver subscribes on multicast network on a particular topic and Sender sends message on those Topic, after that its tibco’s responsibility to deliver those message.



For training on TIBCO mail us at [email protected]

Every host where tibco rvd is running expose on HTTP interface using that we can get many useful information e.g

— How many clients are connecting to a particular service
— Which services has been subscribed by rvd
— Which hosts are connected to this rvd.
— How much data has been sent to received
— Viewing tibco log to figure out any tibco issue.
— Hwo many subject a particular service is using and what are those etc.

to check on which Http port your rvd is publishing information do this in your linux/windows host where rvd is running

ps -ef | grep rvd

this will show rvd process with parameters used for starting “-http 7582″ shows that http interface is on port 7582
now just type this in your browser.

http://hostname:7582/




For training on TIBCO mail us at [email protected]

The purpose of this -short- tutorial is to guide you until you can send and read a « HelloWorld » message passing through Tibco RendezVous

Installation

• Set the variable JAVA_HOME
  Eg, in my case:
  
  set JAVA_HOME=C:\java\jdk150_10
  
  
• Get the file to be installed:
  
• TIB_rv_8.1.2_win_x86_vc8.zip
• Unzip the content in your local drive
• Launch the installer (.exe)
  • select Custom installation
  • choose the installation folder, eg: C:\tibco
  • keep default options for other requests
• Set the variable TIBRV_HOME
  Eg, in my case:
  
  set TIBRV_HOME=C:\tibco\tibrv\8.1
  
  

Main Runnables
RVD: Daemon
Launching the daemon on local host on port 8181 (default port: 7580):

rvd -http 8181

You should see the following trace:
C:\tibco\tibrv\8.1\bin>rvd -http 8181 

TIB/Rendezvous daemon 
Copyright 1994-2008 by TIBCO Software Inc. 
All rights reserved. 

 Version 8.1.2 V8 9/26/2008 
2010-01-19 16:37:02 rvd: Command line: rvd -http 8181 
2010-01-19 16:37:02 rvd: Hostname: MYLOCALMACHINE
2010-01-19 16:37:02 rvd: Hostname IP address: 123.123.123.123 
2010-01-19 16:37:02 rvd: Detected IP interface: 123.123.123.123 (IP00) 
2010-01-19 16:37:02 rvd: Detected IP interface: 127.0.0.1 (loopback) 
2010-01-19 16:37:02 rvd: Unable to find ticket file tibrv.tkt in PATH 
2010-01-19 16:37:02 rvd: Http interface - http://myLocalMachine.myDomain:8181

tibrvsend: send a message
To send a message on myLocalMachine:7580:

.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage

Expected output:

C:\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage 

 Publishing: subject=mySubject "myMessage" 
2010-01-19 16:52:11 RV: TIB/Rendezvous Error Not Handled by Process:
 {ADV_ ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" expiretime=2010-01-19 16:02:11Z host="10.30.226.147"}

tibrvlisten: listen to messages
Abstract
To listed to messages published on MYLOCALMACHINE:7580, related to subject mySubject:

tibrvlisten -service 7580 -network MYLOCALMACHINE mySubject

Use case: HelloWorld
For instance, let’s assume that you launch this command from one frame:

C:\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network localhost mySubject HelloWorld Publishing: subject=mySubject "HelloWorld"

Here is what appears in the « listening » frame:

2010-01-19 17:01:32 (2010-01-19 16:01:32.990000000Z): subject=mySubject, message={DATA="HelloWorld"}

Notice you can have many instances listening to the same messages.

Other runnables
Launch the daemon manager

• Launch:
  
  cd %TIBRV_HOME%/RVDM ./RVDM.bat -http 8282 .
  
  
• You should see following messages, that you can ignore:
  2010-01-19 13:01:48 rvdm: RVDM has activated. 2010-01-19 13:02:03 RV: TIB/Rendezvous Error Not Handled by Process: {ADV_ ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" e xpiretime=2010-01-19 12:11:48Z host="123.123.123.123"}
  
  
• To check the daemon is on, you can open the address http://localhost:8282 on your favorite browser.

Example sources
Example sources are available in folder %TIBRV_HOME%/src/examples/java

Misc
TIBRV_HOME\bin folder fosters a couple of binaries:

• rvntscfg.exe: Services Configuration Program

For training on TIBCO mail us at [email protected]

1. Start RVRD on both the boxes, i.e. box A and box B, which are in two different subnets.

2. Open the http interface of both the RVRDs in two different browser instances.

3. Click on the router link, add a unique router name for both the instances.

4.Then click on the local network link on the same page (which will be initially shown as 0), add the local network name, service, network specification and cost and click on add.

5. Then go to the routers link, click on the neighbours link (initially shown as zero), in the remote end point, put the hostname/ip address of the other RVRD box as well as the router name for the other RVRD and add the neighbor interface. In the port, use a TCP port that has been opened by your firewall. In this page, you can select on the type of your neighbors as well, i.e. accept any, passive etc. Default is ACTIVE-ACTIVE, i.e. any of these two RVRDs can initiate a connection to the other RVRD.

6. Follow step 4 and 5 for the other RVRD too.

7. Wait for some time and then click on the “Connected Neighbors” link to see if the connection is established between these two RVRDs.

8. Now for data communication, click on the local network name from the routers page and specify the export/import list of the subjects. This will enable your RVRD to send and receive the messages to/from the other network, which match these export/import subject.

9. Try a tibrvlisten/tibrvsend test on one of the exported/imported subject on both sides to check that the communication is happening.



For training on TIBCO mail us at [email protected]