Skip to content

Commit

Permalink
Merge branch 'main' of https://github.com/odpi/egeria-docs into dojod…
Browse files Browse the repository at this point in the history
…ay1a
  • Loading branch information
planetf1 committed Jan 5, 2022
2 parents bcf41ab + 1987758 commit 73c463b
Show file tree
Hide file tree
Showing 213 changed files with 7,618 additions and 5,331 deletions.
2 changes: 1 addition & 1 deletion site/docs/concepts/cohort-member.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,6 @@ metadata repository cohort in
The administration hands on lab called "**Understanding Cohort Configuration Lab**"
provides an opportunities to query the cohort registries of cohort members as they
exchange metadata for Coco Pharmaceuticals.
Instructions for running the labs [can be found here](/egeria-docs/education/open-metadata-labs).
Instructions for running the labs [can be found here](/egeria-docs/education/open-metadata-labs/overview).

--8<-- "snippets/abbr.md"
3 changes: 3 additions & 0 deletions site/docs/concepts/extended-properties-type-hierarchy.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions site/docs/concepts/extended-properties.drawio
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
<mxfile host="Electron" modified="2021-12-16T17:36:28.059Z" agent="5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/15.2.7 Chrome/93.0.4577.63 Electron/14.0.1 Safari/537.36" etag="9LF8MhJr-hcVrP3d5KQ9" version="15.2.7" type="device"><diagram id="GG5_nNqYO6-7ISTeHCT9" name="type-hierarchy">7Vpdc5s4FP01fkwGEGD8aDtJO9NtN9t0ZtOnHRnJRg1GVMiJ3V+/VyC+nZjUJkySeiYZ6UoI6Zx7j66AEZqvtx8EjoPPnNBwZBlkO0IXI8uaIAv+K8MuM5g2sjPLSjCibaXhhv2i2mho64YRmtQ6Ss5DyeK60edRRH1Zs2Eh+EO925KH9bvGeEVbhhsfh23rv4zIQFtNd1I2fKRsFehbe9Y4a1jjvLNeSRJgwh8qJnQ5QnPBucxK6+2chgq8HJfsuqtHWouJCRrJLhds8OYfI/5wn4x3t+EXZE+vbv87MzU/9zjc6BWP5tZoOoNBmdyp8mw2stwQbjFbCCitVKmw5IZvPGZ+boU5LMqe6drlLgc0kOsQSia0JVLwOzrnIRdpG3J9jy6W0IJDtorA5sM0KDTOliwMKx0Jpt7SB/tKYMKgU6VtTLFLjeLW91RIun0UM7NgAlyY8jWVYgdd9AWuocnT7mshXX8ofcGytS2ouIGjbVi736oYumQICpqk5xCGWoRJhf23XUzBPELTFG7BolULesE3EaFqdAXPQ8AkvYmxr1ofIHrB9hQ5Rvrbj/ky/VWIC+lS9kSB15EC1BcFltdClhIQDV3lQgZ8xSMcXpbWWR37ss9fnMca8R9Uyp1WQLyRvM4HwCV2t+r6cyevfq+2XWz14FltV9TIVOkgVBch9+8y0xVTa8476JuaXkGZWtDThMH6+Ub49CmgtEZKLFZUHnTqtgsIGmLJ7uszOT2fk9No4Ce8vMPvRAiRO7QQ5uFdYQ2WA4QxHiWFEjJYXos5QeOQ+bjR6y2KpW0OTZNttpB9CbHcMlnRSqh9z9UOyqVSqkoplP0L7Pi0AmtbHQXWsYcU2HyaxwrsV7qkAJJP8QLc5FiNJe7CddwOGgvBavmPaOxySSau20/wnpkuGjp629nmzw3gtWSUfMHrdsbZ5BATkioyDq8FjwEdRkvZXYOMWi5eKzFNr8tHmVdHzNrrHtHyEcLua8y7PzfqXDUDNuSZJljdMpXaorU5CmCUDvSIN72JLeHMNDt6FZr05VX2MAn0cDrtdNRpe9BEOJ/msTo9TRIq34E+I+N87Ayt0G6Ls6iLMBOa+ILFSpsP9v0jss91DXNybnX0DLsvz8hd7jVk3s9T5t/N1E+o6E7+LPqgortHKrq+9Jqnh9Tc4Rxvcu7UXA4Mk8rPa2ze2UT1KA3PKqZ1hLOZp9k6LrDEN+9h8zANe+Cdw9lzKhtQjAuC+gDb6Qg26iu1ctoHqd+Kj79jGn2mEhOIk6/q1dGbD5QzyxsPHSn2nkj5kyQdzyzqyGxvr3Kc8SA50ut7lZO/Jz78pNHqJd8Zo7rvoEkjv8lW0Mpv9g3USJxQ/kXCS6VK3uF9t8J0xCPldAQnQepzZt2XlP0aS5DsKLVYBipCPv9gwXqGL7SZqwSn84TqHpvQNl8wNc9FXQn2vAMD9U3vnreJTXqTAMeq6G9EuJsJ7N+pmDqk46XumKcRZMftstXu4dw1xj0Jcj6jV4geyiPhAHim1ddu5rYPYbWn7msMPg9/gIKaQzODkQFgtAqUTGwlTcECPCoD6Efx0SKJ9yUlKsOpY97KKRXgzMfhVDesGSHZnkoT9it9rZPtZLEKzxQfZzZyLtRYsI0menNrJTVaJKspqzadgGg0ae497Uc75vgl0xa3fXSrEZ1s4hjykpRAwgT1Zbh7im8Z0AbVBl/8UJ/TvVeOzfP+OIZq+dVftu2U306iy/8B</diagram></mxfile>
63 changes: 63 additions & 0 deletions site/docs/concepts/extended-properties.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
<!-- SPDX-License-Identifier: CC-BY-4.0 -->
<!-- Copyright Contributors to the ODPi Egeria project 2020. -->

