Skip to content
In development

A component that is in development means that the Egeria community is still building the function. The code is added continuously in small pieces to help the review and socialization process. It may not run, or do something useful - it only promises not to break other function. Expect to find git issues describing the end state.

Asset Manager Open Metadata Access Service (OMAS)

Data Catalogs and Configuration Management Databases (CMDBs) are examples of asset managers. They maintain a catalog of resources for their users as assets along with catalog search and governance functions to support the maintenance and use of these resources. Such technologies might integrate with the open metadata ecosystem to receive additional information about their resources, or to distribute the information they have to other tools.

Common types of asset manager

The Asset Manager OMAS provides APIs and outbound events to support the exchange of metadata between a third party asset manager and the open metadata ecosystem.

Types of metadata supported by the Asset Manager OMAS

Asset Manager OMAS provides search and query APIs for these types of metadata elements along with the APIs to maintain their values.

  • Data Assets and schema
  • Connections, connector types and endpoints
  • IT Infrastructure (hosts, platforms, servers, storage, capabilities)
  • Processes and Lineage
  • Collaboration (comments, tags other forms of feedback)
  • Stewardship actions
  • Reference data (valid values)
  • Glossaries and external references
  • Governance definitions such as quality rules

The Asset Manager OMAS OutTopic provides a notification service for any changes to these types of elements.

Asset Manager OMAS capabilities

Integration

Asset managers often have their own integration mechanisms for both the collection of metadata and its distribution. Therefore, it may be possible to integrate calls to the Asset Manager OMAS directly into the asset manager's runtime, either via the Java client or by calls to the REST API/OutTopic. This is shown on the left of the diagram below. The alternative is to create an integration connector that uses the Catalog Integrator OMIS running in an Integration Daemon .

Integration Choices

External Identifiers

A major challenge when exchanging metadata with third party asset managers is that there is often a mismatch between the structure of the metadata in a third party asset manager and the structure of the open metadata types used by the Asset Manager OMAS.

For this reason, the Asset Manager OMAS supports the ability to associate one or more external identifiers with an open metadata instance. These external identifiers are scoped to a particular third party asset manager so that there is no confusion if two third party asset managers happen to use the same unique identifier within their repositories. Each of these external identifiers can be mapped to the appropriate open metadata instances without confusion.

There are also API calls for querying open metadata instances using external identifiers and the identifier of the third party asset manager.

Identifying your asset manager

The Asset Manager OMAS provides an API for managing an element that represents your asset manager. This is a software capability of type Catalog with the AssetManager classification attached. This element can then be linked to the assets and their properties contributed from your asset manager to show where the metadata came from and the scope of any identifiers that are mapped to these elements.

Defining an external identifier

The code snippet below shows the Asset Manager OMAS method to create a glossary term in open metadata. It includes five properties (all include glossaryTermExternalIdentifier in their name) that are used to define the external identifier for the new element. In addition, the assetManagerGUID and assetManagerName properties are used to tie the external identifier to software capability for the external identifier and mappingProperties are used to provide additional values used to guide the mapping process between the open metadata elements and the elements in the third party asset manager.

    /**
     * Create a new metadata element to represent a glossary term.
     *
     * @param userId calling user
     * @param assetManagerGUID unique identifier of software capability representing the caller
     * @param assetManagerName unique name of software capability representing the caller
     * @param glossaryGUID unique identifier of the glossary where the term is located
     * @param glossaryTermExternalIdentifier unique identifier of the glossary term in the external asset manager
     * @param glossaryTermExternalIdentifierName name of property for the external identifier in the external asset manager
     * @param glossaryTermExternalIdentifierUsage optional usage description for the external identifier when calling the external asset manager
     * @param glossaryTermExternalIdentifierSource component that issuing this request.
     * @param glossaryTermExternalIdentifierKeyPattern pattern for the external identifier within the external asset manager (default is LOCAL_KEY)
     * @param mappingProperties additional properties to help with the mapping of the elements in the external asset manager and open metadata
     * @param glossaryTermProperties properties for the glossary term
     *
     * @return unique identifier of the new metadata element for the glossary term
     *
     * @throws InvalidParameterException  one of the parameters is invalid
     * @throws UserNotAuthorizedException the user is not authorized to issue this request
     * @throws PropertyServerException    there is a problem reported in the open metadata server(s)
     */
    String createGlossaryTerm(String                 userId,
                              String                 assetManagerGUID,
                              String                 assetManagerName,
                              String                 glossaryGUID,
                              String                 glossaryTermExternalIdentifier,
                              String                 glossaryTermExternalIdentifierName,
                              String                 glossaryTermExternalIdentifierUsage,
                              String                 glossaryTermExternalIdentifierSource,
                              KeyPattern             glossaryTermExternalIdentifierKeyPattern,
                              Map<String, String>    mappingProperties,
                              GlossaryTermProperties glossaryTermProperties) throws InvalidParameterException,
                                                                                    UserNotAuthorizedException,
                                                                                    PropertyServerException;
