Remove obsolete services

saved/lineage-warehouse/lineage-warehouse.md

@@ -0,0 +1,18 @@
+---
+hide:
+- toc
+---
+
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+<!-- Copyright Contributors to the Egeria project 2020. -->
+
+# Lineage Warehouse
+
+The lineage warehouse is a [governance server](/concepts/governance-server)
+that manages a historical warehouse of lineage information.
+
+![Lineage Warehouse](lineage-warehouse.svg)
+
+Its behavior and configuration is described [in the administration guide](/guides/admin/servers/by-server-type/configuring-a-lineage-warehouse).
+
+--8<-- "snippets/abbr.md"

site/docs/concepts/asset.md

@@ -56,7 +56,6 @@ Some examples:
 | [Asset Manager OMAS](/services/omas/asset-manager/overview) | provides a service for exchanging metadata about assets and related information with a third party [asset manager](/concepts/server-capability). This API supports the many-to-many correlation of identifiers used in the third party asset manager and the open metadata ecosystem. |
 | [Asset Owner OMAS](/services/omas/asset-owner/overview) | provides a service for the owner of an asset to classify and manage the asset, and understand how it is being used by the organization. |
 | [Data Manager OMAS](/services/omas/data-manager/overview) | enables a data manager (such as a database or file system) to maintain information about the assets it stores. |
-| [Governance Engine OMAS](/services/omas/governance-engine/overview) | provides the metadata services for [governance action services](/concepts/governance-action-service) that verify, enhance and correct the properties of assets and their associated elements. |
 | [IT Infrastructure OMAS](/services/omas/it-infrastructure/overview) | provides a service for maintaining information about the IT assets and supporting infrastructure owned or used by an organization. |
 | [Data Science OMAS](/services/omas/data-science/overview) | provides a service for maintaining information about analytical models and related assets such as python notebooks. |
 

site/docs/concepts/engine-host.md

@@ -10,7 +10,7 @@ hide:
 
 An *engine host* is an [OMAG Server](/concepts/omag-server) that hosts one or more [governance engines](/concepts/governance-engine). Governance engines define collections of [governance services](/concepts/gpvernance-service) used to automate governance activity in the digital landscape. The governance services within the governance engines may access third party technology to perform their responsibilities or implement their behavior directly.
 
-The engine host uses a [metadata access server](/concepts/metadata-access-server) to retrieve the [definitions of the governance engines](/governance-engine-definition) and the governance services within them. These definitions are retrieved through the [Governance Engine OMAS](/services/omas/governance-engine/overview). The Governance Engine OMAS also manages the definition of [governance action processes](/concepts/governance-action-process) that choreograph calls to the services in a governance engine in order to implement technical controls in the governance program.
+The engine host uses a [metadata access server](/concepts/metadata-access-server) to retrieve the [definitions of the governance engines](/governance-engine-definition) and the governance services within them. These definitions are retrieved through the [Governance Server OMAS](/services/omas/governance-server/overview). The Governance Server OMAS also manages the definition of [governance action processes](/concepts/governance-action-process) that choreograph calls to the services in a governance engine in order to implement technical controls in the governance program.
 
 ![Engine host in an OMAG Server ecosystem](engine-host.svg)
 

site/docs/concepts/governance-engine-definition.md

@@ -37,11 +37,11 @@ Each governance engine definition describes a single engine and its specialized
 
 !!! education "Further information"
 
-    * Governance engine definitions are typically defined in a [governance engine pack](/guides/developer/open-metadata-archives/creating-governance-engine-packs) or through the [Governance Engine OMAS](/services/omas/governance-engine/overview) API.
+    * Governance engine definitions are typically defined in a [governance engine pack](/guides/developer/open-metadata-archives/creating-governance-engine-packs) or through the [Governance Server OMAS](/services/omas/governance-server/overview) API.
 
-    * The Open Metadata Types model [0461 Governance Action Engines](/types/4/0461-Governance-Engines) shows the types for a governance engine definition.
+    * The Open Metadata Types model [0461 Governance Engines](/types/4/0461-Governance-Engines) shows the types for a governance engine definition.
 
-    * Governance engines are run by the [Open Metadata Engine Services (OMES)](/services/omes) in an [Engine Host](/concepts/engine-host) OMAG Server.  The [Engine Host Services](/services/engine-host-services) called the [Governance Engine OMAS](/services/omas/governance-engine/overview)
+    * Governance engines are run by the [Open Metadata Engine Services (OMES)](/services/omes) in an [Engine Host](/concepts/engine-host) OMAG Server.  The [Engine Host Services](/services/engine-host-services) called the [Governance Server OMAS](/services/omas/governance-server/overview)
 
 
 --8<-- "snippets/abbr.md"

