IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Adapter Toolkit > Implementing code from the IBM WebSphere Adapter Toolkit > Enterprise metadata discovery general interfaces and implementation for application adapters > Metadata discovery connection type

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.

See the WBIMetadataTreeImpl in Javadoc.

Metadata discovery connection type