Rendezvous Subscriber

Rendezvous Subscriber is a process starter activity that creates a process when a TIBCO Rendezvous® message on the specified subject is received.

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 listen for the Rendezvous® message.
Transport Literal Value/Module Property The Rendezvous transport parameters. These are specified as a Rendezvous Transport shared resource.
XML Format None If you select this check box, the body of the incoming Rendezvous message is a single field named "xml". This field is a byte array containing the body of the message.

TIBCO ActiveMatrix BusinessWorks™ automatically deserializes the xml field and represents the message as a schema tree in this activity’s output.

Note: When selected, the Need Input Filteration check box gets disabled.
Need Output Filteration None Specifies that only fields 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 an incoming message. Any unnecessary fields are not included in the activity output. This saves memory, and consequently improves the performance.

Note: This option is valid, only when the XML Format check box is not selected. Do not select this check box when the XML Format check box is also selected.
XML Compliant Field Names None Specifies whether the field names of the incoming 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 check box is not selected. When selected, field names are left unaltered.
Raw-RV-Object Mode None Selecting this check box disables XML Format, Needs Output Filtration, and XML-Compliant Field Names check boxes.

Select this check box to specify that the body of the RV message is the output as a Java object reference. A subsequent Java Invoke activity in the process can accept the reference as an input parameter and then construct the RV message from the object. To use the Java object, the Java Invoke activity must cast the object reference as a byte array. For example:

TibrvMsg tibrvMsg = new

TibrvMsg ((byte[])in_var_1);

Where in_var_1 is the input parameter for the Java Invoke activity that is mapped to the object reference of the object containing the Rendezvous message.

Description

Provide a short description for the activity.

Advanced

The Advanced tab has the following fields.

Field Description
Sequence Key This field can contain an XPath expression that specifies which processes should run in a sequence. Process instances with sequence keys that evaluate to the same value, are executed sequentially in the sequence the process instance was created.
Custom Job Id This field can contain an XPath expression that specifies a custom job ID for the process instance.

Output Editor

Use the Output Editor tab to define a custom schema for the body of the Rendezvous® message.

Conversations

You can initiate the conversation here. Click the Add New Conversation button to initiate multiple conversations.

For more information about conversations, see Application Development.

Output

The following is the output of the activity.

Output Item Datatype Description
sendSubject string The subject of the received message.
replySubject string The reply subject of the Rendezvous® message.