Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Adapter Program Elements : Transports, Wire Formats, and Message Formats

Transports, Wire Formats, and Message Formats
This section discusses transports, wire formats, and message formats. Understanding what each term means, and what the available options are, is essential for proper configuration and programming of the adapter.
Adapter events are created by an event source such as an MTimer or an MSubscriber (see Event Model). With each event, data are either sent or received using one of the supported transports and wire formats. You must specify the transport, quality of service, and wire format when configuring the adapter elements.
Transports
Both TIBCO Rendezvous and TIBCO Enterprise Message Service are supported. Each transport supports different qualities of service:
TIBCO Rendezvous supports reliable, certified, and transactional messages. In addition, you can use TIBCO Rendezvous to support queues.
SDK C++ API calls the EMS C API to create lookup context and other EMS functionalities as there is no concept of tibjmsnaming in the EMS C API. The concept of tibjmsnaming is used only in Java for JNDI implementation.
To use tibjmsnaming, specify the TCP notion in Designer or SDK, and specify tibjmsnaming in the factories.conf file, which is queried by the EMS server.
In the factories.conf file, specify the URL of [TopicConnectionFactory] or [QueueConnectionFactory] as follows:
Wire Formats
Three wire formats are supported:
rvMsg (standard TIBCO Rendezvous Message)
aeRvMsg (ActiveEnterprise Messages, which includes control information)
aeXml (standard XML representation)
TIBCO Rendezvous supports all three wire formats, while TIBCO Enterprise Message Service supports only aeXml. See TIBCO Adapter Wire Formats for more information.
Message Formats
The combination of a transport and a wire format is called a message format. A message format is a C++ enumerated type or a Java interface that can be passed, for example, when constructing an MTree class. The following message formats are available.
Table 18 Message Formats
rvMsg using TIBCO Rendezvous transport
aeRvMsg using TIBCO Rendezvous transport
aeXml message using TIBCO Rendezvous transport
aeXml message using JMS transport

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved