Send Rendezvous Request

The Send Rendezvous Request activity publishes a TIBCO Rendezvous message on the given subject with the given message content, and it expects a reply to the message on the given reply subject and with the given reply message content. 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.

The Configuration tab has the following fields.

Field	Global Var?	Description
Name	No	The name to appear as the label for the activity in the process definition.
Description	No	Short description of the activity.
Subject	Yes	The subject on which to publish the TIBCO Rendezvous message. You can override this value by specifying a subject on the Input tab.
Transport	No	The TIBCO Rendezvous transport parameters. These are specified as a Rendezvous Transport shared configuration resource. See Rendezvous Transport for more information about shared configuration resources.
Request Timeout (msec)	Yes	The amount of time to wait (in milliseconds) for a reply to the TIBCO Rendezvous message. If no reply is received in the given time limit, an error is returned.
Pre-register Listener	Yes	When using TIBCO Rendezvous Certified Messaging (RVCM), this field specifies the cmname(s) of the RVCM subscriber(s). This allows the sender to pre-register with any expected listeners. If multiple cmnames are specified, separate each cmname with a comma. See the TIBCO Rendezvous documentation for more information about RVCM.
XML Format	No	If checked, the bodies of the TIBCO Rendezvous request and reply messages are sent as a single field named "xml". This field is a byte array containing the body of the message. TIBCO ActiveMatrix BusinessWorks automatically deserializes the reply message and represents the data of the message as a schema tree based on the schema specified in the Output Editor tab.
Needs Output Validation	No	Specifies that you would like the reply message to be validated against the schema specified on Output Editor tab. An error is returned if a reply message does not match the specified schema. Validation does affect system performance, and you may want to uncheck this field to handle reply messages more quickly. If you uncheck this field, no validation is performed and any reply message that does not match the specified schema is processed. You should only uncheck this field if you can guarantee that reply messages conform to the expected schema.
Needs Output Filtration	No	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 can save memory, and consequently improve performance. Note: This option is only valid when the XML Format field is unchecked. Do not check this check box when the XML Format field is also checked.
XML-Compliant Field Names	No	Specifies whether the field names of the outgoing message should be altered so that they comply with XML and ActiveEnterprise naming rules. Only field names that do not comply with XML and ActiveEnterprise naming rules are altered when this field is unchecked. When checked, field names are left unaltered.

The name to appear as the label for the activity in the process definition.

Description

Short description of the activity.

Subject

Yes

The subject on which to publish the TIBCO Rendezvous message. You can override this value by specifying a subject on the Input tab.

Transport

The TIBCO Rendezvous transport parameters. These are specified as a Rendezvous Transport shared configuration resource. See Rendezvous Transport for more information about shared configuration resources.

Request Timeout (msec)

Yes

The amount of time to wait (in milliseconds) for a reply to the TIBCO Rendezvous message. If no reply is received in the given time limit, an error is returned.

Pre-register Listener

Yes

When using TIBCO Rendezvous Certified Messaging (RVCM), this field specifies the cmname(s) of the RVCM subscriber(s). This allows the sender to pre-register with any expected listeners. If multiple cmnames are specified, separate each cmname with a comma.

See the TIBCO Rendezvous documentation for more information about RVCM.

XML Format

If checked, the bodies of the TIBCO Rendezvous request and reply messages are sent as a single field named "xml". This field is a byte array containing the body of the message.

TIBCO ActiveMatrix BusinessWorks automatically deserializes the reply message and represents the data of the message as a schema tree based on the schema specified in the Output Editor tab.

Needs Output Validation

Specifies that you would like the reply message to be validated against the schema specified on Output Editor tab. An error is returned if a reply message does not match the specified schema.

Validation does affect system performance, and you may want to uncheck this field to handle reply messages more quickly. If you uncheck this field, no validation is performed and any reply message that does not match the specified schema is processed.

You should only uncheck this field if you can guarantee that reply messages conform to the expected schema.

Needs Output Filtration

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 can save memory, and consequently improve performance.

Note: This option is only valid when the XML Format field is unchecked. Do not check this check box when the XML Format field is also checked.

XML-Compliant Field Names

Specifies whether the field names of the outgoing message should be altered so that they comply with XML and ActiveEnterprise naming rules. Only field names that do not comply with XML and ActiveEnterprise naming rules are altered when this field is unchecked. When checked, field names are left unaltered.

The Input Editor and Output Editor tabs allow you to define custom schemas for the body of the outgoing TIBCO Rendezvous request and body of the incoming TIBCO Rendezvous response. See Appendix A, Specifying Data Schema for a complete description of using the Input/Output Editor tab.

See TIBCO ActiveMatrix BusinessWorks Process Design for more information about mapping and transforming input data.

The input for the activity is the following.

Input Item	Datatype	Description
subject	string	The subject of the TIBCO Rendezvous message.
body	complex	The body of the TIBCO Rendezvous message.
replySubject	string	The reply subject for this activity. Note: The reply messages may not be received by the correct job if more than one job has the same reply subject (for example, if a constant is specified in this field). Use the Publish Rendezvous Message and Wait for Rendezvous message instead if you want to receive replies on a single subject.
timeout	number	The amount of time to wait (in milliseconds) for a reply to the TIBCO Rendezvous message. If no reply is received in the given time limit, an error is returned.

The subject of the TIBCO Rendezvous message.

body

complex

The body of the TIBCO Rendezvous message.

replySubject

string

The reply subject for this activity.

Note: The reply messages may not be received by the correct job if more than one job has the same reply subject (for example, if a constant is specified in this field). Use the Publish Rendezvous Message and Wait for Rendezvous message instead if you want to receive replies on a single subject.

timeout

number

The amount of time to wait (in milliseconds) for a reply to the TIBCO Rendezvous message. If no reply is received in the given time limit, an error is returned.

The output for the activity is the following.

Output Item	Datatype	Description
replyMessageReplySubject	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.
body	complex	The body of the TIBCO Rendezvous reply message.

Output Item

Datatype

Description

replyMessageReplySubject

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.

body

complex

The body of the TIBCO Rendezvous reply message.

The Error Output tab lists the possible exceptions that can be thrown by this activity. See TIBCO ActiveMatrix BusinessWorks Error Codes for more information about error codes and corrective action to take.

Exception	Thrown When...
TransportException	The transport cannot be created.
SerializationException	The message cannot be serialized.
RVPluginException	An error occurred when sending the message.
ActivityTimedOutException	A timeout has been reached.

Exception

Thrown When...

TransportException

The transport cannot be created.

SerializationException

The message cannot be serialized.

RVPluginException

An error occurred when sending the message.

ActivityTimedOutException

A timeout has been reached.