Copyright © Cloud Software Group, Inc. All Rights Reserved

Rendezvous Subscriber

Process Starter

The Rendezvous Subscriber process starter creates a process when a TIBCO Rendezvous message on the given subject is received.

Configuration

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 listen for the TIBCO Rendezvous message.
Transport	Yes	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.
XML Format	No	If checked, the body of the incoming TIBCO Rendezvous message is expected to be 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.
Needs Output Validation	No	Specifies that you would like the incoming message to be validated against the schema specified on Output Editor tab. An error is returned if an incoming message does not match the specified schema. Validation does affect system performance, and you may want to uncheck this field to handle incoming messages more quickly. If you uncheck this field, no validation is performed and any incoming message that does not match the specified schema is processed. You should only uncheck this field if you can guarantee that incoming messages conform to the expected schema.
Needs Output Filtration	No	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 can save memory, and consequently improve performance. Note: This option is only valid when the XML Format field is unchecked. Do not select this check box when the XML Format field is also selected.
XML-Compliant Field Names	No	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 field is unchecked. When checked, field names are left unaltered.
Raw-RV-Object Mode	No	Checking this field disables the XML Format, Needs Output Validation, Needs Output Filtration, and XML-Compliant Field Names fields. Specifies that the body of the RV message should be output as a Java object reference. A subsequent Java Code activity in the process definition can accept the reference as an input parameter and then construct the RV message from the object. To use the Java object, the Java code 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 Code activity that is mapped to the object reference of the object containing the RV message.

Misc

The Misc tab contains the following fields:

Field	Description
Sequencing Key	This field can contain an XPath expression that specifies which processes should run in order. Process instances with sequencing keys that evaluate to the same value will be executed sequentially in the order the process instance was created. See TIBCO ActiveMatrix BusinessWorks Process Design for more information about controlling the execution order of process instances and about XPath expressions.
Custom Id	This field can contain an XPath expression that specifies a custom ID for the process instance. This ID is displayed in the View Service dialog of TIBCO Administrator, and it is also available in the $_processContext process variable.

Output Editor

The Output Editor tab allows you to define a custom schema for the body of the TIBCO Rendezvous message. See Appendix A, Specifying Data Schema for a complete description of using the Output Editor tab.

Output

The output for the activity is the following.

Output Item	Datatype	Description
sendSubject	string	The subject of the received message.
replySubject	string	The reply subject of the TIBCO Rendezvous message.
certifiedSender	string	This element is only available when RVCM transports are used. This element contains the CM name of the message sender.
certifiedSequenceNumber	integer	This element is only available when RVCM transports are used. This element contains the sequence number of the message.
body	complex	The body of the TIBCO Rendezvous message. If the Raw-RV-Object Mode field is checked on the Configuration tab, the body is output as an object reference.

Copyright © Cloud Software Group, Inc. All Rights Reserved