Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OMVSs to side menu #853

Merged
merged 2 commits into from
Oct 11, 2023
Merged

Add OMVSs to side menu #853

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b602a3b
Add OMVSs to side menu
mandy-chessell Oct 11, 2023
a2914b1
Merge branch 'main' of https://github.com/odpi/egeria-docs into dev-dojo
mandy-chessell Oct 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions site/docs/introduction/key-concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 change and grow. There is also a 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 label 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.
Expand Down
4 changes: 4 additions & 0 deletions site/mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -573,6 +573,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
Expand Down