![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Adapters are configured in TIBCO Designer using the Generic Adapter Configuration resource and its dependent resources.Adapter configuration consists of the configuration of the adapter itself and the creation and definitions of metadata schemas.Basic adapter configuration, which includes startup state, session parameters, adapter service definition, tracing information, and so on, is the configuration of the adapter itself.Adapters can provide Publication Service, Subscription Service, Request-Response Service, and Request-Response Invocation Service.Any configuration that the adapter developers need in addition to the standard configuration is custom configuration. For example, database connection account information.A low-level plug-in that allows the transformation of message content before or after it is sent out on the network.The TIBCO Designer AESchemas palette can be used for the schema (metadata) configuration. With the schema palette, developers define the data that the adapter sends or receives and also the parameters and exceptions of the operations a client/server type of adapter uses. Developers can also generate schema in AEXML format and import them into the repository or into TIBCO Designer. For more information, see TIBCO Designer Palette Reference.Examples of how to use TIBCO Designer to perform adapter configuration are included in the TIBCO Adapter SDK Programmers Guide. It is recommended that first time Adapter SDK developers work through the examples to familiarize themselves with Designer.Metadata describes application data. Metadata isolates the data description from the application data and allows data to be exchanged independent of languages and platforms.
TIBCO Designer defines metadata classes, attributes, and other items at design time. There are two types of metadata:These metadata are defined with class, union, or association resources and have scalar-type attributes or complex-type attributes (which can be another class, union, or association).These metadata have a name, a method or methods with a return class (if any), and parameters (their name, class and the direction: in, out, or both), as well as any exceptions the operation raises. These metadata are used by SDK Operations classes.By default, metadata is loaded upon startup. The SDK stores the metadata information using a class registry and associated classes.Figure 7 Metadata Creation and UsageMetadata is used in a similar way to a hardcopy specification document that is shared among developers. Instead of delivering a hardcopy document for each developer and updating and distributing that document periodically, applications access metadata through the adapter instance description stored in a repository. Because metadata is managed by TIBCO Administrator, changes in the data description are immediately picked up by all applications or application components.By default, a number of global variables are defined for TIBCO Designer projects. These global variables set the values for parameters such as session, subject, and so on.It is recommended that these variables be kept and used because they provide a flexible way of changing the adapter configuration at runtime without having to load, reconfigure, and save the adapter configuration instance each time.However, depending on the requirements, it may not be desirable to change an adapter configuration at runtime. In this case, fixed values can be set.
• Multi-file project—The preferred format during development. Allows multiple developers to collaborate with a version control system.
• Single-file repository project—A single .dat file.
• Server-based repository project—A server-based .dat file, which can be managed by a TIBCO Administrator administration server.See TIBCO Administrator Server Configuration Guide for more information.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |