Use the Endpoint Wizard to configure an endpoint connection for a TIBCO Rendezvous Certified session and transport. To access the Endpoint Wizard, from Endpoint Manager, right-click on an endpoint type and select Add Endpoint.
When using TIBCO Rendezvous Certified, be sure that the daemon is running. You can verify that it is running by checking RVD in Task Manager. You must also be sure that the application you are sending information is running. You can use a Relay Agent, which allows you to send messages even if the sender and listener are not running, between the Sender and the Listener. You must set up the Sender and Listener files as unique with the same relay agent named.
Warnings: Non-transactional transports such as TIBCO Rendezvous Certified, TIBCO Rendezvous Reliable, file, and socket do not allow for message rollback functionality so delivery is not guaranteed. Non-transactional transports can be problematic because the message is committed to the transport immediately after a get or put occurs.
Only three field types are supported for inbound messages. TIBRVMSG_STRING, TIBRVMSG_OPAQUE, and TIBRVMSG_XML.
You must configure an endpoint session before you configure the transport because the endpoint session provides information used by the transport. Session and transport keys are provided in the following tables. The third table, common transport keys, contains keys that are used by multiple messaging configurations.
TIBCO Rendezvous Certified sessions are configured to point to existing connection factories on a TIBCO Rendezvous Certified provider.
|
Session Key |
Description and Valid Values |
|
Application Description |
User defined. Identifies the application to TIBCO Rendezvous Certified components. This is the name displayed when viewing the session in a browser application interface. |
|
Daemon URL |
Identifies the connection for the TIBCO Rendezvous daemon. Warning. It you do specify a daemon, it must be running or a runtime error occurs. |
|
Ledger Name |
Identifies the name of a file-based ledger used to persist messages. If field is blank, the default is a process-based ledger. The process-based ledger persists only as long as the process is running. |
|
Ledger Synchronization |
Determines whether the ledger updates are saved immediately. FALSE (default): Data is written to persistent storage at an optimal time. TRUE: Changes are immediately written to persistent storage. |
|
Log Level |
Determines the level for logging TIBCO Rendezvous error messages to the Unwired Orchestrator .nml file: ALL (default): General error and warning information logged. WARN: Limited warning and error information logged. ERROR: Error information logged. NONE: No information logged. |
|
Outbound Message Time Limit |
Determines length of time the system waits to resend the message. The message is sent one time. If the message is not successfully sent, the system waits the designated time to send the message again. If the message cannot be successfully sent, the message is written to the ledger. A non-negative value must be entered in whole seconds. A time limit specified on a message takes precedence over the value specified here. |
|
Relay Agent Name |
User defined. Identifies the relay agent, which stores certified messages for processes that intermittently connect to the network, used for this session. A relay agent allows the transfer of messages without the sender and listener being up at the same time. The TIBCO Rendezvous relay agent daemon must be started independently. |
|
Resend Unconfirmed Messages |
Determines whether unconfirmed messages sent to a previously existing persistent correspondent with the same name should be sent again. FALSE (default): Do not resend. TRUE: Resend. |
|
Session Name |
User defined. This property is required and must be unique. |
|
Transport Network |
User defined. This is a partitioning tool for assigning networks and computers. Transport instances communicate with other transport instances within the same network. A new endpoint session must be created to communicate with each network. |
|
Transport Service |
User defined. This is another level of partitioning based on UDP or PGM services. Determines the service associated with the transport instance. The default is an empty string. |
The configuration for TIBCO Rendezvous Certified includes a series of message options that can be added to the default parameters. The following table provides a brief description of the options presented in the configuration wizard.
Refer to TIBCO Rendezvous Certified documentation for additional descriptions of the keys.
|
Session Key |
Description and Valid Values |
|
AUDIT Get Transport Name |
Identifies the name of the transport to receive a Get message. This can be used to send to another system or for audit within TIBCO Rendezvous Certified. |
|
AUDIT Put Transport Name |
Identifies the name of the transport to receive a Put message. This can be used to send to another system or for audit within TIBCO Rendezvous Certified. |
|
Custom Message Converter |
Identifies the message converter library, which is the interface between the TIBCO Rendezvous field-based message structure and transport message structures that support Payload and Out-of-Band types. Message converters transform messages to and from the Open Transport and TIBCO Rendezvous Certified representations. (Legacy key: TIBRV_TIL_MESSAGE_CONVERTER) The default designates that messages have a single field for data and a single field for options. The Field Map Converter allows you to map out of band information to multiple fields on the TIBCO Rendezvous message. The default message converter maps the following:
|
|
Default Translation Map |
Identifies the field to property translation map to use if the message does not contain an embedded field/property translation map. This property value has the following structure: propertyName1=fieldName1,propertyName2=fieldName2,propertyName3=fieldName3... . An example value for this property is: OPT_APP_GRP=tib_app,OPT_MSG_TYPE=tib_fmt,map=map. Note: This value is only valid if you have selected the Field Map Converter Factory custom message converter in a previous field. |
|
Payload Field |
Specifies the field name on the TIBCO Rendezvous message that contains the payload data. The default value is DATA. |
|
Properties Field |
User defined. Specifies the field name on the TIBCO Rendezvous message that contains the out-of-band data. Message properties in the Options field are serialized as a comma-separated list of name/value pairs, such as <name1=value,name2=value>. |
|
Property Translation Map Field
|
User defined. Identifies the name of the field in the TIBCO Rendezvous message that contains the embedded field/property translation map. The translation map field is a self-describing field that maps out-of-band information to TIBCO Rendezvous message fields. The default value is TIBRV_MSG_FIELD_MAP but an embedded field map takes precedence over the default translation map. This value works in conjunction with the Field Map converter Factor, which references the field in the message that contains a map. |
|
Session Name |
Select the user-defined endpoint session configuration to be used by this transport instance. This is similar to the session name in queueing transport applications. |
|
Subject Name |
Subject name of transported messages. Sender and listener subject names must match for a message to be transported. This is similar to the queue name in queueing transport applications. |
The information in this table identifies configuration parameters used in the Endpoint Wizard for each type of transport mechanism used. The specific key name is provided when it is used within the GUI to reference these parameters.
|
Name |
Description |
|
Blocking Timeout NNOT_TIL_GET_BLOCKING_TIMEOUT |
Amount of time in milliseconds to wait for a message to arrive before the process performs another put or get. The default is for no blocking to occur so the return is immediate. It is recommended that you set blocking timeout to 2000 (2 seconds).
|
|
Message Option Headers
|
Specifies whether a message put to the transport should contain a message option header. NNOT_HDR_EXCLUDE: Message option header not included. NNOT_HDR_IF_NEEDED: Message option header included if required by the message. NNOT_HDR_INCLUDE: Message option header included. |
Note: When running TIBCO Rendezvous transports, be sure that the TIBCO/bin directory is at the end of the path in your system variables.
For more information about transactionality, read Transactionality and Errored Business Processes.