Rendezvous Request Reply
Rendezvous Request Reply is an asynchronous activity that publishes a TIBCO Rendezvous® message on the specified subject with the specified message content. A reply to the message on the specified reply subject and with the specified reply message content is received by this activity. This activity waits for a reply on the reply subject and outputs the content of the reply. This activity uses the INBOX mechanism to ensure that reply messages are received only by the process that sent the request.
General
The General tab has the following fields.
| Field | Literal Value/Process Property/Module Property | Description |
|---|---|---|
| Name | None | The name to be displayed as the label for the activity in the process. |
| Subject | Yes | The subject on which to publish the Rendezvous® message. You can override this value by specifying a subject on the Input tab. |
| Transport | Yes | The Rendezvous transport parameters. These are specified as a Rendezvous Transport shared configuration resource. |
| Request Timeout (msec) | Yes | The length of time to wait (in milliseconds) for a reply to the Rendezvous message. If no reply is received in the specified time limit, it returns an error. |
| Pre-register Listener | Yes | When using TIBCO Rendezvous Certified Messaging (RVCM), this field specifies the cmnames of the RVCM subscribers. The sender can preregister with any expected listeners. If multiple cmnames are specified, separate each cmname with a comma.
For more information about RVCM, see the TIBCO Rendezvous® documentation . |
| XML Format | None | If this check box selected, the body of the Rendezvous® request and reply messages is sent as a single field named "xml". This field is a byte array containing the body of the message. |
| Need Output Filtration | None | Specifies that only fields in the reply message that match the name and datatype of the schema elements specified on the
Output Editor tab should be processed. Any elements that do not match the specified schema are ignored and not included in this activity’s output.
This is useful if you need only a subset of the fields of a reply message. Any unnecessary fields are not included in the activity output. This saves memory, and consequently improves performance. |
| XML Compliant Field Names for Input | None | Specifies whether the field names of the input message should be altered so that they comply with XML naming rules. Only field names that do not comply with XML naming rules are altered when this check box is not selected.
Select this check box if you want the field names to be unaltered. |
| XML Compliant Field Names for Output | None | Specifies whether the field names of the outgoing message should be altered so that they comply with XML naming rules. Only field names that do not comply with XML naming rules are altered when this check box is not selected.
Select this check box if you want the field names to be unaltered. |
Input Editor
In the Input Editor tab you can define custom schemas for the body of the outgoing Rendezvous request and body of the incoming Rendezvous response.
Output Editor
In the Output Editor tab you can define custom schemas for the body of the outgoing Rendezvous request and body of the incoming Rendezvous response.
Input
The following is the input for this activity.
| Input Item | Datatype | Description |
|---|---|---|
| subject | string | The subject of the Rendezvous message. |
| replySubject | string | The reply subject for this activity. |
| timeout | number | The amount of time to wait (in milliseconds) for a reply to the Rendezvous message. If no reply is received in the given time limit, an error is returned. |
Output
The following is the output of this activity.
| Output Item | Datatype | Description |
|---|---|---|
| replySubject | string | A reply message can optionally have a reply subject, presumably so that the two applications can communicate with further messages. This element contains the reply subject set on the reply message, if one is set. If no reply subject is set on the reply message, this element is not populated. |