glossaryTermExternalIdentifier contains the value of the identifier. The other properties provide additional context information:

  • glossaryTermExternalIdentifierName is the name of the property where the identifier is stored in the third party asset manager.
  • glossaryTermExternalIdentifierUsage describes how the external identifier is used
  • glossaryTermExternalIdentifierSource describes the process that created the extern identifier
  • glossaryTermExternalIdentifierKeyPattern describes the pattern used for the identifier (how it is generated and managed). These are the values it can take, with the default (and most used) being LOCAL_KEY:
Enumeration Value Name Description
LOCAL_KEY 0 "Local Key" Unique key allocated and used within the scope of a single system.
RECYCLED_KEY 1 "Recycled Key" Key allocated and used within the scope of a single system that is periodically reused for different records.
NATURAL_KEY 2 "Natural Key" Key derived from an attribute of the entity, such as email address, passport number.
MIRROR_KEY 3 "Mirror Key" Key value copied from another system.
AGGREGATE_KEY 4 "Aggregate Key" Key formed by combining keys from multiple systems.
CALLERS_KEY 5 "Caller's Key" Key from another system can bey used if system name provided.
STABLE_KEY 6 "Stable Key" Key value will remain active even if records are merged.
OTHER 99 "Other" Another key pattern.

PermittedSynchronization

PermittedSynchronization defines the direction of flow of metadata.

Enumeration Value Name Description
BOTH_DIRECTIONS 0 "Both Directions" Metadata exchange is permitted in both directions. Synchronization is halted on a specific element if potentially clashing updates have occurred both in the third party technology and open metadata. Such conflicts are logged on the audit log and resolved through manual stewardship.
TO_THIRD_PARTY 1 "To Third Party" The third party technology is logically downstream of open metadata. This means the open metadata ecosystem is the originator and owner of the metadata being synchronized. Any updates detected in the third technology are overridden by the latest open metadata values.
FROM_THIRD_PARTY 2 "From Third Party" The third party technology is logically upstream (the originator and owner of the metadata). Any updates made in open metadata are not passed to the third party technology and the third party technology is requested to refresh the open metadata version.
OTHER 99 "Other" Another type of synchronization rule - see description property.

DataItemSortOrder

DataItemSortOrder provides the valid values for the sortOrder property of SchemaAttribute. It indicates whether the rows/instances of the data stored in this schema appear in any particular order or not.

Enumeration Value Name Description
UNKNOWN 0 "" "The sort order is not specified.
ASCENDING 1 "Ascending" "The attribute instances are organized so that the smallest/lowest value is first and the rest of the instances follow in ascending order.
DESCENDING 2 "Descending" The attribute instances are organized so that the largest/highest value is first and the rest of the instances follow in descending order.
UNSORTED 3 "Unsorted" "The instances of the schema attribute may appear in any order.

Supplementary Properties

It is common for external asset managers to include extensive descriptive properties for assets that include both a technical name and description as well as a business name and description. The Asset Manager OMAS supports this distinction and stores the technical name and description in an Asset metadata instance and the business name and description in a glossary term metadata instance that is linked to the asset using a SupplementaryProperties relationship. The properties that are stored in the glossary term are referred to as supplementary properties.