Rendezvous Transport
Rendezvous Transport resource describes a TIBCO Rendezvous ® transport. This resource is used when specifying activities from the Rendezvous palette. For more information about specifying these fields, see the TIBCO Rendezvous documentation.
Configuration
The Configuration tab has the following fields.
| Field | Literal Value/Process Property/Module Property | Description |
|---|---|---|
| Name | No | Resource label. |
| Description | No | Short description of the shared resource. |
| Daemon | Yes | If the Rendezvous daemon is running on the same machine as the process engine: Daemon is not specified.
If the Rendezvous daemon is running on a different machine than the process engine: Host name followed by the socket number. For example: ssl:acct:5785 |
| Network | Yes | Host name, IP address, network name, or interface name.
For example: ;224.34.103.4 |
| Service | Yes | TIBCO Rendezvous service name or port number:
For example: <service name> <port number> |
| SSL | No | Use Secure Sockets Layer (SSL) when communicating with the TIBCO Rendezvous daemon. Select this field to enable the Configure SSL button.
For more information, see Configure SSL Button. |
Configure SSL Button
The Configure SSL button allows you to configure the SSL parameters for communicating with the TIBCO Rendezvous daemon. For more information about how SSL is configured for TIBCO Rendezvous daemons and clients, see the TIBCO Rendezvous documentation .
The SSL Configuration for TIBCO RV dialog tab has the following fields:
| Field | Description |
|---|---|
| Daemon Certificate | File containing one or more certificates from trusted daemon certificate authorities. Select this field to connect to a trusted (non-rogue) daemon and retrieve a daemon certificate.
Once a certificate is retrieved, select a project folder in the TIBCO Rendezvous administration interface and choose Tools>Trusted Certificates>Import Into PEM Format to import the certificate. Alternatively, instead of importing or embedding them, configure certificates at deployment time by declaring a global variable and setting its absolute path to a certificate in PEM format. To learn more about retrieving, importing, and configuring daemon certificates using the administration interface, see the TIBCO Rendezvous documentation. |
| Identity | Identity resource used to authenticate the TIBCO Rendezvous daemon.
Click Browse to select an identity resource from a list of resources whose Type field is set to Identity File or Username/Password. |
| Field | Global Variable? | Description |
|---|---|---|
| RV Type | No | Type of Rendezvous connection (reliable (standard RV transport), certified (RVCM), or Distributed Queue (RVCMQ)).
The fields on the Advanced tab correspond to the value selected for this field. |
| Certified Transport | ||
| CM Name | Yes | Name of the delivery-tracking session, in the same format as TIBCO Rendezvous subject names. |
| Ledger File | Yes | Name and location of the persistent ledger file that tracks certified messages. If not specified, the certified message ledger is kept in process memory only. |
| Sync Ledger File | Yes | Specifies whether to keep the ledger file synchronous with the current messages. |
| Relay Agent | Yes | Name of the relay agent to use. Relay agents are useful when clients are disconnected from the network from time to time. The relay agents store inbound certified messages and labeled messages (and other messages related to certified delivery features) on behalf of their disconnected client programs. When a client is connected, the relay agent receives inbound messages immediately. |
| Require Old Message | Yes | Select this check box if you want to require the retention of messages for which delivery has not been confirmed. These messages are be resent. |
| Message Timeout (sec) | Yes | Time limit for certified message delivery. |
| Distributed Queue Transport | ||
| CMQ Name | Yes | Name of the distributed queue, in the same format as TIBCO Rendezvous subject names. |
| Worker Weight | Yes | Weight of the worker (this pertains to the worker processing queue requests, not to BusinessWorks process engines). Relative worker weights assist the scheduler in assigning tasks. When the scheduler receives a task, it assigns the task to the available worker with the greatest worker weight. |
| Worker Tasks | Yes | Sets the task capacity for the worker (this pertains to the worker processing queue requests, not to BusinessWorks process engines). Task capacity is the maximum number of tasks that a worker can accept. When the number of accepted tasks reaches this maximum, the worker cannot accept additional tasks until it completes one or more of them. |
| Worker Complete Time | Yes | The amount of time the scheduler waits for a worker process to complete. If the worker process does not completethe process in the specified time, the scheduler reassigns the message to another worker. |
| Scheduler Weight | Yes | Weight represents the ability of this member to fulfill the role of scheduler, relative to other members with the same name. Cooperating distributed queue transports use relative scheduler weight values to elect one transport as the scheduler. Members with higher scheduler weight take precedence. Acceptable values range from 1 to 65535. |
| Scheduler Heartbeat (sec) | Yes | Interval in which scheduler sends heartbeat messages. All members with the same name must specify the same value for this parameter. The value must be strictly positive. |
| Scheduler Activation (sec) | Yes | Maximum amount of time that the heartbeat signal from the scheduler is silent before the member with the greatest scheduler weight becomes the new scheduler. All members with the same name must specify the same value for this parameter. The value must be positive. |