site/docs/concepts/governance-engine.md

@@ -26,7 +26,7 @@ Calls to the governance engine are made by creating [engine actions](/concepts/e
 
 ??? education "Further information"
 
-    Each governance engine has a unique name.  A *governance engine definition* for this unique name is either created through the [Governance Engine OMAS](/services/omas/governance-engine/overview) API or as part of a [governance engine pack](/concepts/governance-engine-pack).  The [governance engine is configured](/guides/admin/servers/by-section/engine-host-services-section) in the [engine host](/concepts/engine-host) using this unique name.
+    Each governance engine has a unique name.  A *governance engine definition* for this unique name is either created through the [Governance Server OMAS](/services/omas/governance-server/overview) API or as part of a [governance engine pack](/concepts/governance-engine-pack).  The [governance engine is configured](/guides/admin/servers/by-section/engine-host-services-section) in the [engine host](/concepts/engine-host) using this unique name.
 
     The open metadata types for this definition are in model [0461 - Governance Engines](/types/4/0461-Governance-Engines) - specifically notice **Governance Engine** and **GovernanceService** linked by the **SupportedGovernanceService** relationship.
 

site/docs/concepts/governance-server.md

@@ -20,7 +20,6 @@ The table below shows the different types of governance servers and the OMASs th
 |:----------------------------------------------------|:-------------------------------------------------------------------------|:---------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| 
 | [Integration Daemon](/concepts/integraition-daemon) | Manages the capture of metadata through configured integration services. | [Integration Daemon Services](/services/integration-daemon-services) | [Governance Server OMAS](/services/omas/governance-server/overview) provides support for retrieving governance engine definitions.  The [integration services](../../integration-services) define the OMASs that support each type of integration connector. |
 | [Engine Host](/concepts/engine-host)                | Manages governance engines.                                              | [Engine Host Services](/services/engine-host-services)               | [Governance Server OMAS](/services/omas/governance-server/overview) provides support for retrieving governance engine definitions. The [engine services](../../engine-services) define the OMASs that support each type of governance engine.                |
-| [Lineage Warehouse](/concepts/lineage-warehouse)    | Provides a historic reporting warehouse for lineage.                     | [Lineage Warehouse Services](/services/lineage-warehouse-services)   | [Asset Lineage OMAS](/services/omas/asset-lineage/overview)                                                                                                                                                                                                  | 
 
 
 --8<-- "snippets/abbr.md"

site/docs/concepts/governance-service-definition.md

@@ -74,8 +74,8 @@ A governance service definition is then linked into one or more [Governance Engi
 
 !!! education "Further information"
 
-    * Governance engine definitions are typically defined in a [governance engine pack](/guides/developer/open-metadata-archives/creating-governance-engine-packs) or through the [Governance Engine OMAS](/services/omas/governance-engine/overview) API.  This will typically include the governance service definitions.
-    * Governance engines are run by the [Open Metadata Engine Services (OMES)](/services/omes) in an [Engine Host](/concepts/engine-host) OMAG Server.  The [Engine Host Services](/services/engine-host-services) called the [Governance Engine OMAS](/services/omas/governance-engine/overview).
+    * Governance engine definitions are typically defined in a [governance engine pack](/guides/developer/open-metadata-archives/creating-governance-engine-packs) or through the [Governance Server OMAS](/services/omas/governance-server/overview) API.  This will typically include the governance service definitions.
+    * Governance engines are run by the [Open Metadata Engine Services (OMES)](/services/omes) in an [Engine Host](/concepts/engine-host) OMAG Server.  The [Engine Host Services](/services/engine-host-services) called the [Governance Server OMAS](/services/omas/governance-server/overview).
 
 
 --8<-- "snippets/abbr.md"

site/docs/concepts/governance-service.md

@@ -17,7 +17,7 @@ Instructions for implementing your own governance services are in the developer
 
 ## Support for running governance services
 
-The [Governance Engine OMAS](/services/omas/governance-engine/overview) provides:
+The [Governance Server OMAS](/services/omas/governance-server/overview) provides:
 
 * The API to create [governance engine definitions](/concepts/governance-engine) for the governance services.
 * The API to link governance services together into [governance action processes](/concepts/governance-action-process).

site/docs/concepts/guard.md

@@ -5,7 +5,7 @@
 # Guards
 
 Guards are labels that are created by [governance services](/concepts/governance-service)
-and are used by the [Governance Engine OMAS](/services/omas/governance-engine/overview) to
+and are used by the [Governance Server OMAS](/services/omas/governance-server/overview) to
 determine which [engine action](/concepts/engine-action) to run next.
 
 

site/docs/concepts/index.md

@@ -157,11 +157,11 @@
 - [Governance Domain Identifier](/concepts/governance-domain)
 - [Governance Engine](/concepts/governance-engine)
 - [Governance Engine Definition](/concepts/governance-engine-definition)
-- [Governance Engine OMAS](/services/omas/governance-engine/overview)
 - [Governance Program](/services/omas/governance-program/overview)
 - [Governance Program OMAS](/services/omas/governance-program/overview)
 - [Governance Request Type](/concepts/governance-request-type)
 - [Governance Servers](/concepts/governance-server)
+- [Governance Server OMAS](/services/omas/governance-server/overview)
 - [Governance Service](/concepts/governance-service)
 - [Governance Service Definition](/concepts/governance-service-definition)
 - [Governance Zones](/concepts/governance-zone)
@@ -222,7 +222,6 @@
 - [Lineage](/features/lineage-management/overview)
 - [Lineage Integrator OMIS](/services/omis/lineage-integrator/overview)
 - [Lineage Warehouse](/concepts/lineage-warehouse)
-- [Lineage Warehouse Services](/services/lineage-warehouse-services)
 - [Local Metadata Collection Id](/concepts/metadata-collection-id)
 - [Local Repository Services (OMRS)](/services/omrs)
 

site/docs/concepts/integration-group.md

@@ -44,7 +44,7 @@ An [integration daemon is configured](/guides/admin/servers/by-server-type/confi
 
 ???+ education "Further information"
 
-    Each integration group has a unique name.  An *IntegrationGroup* entity with a qualifiedName set to this unique name is created through the [Governance Engine OMAS](/services/omas/governance-engine/overview) API.  This API is also used to create and link the integration connector definitions into the integration group.
+    Each integration group has a unique name.  An *IntegrationGroup* entity with a qualifiedName set to this unique name is created through the [Governance Server OMAS](/services/omas/governance-server/overview) API.  This API is also used to create and link the integration connector definitions into the integration group.
 
     The [integration group's qualifiedName is configured](/guides/admin/servers/by-section/integration-daemon-services-section) in the [integration daemon](/concepts/integration-daemon).
 

site/docs/concepts/lineage-warehouse.md

@@ -8,11 +8,8 @@ hide:
 
 # Lineage Warehouse
 
-The lineage warehouse is a [governance server](/concepts/governance-server)
-that manages a historical warehouse of lineage information.
+The lineage warehouse is a data store
+that manages a historical warehouse of lineage information.  See [Lineage Management](/features/lineage-managent/overview) for details of how it is populated and used.
 
-![Lineage Warehouse](lineage-warehouse.svg)
-
-Its behavior and configuration is described [in the administration guide](/guides/admin/servers/by-server-type/configuring-a-lineage-warehouse).
 
 --8<-- "snippets/abbr.md"

site/docs/concepts/omag-server.md

@@ -48,7 +48,6 @@ The types of OMAG Server are shown in Figure 1. The hierarchy groups similar typ
 - [Governance Server](/concepts/governance-server) - supports the use of metadata in the broader IT landscape.
     - [Engine Host](/concepts/engine-host) - provides a runtime for a specific type of [governance engine](/concepts/governance-engine) that runs [governance services](/concepts/governance-service) to monitor, enhance and govern the open metadata ecosystem.
     - [Integration Daemon](/concepts/integration-daemon) - manages the synchronization of metadata with third party technology that can not call the access services directly.   through the [integration services](/services/omis).
-    - [Lineage Warehouse](/concepts/lineage-warehouse) - Manages the collation of lineage information and maintains it in a format for reporting. This includes the state of the lineage at different points in time.
 
 ## Server connectivity
 

site/docs/concepts/omag-subsystem.md

@@ -31,10 +31,8 @@ Fixed services that are always present in the platform:
 
 - Governance server services:
 
-    - [Data engine services](/services/data-engine-proxy-services) implements the services for the [Data Engine Proxy](/concepts/date-engine-proxy).
     - [Engine host services](/services/engine-host-services) implements the services for the [Engine Host](/concepts/engine-host).
     - [Integration daemon services](/services/integration-daemon-services) implements the services for the [Integration Daemon](/concepts/integration-daemon).
-    - [Lineage warehouse services](/services/lineage-warehouse-services) implements services for the [Lineage Warehouse](/concepts/lineage-warehouse).
 
 - [Connected Asset Services](/services/ocf-metadata-management) for supporting the server-side REST API behind the `ConnectedAssetProperties` interface of an [Open Connector Framework (OCF)](/frameworks/ocf/overview) connector.
 

site/docs/concepts/open-lineage-server.md

@@ -8,6 +8,6 @@ hide:
 
 # Open lineage Server
 
-The Open Lineage Server was renamed to the [Lineage Warehouse](/concepts/lineage-warehouse) in V5.0 of Egeria.
+Open Lineage is processed by the [Lineage Integrator OMIS](/services/omis/lineage-integrator/overview) running in the [Integration Daemon](/concepts/integration-daemon).  Details of how it is used can be found in the [Lineage Management](/features/lineage-management/overview) feature.
 
 --8<-- "snippets/abbr.md"

site/docs/concepts/schema.md

@@ -137,7 +137,6 @@ APIs that support the definition of schemas:
 * [Asset Owner OMAS](/services/omas/asset-owner/overview)
 * [Asset Manager OMAS](/services/omas/asset-manager/overview)
 * [Data Manager OMAS](/services/omas/data-manager/overview)
-* [Governance Engine OMAS](/services/omas/governance-engine/overview)
 * [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview)
 * [Database Integrator OMIS](/services/omis/database-integrator/overview)
 * [Files Integrator OMIS](/services/omis/files-integrator/overview)

site/docs/connectors/governance-action/generic-element-watchdog-governance-action-service.md

@@ -83,7 +83,7 @@ The rest of the properties are the governance action processes to call for speci
     }
     ```
 
-    This is its connection definition to use when creating the definition of the governance action service using the [Governance Engine OMAS](/services/omas/governance-engine). Remove the configuration properties that are not required. Replace `{{typeName}}`, `{{guid}}` and `{{processQualifiedName}}` as required.
+    This is its connection definition to use when creating the definition of the governance action service using the [Governance Server OMAS](/services/omas/governance-server/overview). Remove the configuration properties that are not required. Replace `{{typeName}}`, `{{guid}}` and `{{processQualifiedName}}` as required.
 
 ## Governance action settings
 

site/docs/connectors/governance-action/move-copy-file-provisioning-governance-action-service.md

@@ -74,11 +74,9 @@ processing path and the folders represent the data sets.
 Irrespective of the pattern used, the resulting changes to the metadata can lead to the triggering of additional activity
 in the open metadata ecosystem.  For example:
 
-* The [Asset Lineage OMAS](/services/omas/asset-lineage/overview)
-may publish the lineage to the [Lineage Warehouse](/concepts/lineage-warehouse).
+* An [integration connector](/services/omas/asset-manager/overview) may publish the lineage to the [Lineage Warehouse](/concepts/lineage-warehouse).
 
-* Additional [Governance Action Services](/concepts/governance-action-service)
-may be triggered.
+* Additional [Governance Action Services](/concepts/governance-action-service) may be triggered to provide additional enrichment of the lineage graph.
 
 ## Configuration
 

site/docs/connectors/index.md

@@ -300,16 +300,6 @@ Egeria's [Open Metadata Repository Services (OMRS)](/services/omrs) provides a d
 The connection for this connector is configured in the `LocalRepositoryRemoteConnection` property of the
 cohort member's [Local Repository Configuration](/user/guides/admin/servers/by-section/#configuring-the-local-repository-store).
 
-### Governance Daemon Connectors
-
----8<-- "snippets/connectors/governance-daemon-intro.md"
-
-| Connector                                                                                            | Description                                                                                                                                                                   |
-|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Lineage Warehouse Janus Connector](/connectors/governance-daemon/lineage-warehouse-janus-connector) | The Lineage Warehouse connectors provide plugins to the [Lineage Warehouse](/concepts/lineage-warehouse) that allow the Lineage Warehouse Services to connect with databases. |
-
-
-
 
 
 --8<-- "snippets/abbr.md"

site/docs/connectors/resource/kafka-open-metadata-topic-connector.md

@@ -184,7 +184,7 @@ By default, Egeria generates its topic names using the following naming conventi
 
     These need to be done FOR EACH SERVER configured to run one or more OMASs. (For example for Coco Pharmaceuticals this might include `cocoMDS1`, `cocoMDS2`, `cocoMDS3` etc).
 
-    Then, FOR EACH OMAS configured (eg Asset Consumer OMAS, Data Platform OMAS, Governance Engine OMAS etc.) that supports topics, you will need to create the topic it is using.
+    Then, FOR EACH OMAS configured (eg Asset Consumer OMAS, Data Platform OMAS, Governance Server OMAS etc.) that supports topics, you will need to create the topic it is using.
 
     This is the default naming convention: