IBM WebSphere Adapters User Manual page 134

for multiple back-end EIS assets. IBM WebSphere recommends a single
adapterType for each enterprise metadata discovery implementation.
The following information must be provided for this class by a discovery service
implementation.
v ID (for example, PeopleSoft)
v Description (for example, PeopleSoft JCA Adapter)
v Display name (for example, PeopleSoft Adapter)
v Vendor (for example, IBM)
v Version (for example, 6.2)
v List of OutboundConnectionTypes - Lists the outbound connection types an
v List of InboundConnectionTypes - List of inbound connection types supported
Metadata discovery connection type
You must specify connection type values for the enterprise metadata discovery
service. The connection type includes connection configuration instance
information for outbound and inbound directions.
ConnectionType is a factory for ConnectionConfiguration instances. The enterprise
metadata discovery tool uses the instances to create actual and persistent
connections. The connection can be inbound or outbound and is unique within the
AdapterType.
OutboundConnectionType
The enterprise metadata discovery service uses the OutboundConnectionType
property to create an outbound service description. The mapping of connection
type to adapter is driven by the number of managed connection factories that are
supported by the adapter. If the adapter uses a different connection than one
provided by a managed connection factory, this list must include the additional
connection types. The connection types displayed in the tool for selection are only
the ones that can be used to perform metadata discovery. Such connections are
marked as true for isSupportedInMetadataDiscovery. For all connection types that
cannot be used to perform discovery, set isSupportedInMetadataDiscovery to
false.
IBM WebSphere recommends implementing a connectionType for metadata that is
separate from that for run time. The metadata connectionType must contain
properties needed to perform the metadata discovery only. The runtime connection
type should have properties for the resource adapter and the managed connection
factory. The discovery service should attempt to reuse the properties from the
metadata connectionType wherever possible. Candidates for reuse include the
username and password properties. A utility class, EMDUtil, provides methods to
128
WebSphere Adapters: WebSphere Adapter Toolkit User Guide
adapter can support. A single adapter might support multiple connection types.
The mapping of connection type to adapter is driven by the number of managed
connection factories that are supported by the adapter. If the adapter uses a
different connection than one provided by a managed connection factory, this list
must include the additional connection types. The connection types displayed in
the tool for selection are only the ones that can be used to perform metadata
discovery. Such connections are marked as true for
isSupportedInMetadataService. For all connection types that cannot be used to
perform discovery, set isSupportedInMetadataService to false.
by an adapter. The inbound connections map to the Activation Specifications
supported by an adapter.