![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Adapters should not attempt to simulate the wire format by adding control information. Experience has shown that the results are not satisfactory.The term wire format refers to the message formatting convention used by the adapter. Wire formats include rvMsg, aeRvMsg, and aeXml.The term message format refers to a combination of the transport (TIBCO Enterprise Message Service or TIBCO Rendezvous) and the wire format. In ActiveEnterprise 5, the message format (not the wire format) is the critical attribute of an endpoint. See Message Formats. SDK-based adapters can only exchange data if the sending and the receiving application use the same message format.
• rvMsg wire format is used for the basic TIBCO Rendezvous message format. The SDK does not perform validation, but if you use this format, SDK adapters are compatible with non-SDK adapters. This format can be used in conjunction with TIBCO Rendezvous.For rvMsg wire format, a message of type TIBRVMSG_MSG is expected. If a sending application (for example, rvsend) publishes a simple TIBRVMSG_STRING, the SDK passes an MExceptionEvent to the event listener.
• aeRvMsg is the TIBCO ActiveEnterprise standard wire format, which provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received. This format can be used in conjunction with TIBCO Rendezvous.
• aeXml wire format can be used in conjunction with either TIBCO Rendezvous or TIBCO Enterprise Message Service.The wire formats are distinguished, in part, by the control information included when data is sent on the wire.When a custom adapter sends data in rvMsg format, no control information is included.When a custom adapter sends data in aeRvMsg or aeXml format, the following control information is generated and set by the SDK:
• ^prefixList^—List of strings for qualifying class names. This is generated and set by the SDK only if message contains a serialized MData or MData subclass.
• ^tracking^—Always a unique identifier defined by the source. Set by the source and carried forward by intermediate components.
aeXml Type Tracking identifier and any associated application information Tracking identifier and any associated application information
The ^guid^ field is obsolete.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |