Merge branch 'main' of github.com:odpi/egeria-docs into asset-catalog…

…-tech-preview
odpi · Jun 20, 2023 · 5731953 · 5731953
2 parents fdda272 + b88b495
commit 5731953
Show file tree

Hide file tree

Showing 96 changed files with 9,291 additions and 3,096 deletions.
diff --git a/site/docs/concepts/index.md b/site/docs/concepts/index.md
@@ -294,6 +294,7 @@
 - [Personal Message](/concepts/personal-message)
 - [Personal Note](/concepts/personal-note)
 - [Personal Roles](/concepts/personal-roles)
+- [Platform Chassis](/services/platform-chassis)
 - [Platform Metadata Security Connector](/concepts/platform-metadata-security-connector)
 - [Platform Security](/features/metadata-security/overview)
 - [Platform URL Root](/concepts/platform-url-root)
@@ -342,7 +343,7 @@
 - [Security Officer OMAS](/services/omas/security-officer/overview)
 - [Security Tags](/concepts/security-tags)
 - [Server Capabilities](/concepts/software-capability)
-- [Server Chassis](/services/server-chassis)
+- [Server Chassis](/services/platform-chassis)
 - [Servers for Governance](/concepts/governance-server)
 - [Server Name](/concepts/server-name)
 - [Server Security](/features/metadata-security/overview)

diff --git a/site/docs/concepts/omag-server-platform.md b/site/docs/concepts/omag-server-platform.md
@@ -19,7 +19,7 @@ Each server is configured to support specific set of Egeria services and connect
 
 ## Deployment of the OMAG Server Platform
 
-Once a configuration document is defined, the OMAG Server can be started and stopped multiple times by the admin services server instance operations.
+Once a configuration document is defined, the OMAG Server can be started and stopped multiple times via the [Platform Services](/services/platform-services/overview).
 
 The OMAG Server Platform can host multiple OMAG Servers at any one time and a single server may be active on multiple platforms. The choices are as follows:
 
@@ -30,8 +30,7 @@ The OMAG Server Platform can host multiple OMAG Servers at any one time and a si
 - **B** - Multiple OMAG Servers are hosted on the same OMAG Server Platform. The OMAG Server Platform routes inbound requests to the right server based on the server name specified in the request URL. The servers may all be of the same type offering the same services but to different groups of people or be a set of collaborating servers of different types consolidated onto the same platform.
 - **C** - Multiple copies of same server instance each running on different platforms to provide high availability and distribution of workload (horizontal scalability).
 
