tibrvTransport_Create()

Function

Declaration

tibrv_status tibrvTransport_Create(
    tibrvTransport*    transport,
    const char*        service,
    const char*        network,
    const char*        daemon);
tibrv_status tibrvTransport_CreateLicensed(
    tibrvTransport*    transport,
    const char*        service,
    const char*        network,
    const char*        daemon,
    const char*        licenseTicket);

Purpose

Create a network transport.

Remarks

These calls create only network transports. The call tibrv_Open() automatically creates the intra-process transport; programs cannot create additional intra-process transports.


Parameter	Description
`transport`	The program supplies a location, and the function stores the new transport in that location. The transport remains valid until the program explicitly destroys it.
`service`	The Rendezvous daemon divides the network into logical partitions. Each network transport communicates on a single service; a transport can communicate only with other transports on the same service. To communicate over 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 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 in TIBCO Rendezvous Concepts. `NULL` specifies the primary network interface for the host computer.
`daemon`	The daemon parameter instructs `tibrvTransport_Create()` about how and where to find the Rendezvous daemon and establish communication. For details, see Daemon Parameter in TIBCO Rendezvous Concepts. You can specify a daemon on a remote computer. For details, see Remote Daemon in TIBCO Rendezvous Concepts. If you specify a secure daemon, this string must be identical to as the `daemonName` argument of tibrvSecureDaemon_SetDaemonCert(). See also, Secure Daemon 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.

Connecting to the Rendezvous Daemon

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

If a Rendezvous daemon process with a corresponding daemon parameter is already running, tibrvTransport_Create() connects to it.

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

If tibrvTransport_Create() cannot connect to the Rendezvous daemon, it returns the status code TIBRV_DAEMON_NOT_CONNECTED, and does not create a transport object.

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().

Destroying Transports

Programs must explicitly destroy each transport object. Destroying a transport object invalidates subsequent send calls on that transport, invalidates any listeners using that transport, and frees its storage. See tibrvTransport_Destroy().

Attempting to use a destroyed transport in any way is an error.