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.

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

Update view service configuration #886

Merged
merged 2 commits into from
Jan 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@

# Configuring the OMAG Server Platform

The [OMAG Server Platform](/concepts/omag-server-platform) is a JVM process that includes a Tomcat web server and uses [Spring Boot :material-dock-window:](https://spring.io/){ target=spring } to support its REST APIs. The Egeria code is in the centre of this and, through configuration, starts up plug-in components called [connectors](/concepts/connector).
The [OMAG Server Platform](/concepts/omag-server-platform) is a JVM process that includes a Tomcat web server and uses [Spring Boot :material-dock-window:](https://spring.io/){ target=spring } to support its REST APIs. The Egeria code is in the centre of this. Through configuration, Egeria starts up plug-in components called [connectors](/concepts/connector) and coordinates calls to them to manage and exchange metadata.

![OMAG Server Platform Onion](omag-server-platform-onion.svg)
> High-level structure of the OMAG Server Platform

The behaviour of these components is influenced by:
The behaviour of the OMAG Server Platform components is influenced by:

* The command line properties passed when the platform is started.
* The contents of the `application.properties` file (or their environment variable equivalents).
Expand Down
Loading