-The OMAG Server platform is included in the [Egeria Distribution TAR file](https://github.com/odpi/egeria/tree/main/open-metadata-distribution/open-metadata-assemblies)
-which can be installed on your machine by following the [Installing Egeria Tutorial](/education/tutorials/building-egeria-tutorial/task-installing-egeria).
+The OMAG Server platform is included in the [Egeria Distribution TAR file](https://github.com/odpi/egeria/tree/main/open-metadata-distribution/open-metadata-assemblies) which can be installed on your machine by following the [Installing Egeria Tutorial](/education/tutorials/building-egeria-tutorial/task-installing-egeria).
 
 ??? education "Further reading"
 

diff --git a/site/docs/concepts/omag-subsystem.md b/site/docs/concepts/omag-subsystem.md
@@ -11,15 +11,15 @@ The [OMAG Server Platform](/concepts/omag-server-platform) is a collection of su
 
 Fixed services that are always present in the platform:
 
-- [Server Chassis](/services/server-chassis) provides the main class of the OMAG Server Platform that manages the start up and shutdown of a platform instance.
+- [Platform Chassis](/services/platform-chassis) provides the main class of the OMAG Server Platform that manages the start up, and shutdown of an OMAG Server instance.
 
 - [Administration Services](/services/admin-services/overview) support the configuration and operation (such as starting and stopping) of [OMAG Servers](/concepts/omag-servers).
 
 - [First Failure Data Capture (FFDC) services](/services/ffdc-services) support the capture of diagnostics.
 
 - [Multi-tenant Services](/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](/services/platform-services/overview) retrieves information about a running platform instance and its associated servers.
+- [Platform Services](/services/platform-services/overview) retrieves information about a running platform instance and its associated servers. Also able to start and stop servers as well as shutdown the platform itself.
 
 - [Open Metadata Repository Services (OMRS)](/services/omrs) for supporting access to metadata stored in metadata repositories and the exchange of metadata between repositories via an [open metadata repository cohort](/concepts/cohort-member). The repository services are further divided into [OMRS subsystems](/services/omrs/#omrs-subsystems) that can be activated independently.
 

diff --git a/site/docs/concepts/repository-proxy.svg b/site/docs/concepts/repository-proxy.svg
diff --git a/site/docs/connectors/Romania 2023 .drawio b/site/docs/connectors/Romania 2023 .drawio
@@ -0,0 +1,13 @@
+<mxfile host="app.diagrams.net" modified="2023-04-24T13:29:42.853Z" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36" etag="WYD9g_u_liZ34SErABoS" version="21.2.1" type="device">
+  <diagram name="Page-1" id="ucmS4EFgsMoZa6qrljXS">
+    <mxGraphModel dx="1242" dy="646" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0">
+      <root>
+        <mxCell id="0" />
+        <mxCell id="1" parent="0" />
+        <mxCell id="mf9yhnzCPZdJebNj-6fK-1" value="" style="rounded=1;whiteSpace=wrap;html=1;" vertex="1" parent="1">
+          <mxGeometry x="350" y="300" width="120" height="60" as="geometry" />
+        </mxCell>
+      </root>
+    </mxGraphModel>
+  </diagram>
+</mxfile>
diff --git a/site/docs/connectors/repository/hms/overview.md b/site/docs/connectors/repository/hms/overview.md
@@ -197,12 +197,31 @@ higher level concepts called catalogs that hold databases.
 
 #### Classification Types
 
-| HMS concept                  | Description                                                     | Egeria open Classifation type | Comments                                                           |
-|------------------------------|-----------------------------------------------------------------|-------------------------------|--------------------------------------------------------------------|
-| Hive table Type              | if this is VIRTUAL_VIEW then this is a view rather than a table | CalculatedValue               | The RelationalTable is classified with CalculatedValue for a view |
-| for columns fieldSchema Type | This is the type of the Hive column (e.g. String)               | TypeEmbeddedAttribute         | This contains the type of the column                               |
-| for tables n/a               | n/a                                                             | TypeEmbeddedAttribute         | The type of the Table                                              |
-
+| HMS concept                  | Description                                                     | Egeria open Classification type | Comments                                                           |
+|------------------------------|-----------------------------------------------------------------|---------------------------------|--------------------------------------------------------------------|
+| Hive table Type              | if this is VIRTUAL_VIEW then this is a view rather than a table | CalculatedValue                 | The RelationalTable is classified with CalculatedValue for a view |
+| for columns fieldSchema Type | This is the type of the Hive column (e.g. String)               | TypeEmbeddedAttribute           | This contains the type of the column                               |
+| for tables n/a               | n/a                                                             | TypeEmbeddedAttribute           | The type of the Table                                              |
+
+
+## Using with the Hive Metastore listener
+
+The Hive metastore listener runs in the HMS process as a HMS listener. When HMS tables are added, dropped or 
+altered then appropriate Egeria events are issued. It sends the 'granular events. In this way the Egeria cohort members are kept up to 
+date as the HMS metadata changes.
+
+The HMS connector needs to have run prior to the listener, so that the Egeria cohort already has existing entities that 
+the HMS tables can be associated with. The listener needs to be configured as the same cohort member as the connector.
+
+| HMS configuration parameter         | Description                                                           |
+|-------------------------------------|-----------------------------------------------------------------------|
+| EgeriaListener.metadataCollectionId | This is the metadata collection id of the HMS connector               |
+| EgeriaListener.serverName           | This is the server name of the HMS connector                          |
+| EgeriaListener.organisationName     | Organisation name to match  the HMS connector                         |
+| EgeriaListener.qualifiedNamePrefix  | Qualified name prefix the HMS connector                               |
+| EgeriaListener.events.kafka.topicname  | The cohort topic name that the HMS connector writes to                |
+| EgeriaListener.events.kafka.clientId  | The client ID of the HMS connector                                    |
+| EgeriaListener.events.kafka.bootstrapServerurl  | The bootstrap server name for the Kafka defined for the HMS connector |
 
 
 You may also find these links in the Egeria documentation useful: