Using connectors
Connectors can be created through the following clients:
The code sample below uses the Asset Consumer OMAS client to retrieve a list of assets from a metadata access server and then create a connector to each one using the getConnectorToAsset()
method.
This method assumes that there is a connection object with a connector type and endpoint linked to the requested asset in the metadata repository.
An exception is thrown if an asset does not have a connection.
In the sample, the connector returned by the Asset Consumer OMAS client is then cast to the CSVFileConnector
. Assets that are not CSV files will have a different connector implementation and so the casting to CSVFileConnector
also results in an exception.
Assets that do not have a CSVFileConnector
are ignored. The result is that the sample method returns a connector for the first CSV file asset retrieved from the metadata repository.
Example: connecting to CSV files using Asset Consumer OMAS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
|
Connecting to assets with different levels of security¶
It is possible that an asset can have multiple connections, each with different levels of security access encoded. Egeria is able to determine which one to use by calling the validateUserForAssetConnectionList()
method of the Server Security Metadata Connector.
Other links to the connection¶
Open metadata is a connected network (graph) of information. The connector type and endpoint that a connection object links to are typically shared with many connections. This creates some interesting insight.
For example, there is typically one connector type for each connector implementation. By retrieving the relationships from the connector type to the connections, it is possible to see the extent to which the connector is used.
Connector types¶
The connector types for Egeria's data store connectors are available in an open metadata archive called DataStoreConnectorTypes.json
that can be loaded into the server. This approach can be used for all of your connector implementations to create the connector type objects in our metadata repository. See the open-connector-archives for more detail.
Connector categories¶
By default, connector implementations are assume to support the OCF. However, many vendor platforms have their own connector frameworks. The ConnectorCategory allows equivalent connector types from different connector frameworks to be gathered together so that the connector type from a connection can be swapped for an equivalent connector type for the locally supported connector framework.
Endpoints¶
The endpoints are typically linked to the software server that is called by the connector. By navigating from the Endpoint
to the linked connections it is possible to trace the callers to the software server.
Software servers and endpoints are set up through the IT Infrastructure OMAS.
Further information
The connector catalog lists the connectors provided by the Egeria community.