Open topic with navigation

TIBCO Rendezvous® 8.7.0

# TibrvRvdTransport()

Constructor

## Declaration

    TibrvRvdTransport()
      throws TibrvException
    TibrvRvdTransport(
        java.lang.String service,
        java.lang.String network,
        java.lang.String daemon)
      throws TibrvException
    TibrvRvdTransport(
        java.lang.String service,
        java.lang.String network,
        java.lang.String daemon,
        java.lang.String licenseTicket)
      throws TibrvException

## Purpose

Create a transport that connects to a Rendezvous daemon.

## Method Forms

With no arguments, connect to `rvd` on the local computer using default values the `service`, `network`, and `daemon` parameters.

All arguments specify options for connecting to `rvd`.

## Connecting to the Rendezvous Daemon

Rendezvous daemon processes do the work of moving messages across a network. Every TibrvRvdTransport must connect to a Rendezvous daemon.

If a Rendezvous daemon process with a corresponding `daemon` parameter is already running, the transport connects to it.

If an appropriate Rendezvous local daemon is not running, the transport tries to start it. However, the transport does not attempt to start a remote daemon when none is running.

If the transport cannot connect to the Rendezvous daemon, the constructor throws an exception with the status code TibrvStatus.DAEMON_NOT_FOUND.

## Description String

As a debugging aid, we recommend setting a unique description string for each transport. Use a string that distinguishes both the application and the role of the transport within it. See TibrvTransport.setDescription().

Parameter | Description
`service` | The Rendezvous daemon divides the network into logical partitions. Each TibrvRvdTransport communicates on a single service; a transport can communicate only with other transports on the same service. To communicate on more than one service, a program must create more than one transport—one transport for each service. You can specify the service in several ways. For details, see Service Parameter on page 79 in TIBCO Rendezvous Concepts. `null` specifies the default `rendezvous` service.
`network` | Every network transport communicates with other transports over a single network interface. On computers with more than one network interface, the `network` parameter instructs the Rendezvous daemon to use a particular network for all outbound messages from this transport. To communicate over more than one network, programs must create more than one transport. You can specify the network in several ways. For details, see Network Parameter on page 82 in TIBCO Rendezvous Concepts. `null` specifies the primary network interface for the host computer.
`daemon` | The daemon parameter instructs the transport object about how and where to find the Rendezvous daemon and establish communication. For details, see Daemon Parameter on page 85 in TIBCO Rendezvous Concepts. You can specify a daemon on a remote computer. For details, see Remote Daemon on page 86 in TIBCO Rendezvous Concepts. If you specify a secure daemon, this string must be identical to as the `daemonName` argument of TibrvSdContext.setDaemonCert(). See also, Secure Daemon on page 86 in TIBCO Rendezvous Concepts. `null` specifies the default—find the local daemon on TCP socket `7500`. (This default is not valid when the local daemon is a secure daemon.)
`licenseTicket` | License tickets are no longer required. Values for this parameter are ignored.

## See Also

TibrvRvdTransport.getDaemon()

TibrvRvdTransport.getNetwork()

TibrvRvdTransport.getService()

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2023. Cloud Software Group, Inc. All Rights Reserved.