Copyright © Cloud Software Group, Inc. All Rights Reserved

Field Names In Messages

A TIBCO Rendezvous message can contain field names that are not compliant with XML or ActiveEnterprise naming rules. For example, XML element names cannot begin with a number, nor can they contain special characters, such as # or ^. When activities in the TIBCO Rendezvous palette send or receive messages, element names in the input or output schemas for the activity must comply with XML and ActiveEnterprise naming rules. Any elements in referenced schemas in the input or output schemas are automatically altered so that they comply with XML and ActiveEnterprise naming rules. The XML-Compliant Field Names field allows you to handle incoming or outgoing messages when the field names are not valid XML or ActiveEnterprise names.

When the XML-Compliant Field Names field is unchecked, any field names in incoming or outgoing messages that do not comply with XML or ActiveEnterprise naming rules are altered so that they comply with the rules. When the field is checked, field names in the message are left unaltered.

When publishing a message, unchecking the XML-Compliant Field names field ensures that field names in the message sent over the transport to the receiving application are altered when necessary to comply with XML or ActiveEnterprise naming rules. Checking the field allows you to send the message with the original field names intact; no alterations are made to the field names. This is useful in the case where you reference a schema in the Input Editor that contains invalid XML or ActiveEnterprise names (such as a TIBCO ActiveEnterprise schema that contains special characters). The receiving application will receive the message with the original field names, if the XML-Compliant Field Names field is unchecked.

When receiving a message, unchecking the XML-Compliant Field Names field ensures that field names in the incoming message are altered to comply with XML and ActiveEnterprise naming rules. If the message contains fields that do not comply to XML and ActiveEnterprise naming rules, the output schema of the subscriber activity must specify the correct altered name in order to match the altered name of the field in the incoming message. See the description of the ae2xsd utility in the TIBCO Runtime Agent Administrator’s Guide for more information about how to convert a TIBCO ActiveEnterprise schema into a valid XSD. Using this utility will allow you to see how field names will be altered to comply with XML and ActiveEnterprise naming rules. Unchecking the field leaves the field names of the message intact.

Unchecking the XML-Compliant Field Names field involves extra processing of incoming and outgoing messages. If you are certain that messages contain only field names that comply with XML naming rules, you can uncheck this field to improve performance.

Copyright © Cloud Software Group, Inc. All Rights Reserved