# Extended Properties

Extended properties provide a means to maintain the properties of elements that are [subtypes of the types](/egeria-docs/concepts/open-metadata-type-definitions) supported directly on an API.

For example, the [Data Manager OMAS](/egeria-docs/services/omas/data-manager/overview) has support for maintaining metadata about *Topics*. Topics are special types of [*assets*](/egeria-docs/concepts/asset) that provide a destination for exchanging events.

Model [0223 Events and Logs](/egeria-docs/types/2/0223-Events-and-Logs) extends the `Topic` type with a new type called `KafkaTopic` that introduces two new properties: `partitions` and `replicas`. `KafkaTopic` is used to represent a topic that is owned and managed by [*Apache Kafka*](https://kafka.apache.org/). The full type hierarchy for `KafkaTopic` is shown in Figure 1.

![Figure 1](extended-properties-type-hierarchy.svg)
**Figure 1:** The type inheritance hierarchy for KafkaTopic. This shows all of the properties that are valid for an element of type `KafkaTopic`. Properties `qualifiedName` and `additionalProperties` are inherited from `Referenceable`; properties `name` and `description` are inherited from `Asset`; finally `topicType` is inherited from `Topic`. All of these properties are supported natively by the Data Manager OMAS. The `partitions` and `replicas` properties introduced by the `KafkaTopic` type are maintainable through `extendedProperties`.

The code snippet below shows a call to the Data Manager OMAS to create an element of type `KafkaTopic`.
The standard properties for a topic are set up first. Then the name of the subtype for the new element (null means `Topic`). Then any extended properties for the requested subtype are set up.
Finally any additional properties that the organization wants to store that are not defined in the type definitions go in `additionalProperties`.
```
TopicProperties topicProperties = new TopicProperties();
/*
* Set up the standard properties - note displayName maps to the name property.
*/
topicProperties.setQualifiedName("Topic:myTopicName");
topicProperties.setDisplayName("myTopicName");
topicProperties.setDescription("Testing that topics can be catalogued");
topicProperties.setTopicType("PLAINTEXT");
/*
* Set up the specific type name for the new element. It must be a null
* (for a type of Topic) or a type name that is a subtype of Topic.
*/
topicProperties.setTypeName("KafkaTopic");
/*
* Set up the properties that come from the subtypes of Topic.
*/
Map<String, Object> extendedProperties = new HashMap<>();
extendedProperties.put("partitions", 1);
extendedProperties.put("replicas", 5)
topicProperties.setExtendedProperties(extendedProperties);
/*
* Set up additional properties. These do not need to be defined in any of the
* type definitions.
*/
Map<String, String> additionalProperties = new HashMap<>();
additionalProperties.put("autoDefined", "true");
additionalProperties.put("jsonPayload", "true");
topicProperties.setAdditionalProperties(additionalProperties);
String topicGUID = dataManagerClient.createTopic(userId,
eventBrokerGUID
eventBrokerName,
eventBrokerIsHome,
topicProperties);
```



--8<-- "snippets/abbr.md"
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@

# Guards

Guards are labels that are created by [governance action services](governance-action-service.md)
Guards are labels that are created by [governance services](/egeria-docs/concepts/governance-service)
and are used by the [Governance Engine OMAS](/egeria-docs/services/omas/governance-engine/overview) to
determine which governance action service to run next.
determine which [governance action](/egeria-docs/concepts/governance-action) to run next.


--8<-- "snippets/abbr.md"
4 changes: 2 additions & 2 deletions site/docs/concepts/guid.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,11 @@ using the `UUID.randomUUID().toString()` method and they look something like thi

They are often used on API calls to request a specific instance of metadata.
However, they are not very consumable for people, so most metadata instances also have
[qualified names](referenceable.md) - also unique - and display names - not necessarily unique
[qualified names](/egeria-docs/concepts/referenceable) - also unique - and display names - not necessarily unique
for displaying information to end users.

There is a tiny chance that two servers will generate the same guid. If this happens, it is
detected by the [repository services](/egeria-docs/services/omrs) and messages are
detected by the [repository services](/egeria-docs/services/omrs/overview) and messages are
output on the detecting server's
[audit log](/egeria-docs/concepts/audit-log).
The repository services also have APIs for re-identifying (ie changing the guid)
Expand Down
7 changes: 5 additions & 2 deletions site/docs/concepts/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,7 @@
- [Event Bus](/egeria-docs/concepts/event-bus)
- [Event Broker](/egeria-docs/concepts/basic-concepts/#event-broker)
- [Event Management Services Subsystem (OMRS)](/egeria-docs/services/omrs)
- [Extended Properties](/egeria-docs/concepts/extended-properties)
- [External Identifiers](/egeria-docs/features/external-identifiers/overview)
- [External References](/egeria-docs/features/external-references/overview)

Expand Down Expand Up @@ -138,7 +139,7 @@

## H

- [Hands on labs](/egeria-docs/education/open-metadata-labs)
- [Hands on labs](/egeria-docs/education/open-metadata-labs/overview)
- [Head count](/egeria-docs/concepts/person-role/#head-count-limit)
- [Home Metadata Collection](/egeria-docs/concepts/metadata-collection-id)
- [Home Metadata Repository](/egeria-docs/concepts/home-metadata-repository)
Expand Down Expand Up @@ -226,7 +227,7 @@
- [Open Metadata Conformance Suite](/egeria-docs/guides/cts/overview)
- [Open Metadata Exchange Rule](/egeria-docs/concepts/open-metadata-exchange-rule)
- [Open Metadata Instances](/egeria-docs/concepts/open-metadata-instances)
- [Open Metadata Labs](/egeria-docs/education/open-metadata-labs)
- [Open Metadata Labs](/egeria-docs/education/open-metadata-labs/overview)
- [Open Metadata Repository](/egeria-docs/concepts/metadata-repository)
- [Open Metadata Repository Cohort](/egeria-docs/concepts/cohort-member)
- [Open Metadata Repository Services](/egeria-docs/services/omrs)
Expand Down Expand Up @@ -264,6 +265,7 @@
- [Ratings](/egeria-docs/concepts/review)
- [Referenceable](/egeria-docs/concepts/referenceable)
- [Registry Events](/egeria-docs/concepts/cohort-events)
- [Registered Services](/egeria-docs/concepts/omag-subsystem)
- [Repository Connector](/egeria-docs/concepts/repository-connector)
- [Repository Helper](/egeria-docs/concepts/repository-helper)
- [Repository Proxy](/egeria-docs/concepts/repository-proxy)
Expand Down Expand Up @@ -296,6 +298,7 @@
- [Stewardship Integrator OMIS](/egeria-docs/services/omis/stewardship-integrator/overview)
- [Stewardship Server](/egeria-docs/concepts/engine-host)
- [Subject Area OMAS](/egeria-docs/services/omas/subject-area/overview)
- [Subsystem](/egeria-docs/concepts/omag-subsystem)
- [Supported Zones](/egeria-docs/concepts/governance-zone)


Expand Down
2 changes: 1 addition & 1 deletion site/docs/concepts/integration-connector.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,6 @@ integration service configuration
all connectors.
- [Configuring the integration services](/egeria-docs/guides/admin/servers/configuring-an-integration-daemon/#configure-the-integration-services) to
understand how to set up an integration connector.
- [Developer guide](/egeria-docs/guides/developer-guide/integration-connectors/overview) for more information on writing connectors.
- [Developer guide](/egeria-docs/guides/developer/integration-connectors/overview) for more information on writing connectors.

---8<-- "snippets/abbr.md"
2 changes: 1 addition & 1 deletion site/docs/concepts/omag-server.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,6 @@ The different types of OMAG Servers connect together as illustrated in Figure 2.
This configuration document is stored by a [configuration document store connector](/egeria-docs/concepts/configuration-document/#storage).

- [Configuring an OMAG Server](/egeria-docs/guides/admin/servers)
- [Start and stop an OMAG Server](/egeria-docs/guides/admin/operating-omag-server.md)
- [Start and stop an OMAG Server](/egeria-docs/guides/operations/guide/#starting-and-stopping-an-omag-server)

--8<-- "snippets/abbr.md"
59 changes: 49 additions & 10 deletions site/docs/concepts/omag-subsystem.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,58 @@ hide:

# Open Metadata and Governance (OMAG) Subsystems

A subsystem is a collection of components within a software server that supports one or more related services. Subsystems can be organized in a hierarchy where course-grained subsystems can be decomposed into more fine-grained subsystems.
A *subsystem* is a collection of components within a software server platform that supports one or more related services. Subsystems can be organized in a hierarchy where course-grained subsystems can be decomposed into more fine-grained subsystems.

The [OMAG Server](omag-server.md) is a flexible software server whose subsystems can be activated (or not) through the presence (or absence) of the subsystem's configuration properties in the OMAG Server's [configuration document](/egeria-docs/concepts/configuration-document).
The [OMAG Server Platform](/egeria-docs/concepts/omag-server-platform) is a collection of subsystems that support open metadata and governance services as well as its own operational needs.

The potential subsystems within an [OMAG Server](omag-server.md) are as follows:
## Fixed services

Fixed services that are always present in the platform:

- [Server Chassis](/egeria-docs/services/server-chassis) provides the main class of the OMAG Server Platform that manages the start up and shutdown of a platform instance.

- [Administration Services](/egeria-docs/services/admin-services) support the configuration and operation (such as starting and stopping) of [OMAG Servers](/egeria-docs/concepts/omag-servers).

- [First Failure Data Capture (FFDC) services](/egeria-docs/services/ffdc-services) support the capture of diagnostics.

- [Multi-tenant Services](/egeria-docs/services/multi-tenant) manages information about the running servers so REST API requests made to the platform can be routed to the correct server.

- [Platform Operation Services](/egeria-docs/services/platform-services) retrieves information about a running platform instance and its associated servers.

- [Open Metadata Repository Services (OMRS)](/egeria-docs/services/omrs) for supporting access to metadata stored in metadata repositories and the exchange of metadata between repositories via an [open metadata repository cohort](/egeria-docs/concepts/cohort-member). The repository services are further divided into [OMRS subsystems](/egeria-docs/services/omrs/#omrs-subsystems) that can be activated independently.
- [Integration daemon services](/egeria-docs/services/integration-daemon-services) for running integration connectors that exchange metadata with third party technologies.
- [Connected Asset Services](/egeria-docs/services/ocf-metadata-management) for supporting the `ConnectedAsset` interface of a connector.
- Dynamically registered services provide specialist APIs for particular technologies and user roles. Each of these services runs in their own subsystem independent of the other registered services. The implementation may come from Egeria or a third party. The links are to Egeria provided dynamic services.
- [Open Metadata Access Services (OMASs)](/egeria-docs/services/omas) for supporting domain-specific services for metadata access and governance. Access services run in the [metadata access server](metadata-access-server.md).
- [Open Metadata Engine Services (OMESs)](/egeria-docs/services/omes) for supporting specialized governance engines that drive governance activity in the open metadata ecosystem. The engine services run in the [engine host](engine-host.md) server.
- [Open Metadata Integration Services (OMISs)](/egeria-docs/services/omis) for supporting specific types of [integration connectors](integration-connector.md). The integration services run in the [integration daemon](integration-daemon.md) server.
- [Open Metadata View Services (OMVSs)](/egeria-docs/services/omvs) for supporting REST services for a User Interface (UI). The view services run in a [view server](view-server.md).

- [Repository Handler](/egeria-docs/services/repository-handler) manages calls to the open metadata repositories through the `OMRSRepositoryConnector` interface. It manages error handling, provenance of metadata, deduplication and effectivity dating

- [Metadata Security Services](/egeria-docs/services/metadata-security services) supports calls to the security connectors at appropriate points in the call path for REST APIs and event handling.

- [Generic Handlers](/egeria-docs/services/generic-handlers) manage the conversion between OMAS specific beans and OMRS beans as well as templating, management of anchors and calls to the metadata security services for assets and connections. It uses the repository handler to access stored metadata.

- Governance server services:

- [Data engine services](/egeria-docs/services/data-engine-proxy-services) implements the services for the [Data Engine Proxy](/egeria-docs/concepts/date-engine-proxy).
- [Engine host services](/egeria-docs/services/engine-host-services) implements the services for the [Engine Host](/egeria-docs/concepts/engine-host).
- [Integration daemon services](/egeria-docs/services/integration-daemon-services) implements the services for the [Integration Daemon](/egeria-docs/concepts/integration-daemon).
- [Open lineage services](/egeria-docs/services/open-lineage-services) implements services for the [Open Lineage Server](/egeria-docs/concepts/open-lineage-server).

- [Connected Asset Services](/egeria-docs/services/ocf-metadata-management) for supporting the server-side REST API behind the `ConnectedAsset` interface of an OCF connector.






## Registered services

Dynamically registered services provide specialist APIs for particular technologies and user roles. Each of these services runs in their own subsystem independent of the other registered services. The implementation may come from Egeria or a third party. The links are to Egeria provided dynamic services.

- [Open Metadata Access Services (OMASs)](/egeria-docs/services/omas) for supporting domain-specific services for metadata access and governance. Access services run in the [metadata access server](metadata-access-server.md).

- [Open Metadata Engine Services (OMESs)](/egeria-docs/services/omes) for supporting specialized governance engines that drive governance activity in the open metadata ecosystem. The engine services run in the [engine host](engine-host.md) server.
- [Open Metadata Integration Services (OMISs)](/egeria-docs/services/omis) for supporting specific types of [integration connectors](integration-connector.md). The integration services run in the [integration daemon](integration-daemon.md) server.
- [Open Metadata View Services (OMVSs)](/egeria-docs/services/omvs) for supporting REST services for a User Interface (UI). The view services run in a [view server](view-server.md).

## Activating the OMAG subsystems

The [OMAG Server](/egeria-docs/concepts/omag-server) is a dynamic software server whose subsystems can be activated (or not) through the presence (or absence) of the subsystem's configuration properties in the OMAG Server's [configuration document](/egeria-docs/concepts/configuration-document).

--8<-- "snippets/abbr.md"
Loading

0 comments on commit 73c463b

Please sign in to comment.