![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO Adapter SDK programming is discussed in detail in TIBCO Adapter SDK Programmer’s Guide. Reference documentation for C++ and Java API is also included in the Adapter SDK documentation set.This section gives an overview of SDK features that facilitate the development of custom adapter programs.The SDK abstracts transport details and many other things a developer usually needs to manage when writing applications that communicate with each other across networks.Default behaviors for multiple interaction scenarios are provided, such as default message acknowledgement behavior. These behaviors can be customized when needed.Tracing, tracking, TIBCO Hawk methods, NT Service wrapper, and other classes or small packaged modules are available.Configuration is separated from programming, application data is separated from metadata, and so on. These kinds of separation allow easy customizations. For example, the configuration data can be changed without changing the program. The metadata can also be changed to affect the data the adapter sends or receives.
• The application manager handles the initialization and shutdown of an adapter and provides the glue logic that holds all components together. As part of the initialization, it loads the configuration data (sessions, endpoints, and so on) and metadata into memory. It also sets up tracing and TIBCO Hawk management. Applications can customize initialization and shutdown.
− Endpoints send or receive the data. They are the publishers, subscribers, clients, and servers in the custom adapter. They are configured to use a specific message format, which packages the data going over the network.
− Each endpoint is associated with a session. Sessions (or the corresponding services) can be configured to use TIBCO Rendezvous or TIBCO Enterprise for JMS. Different quality of service options are available. A session is used to communicate with the source or target application.
• The program is executed based on an event model using event sources (which are the endpoints that receive or send data), events, and event listeners. Event listeners are created programmatically to correspond to endpoints.
− An MTree class represents hierarchical data in the wire format used by an endpoint. On the network, data are always represented as MTrees.
− An MInstance class represents data constrained by metadata. In addition to MInstance, the SDK supports other classes such as MSequence or MAssociation.Metadata can also be specified in TIBCO Designer. Upon startup, the application manager creates appropriate metadata description classes that can then be accessed when creating instances.At runtime the adapter creates instances (MInstance) as defined by the metadata and populates the MInstance attributes with object data from the target application for publishing or responding to request-response invocation.On the receiving side, a subscriber adapter converts the incoming message back to an instance through de-serialization, which also validates the message against expected metadata definitions.Figure 8 Data at Runtime
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |