From b602a3bd2fbdda782026ef5d514bc6a5b113f210 Mon Sep 17 00:00:00 2001 From: Mandy Chessell Date: Wed, 11 Oct 2023 09:41:22 +0100 Subject: [PATCH] Add OMVSs to side menu Signed-off-by: Mandy Chessell --- site/docs/introduction/key-concepts.md | 4 ++-- site/mkdocs.yml | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/site/docs/introduction/key-concepts.md b/site/docs/introduction/key-concepts.md index 48f5b842b4..fb0256ab0b 100644 --- a/site/docs/introduction/key-concepts.md +++ b/site/docs/introduction/key-concepts.md @@ -3,9 +3,9 @@ # Key concepts of the Egeria technology -The functions needed to support the [open metadata ecosystem](/introduction/challenge/#the-open-metadata-ecosystem) are complex and need to be organized so they can be understood and adapted over time as the needs of your organization changes and grows. There is also an belief that it should be possible to dynamically activate and deactivate capability in the open metadata ecosystem through APIs allowing a self-service and local ownership approach to be adopted. This way, an organization does not need a large IT team to manage the deployment. +The functions of the [open metadata ecosystem](/introduction/challenge/#the-open-metadata-ecosystem) are complex, covering many use case. However, not all of these functions are needed initially. The software is therefore organized into components, making it easier to start simple and deploy more capability over time - as the needs of your organization changes and grows. It possible to dynamically activate and deactivate capability in the open metadata ecosystem through APIs, allowing the adoption of a self-service and local ownership approach. This way, an organization does not need a large IT team to manage the deployment. -The organization of the components requires some new terminology to be introduced to lable the different types of components, their purpose and how they connect together. The [overview](/introduction/overview) introduced the concept of the [OMAG Server Platform](/concepts/omag-server-platform) deployed multiple types in different processing centres and running [OMAG Servers](/concepts/omag-server). These OMAG Servers are specialized to perform specific functions. Figure 1 shows the different types of OMAG Servers and how they work together. +This type of metadata management requires some new terminology for the different types of components, their purpose and how they connect together. The [overview](/introduction/overview) introduced the concept of the [OMAG Server Platform](/concepts/omag-server-platform) deployed multiple types in different processing centres and running [OMAG Servers](/concepts/omag-server). These OMAG Servers are specialized to perform specific functions. Figure 1 shows the different types of OMAG Servers and how they work together. ![Figure 1](egeria-solution-components.svg) > **Figure 1:** This picture shows the different types of Egeria's OMAG servers and how they are connected together in a solution. They are not all required. You choose which ones you need, and how many of them to run, to match the needs of your organization. The servers are organized into three rings. In the inner-ring (labeled *Integrated Metadata*), a Metadata Access Server, Repository Proxy and Conformance Test Server are members of an *Open Metadata Repository Cohort*, or "cohort" for short, communicating via Egeria's peer-to-peer protocols. In the next ring out, called *Integrated Governance*, are the Governance Servers connected to the Metadata Access Server in order to access metadata in the open metadata ecosystem. In the outer ring, called *Governance Solution*, are the View Server and Presentation Server also connected to the Metadata Access Server. diff --git a/site/mkdocs.yml b/site/mkdocs.yml index 966c2788fc..bc4dfc955b 100644 --- a/site/mkdocs.yml +++ b/site/mkdocs.yml @@ -571,6 +571,10 @@ nav: - View Services (OMVS): - Open Metadata View Services: services/omvs/index.md - My Profile: services/omvs/my-profile/overview.md + - Collection Manager: services/omvs/collection-manager/overview.md + - Notification Manager: services/omvs/notification-manager/overview.md + - Notification Inbox: services/omvs/notification-inbox/overview.md + - Project Manager: services/omvs/project-manager/overview.md - Glossary Author: services/omvs/glossary-author/overview.md - Glossary Browser: services/omvs/glossary-browser/overview.md - Glossary Workflow: services/omvs/glossary-workflow/overview.md