RTView® 
User Guide


Communicating with TIBCO Rendezvous

NOTE: The TIBCO Rendezvous data source may not be licensed in your RTView installation.

By default, the Display Builder and Display Viewer Application communicate with TIBCO Rendezvous using the TIBCO Rendezvous Daemon (rvd) process. The rvd process is automatically started by TIBCO Rendezvous whenever it is needed and runs as a background service. Due to security restrictions, TIBCO Rendezvous requires that applets communicate using the TIBCO Rendezvous Agent Process (rva). This process must be started manually and must be configured for your message subjects. The rva process must already be running before the Display Viewer Applet is started.

If you do not want to use the rva process, you may redirect TIBCO data through the Data Server. This also eliminates the requirement to run the Display Viewer Applet from a web server.

In order to facilitate testing, you may run the Display Builder and Display Viewer Application using rva. As with the Display Viewer Applet, the rva process must already be running before the Display Builder or Display Viewer Application are started in rva mode.

Running the TIBCO Rendezvous Agent Process
The TIBCO Rendezvous Agent Process (rva) must be running in order for RTView to send and receive messages. RTView assumes that rva is running on your local machine using the default port. If rva is running on a different host or port, you will need to specify both the host and the port either in the Application Options dialog or on the command line.

Review the appropriate section below to determine what host and port parameters you will need to specify. If you are not sure which section applies to you, contact your TIBCO Rendezvous system administrator.

If you have never run rva, you must configure rva to import and export your message subjects. You will also need to configure rva in order to utilize the RTView data simulator, which sends TIBCO Rendezvous messages.


If rva is already running on your local machine
You do not need to specify a host. You do not need to specify a port if rva is running on the default port. Otherwise, you will need to specify a port in the Application Options dialog or on the command line. Please refer to TIBCO Rendezvous documentation for more information on running rva.

You will need to Configure the TIBCO Rendezvous Agent Process in order to utilize the data simulator. The data simulator, which sends TIBCO Rendezvous messages, is necessary to work through the examples in the documentation.


If rva is running on another machine on your network
You need to specify the name of the host that is running rva. You do not need to specify a port if rva is running on the default port. Otherwise, you will need to specify both the host and the port in the Application Options dialog or on the command line. Please refer to TIBCO Rendezvous documentation for more information on running rva.

You will need to Configure the TIBCO Rendezvous Agent Process in order to utilize the data simulator. The data simulator, which sends TIBCO Rendezvous messages, is necessary to work through the examples in the documentation.


If rva is not already running
You need to start rva on your local machine:

1. Open a Command Prompt window, go to <rendezvous installation>\bin and type

    rva -store rvafilename

where rvafilename is the name of the file where your rva settings are stored. If you have never run rva this file will not exist. In this case, rva will create a file by the name you specify and save the rva settings to that file.

2. This will start rva and print some information regarding rva to the console. Note the following information:

         RVA: Http interface:
         RVA Listen:
         RVA Host:

RVA Listen will be the port and RVA Host will be the host that you will use to run RTView. The RVA Http interface (e.g.: http://hostname:7680/) is necessary to configure rva to work with messages sent by the data simulator.

3. If the RVA Listen is 7600 and RVA Host is the name of the machine you are running on, you will not need to specify either parameter. Otherwise, you will need to specify the host and/or the port in the Application Options dialog or on the command line. Please refer to TIBCO Rendezvous documentation for more information on running rva.

4. Since you have never run rva you must Configure the TIBCO Rendezvous Agent Process to import and export your message subjects. You will also need to configure rva in order to utilize the data simulator. The data simulator, which sends TIBCO Rendezvous messages, is necessary to work through the examples in the documentation.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Configuring the TIBCO Rendezvous Agent Process

To configure the TIBCO Rendezvous Agent Process (rva) to import and export message subjects:

1. Open a browser to the rva http interface address. If you do not know the rva http interface, the default is

        http://host:7680/

where host is the name of your machine. If this does not work, contact your TIBCO Rendezvous system administrator. Your setup may be running with a different http interface or you may not have permission to change the rva settings. The browser interface should look similar to the following:

2. Click on the subjects link. The screen should look similar to the following:

Type the message subject into the Add Subject field. The subject to add for the data simulator is

    orders.STATUS.*

3. Click on the button marked Add for Import and Export.

Once rva has been setup, the subject configuration information will be stored in the specified settings file. See the TIBCO Rendezvous documentation for more information regarding configuring rva.  


 
SL, SL-GMS, GMS, RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2012 Sherrill-Lubinski Corporation. All Rights Reserved.

 

JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

 

Third Party Notice Requirements