Filter
Top Products
MetadataConnection
The MetadataConnection object represents the connection to EIS or EIS repository.
This interface is implemented by the Adapter Foundation Classes only and does
not require any implementation from discovery service instances.
MetadataConnection uses the managed connection factory to create the connection
to the EIS. The configuration properties specified by the user are mapped to the
managed connection factory. AgetConnection() call is placed to obtain an EIS
connection.
Besides the physical connection it represents, MetadataConnection also has a handle
to the ConnectionType and OutboundConnectionConfiguration.
Once the connection is established, enterprise metadata discovery makes the
request to get the MetadataTree from the MetadataDiscovery implementation. If
there is a filter PropertyGroup specified at the MetadataTree you are prompted
enter those properties.
MetadataTree model:
The enterprise metadata discovery tool displays a MetadataTree model that
represents an object structure in the EIS. The display also reflects your enterprise
metadata discovery service implementation and filters that you can apply to the
MetadataTree model to improve usability.
The structure of the MetadataTree reflects not only the EIS business data but also
your enterprise metadata discovery implementation. For example, one
implementation might display the properties of the nodes or MetadataObject in the
MetadataTree model. Another implementation might display function parameters
as nodes in the MetadataTree model.
IBM WebSphere recommends displaying the leaf-level properties in the model only
if there is an advantage to doing so. In most cases, simple properties or function
parameters should not be added as nodes in the tree. The description of the node
representing the object or the function should provide information about the node.
For example, in an EIS where function overloading is possible, the function
description for the node should show enough parameter information to make the
right import selection.
To improve usability, provide filters on MetadataTree models as applicable. For
example, if the EIS contains many objects and is difficult to search, a filter might
help. A best practice recommendation is to provide an option of inbound or
outbound as a filter property for the MetadataTree. Doing so restricts the objects
selected to one type for each discovery service pass. Where the same objects are
used for inbound and outbound, skip this property and define it after choosing
objects for MetadataSelection.
For more information, see the WBIMetadataTreeImpl in Javadocs.
MetadataSelection:
MetadataSelection is a container that holds objects and properties that you select
to guide or filter enterprise metadata discovery.
130 WebSphere Adapters: WebSphere Adapter Toolkit User Guide