Versions Compared

Old Version 10

changes.mady.by.user Mandy Chessell

Saved on

compared with

New Version Current

changes.mady.by.user Mandy Chessell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: changed cluster to cohort

...

 


Since the OMAG Server does not have a metadata repository, all metadata is managed in other repositories and retrieved as required by OMRS:

  • The OMRS does not register with the metadata repository cluster cohort because it does not have a local repository and so there is no OMRS message exchange with other repositories.    However, the OMASs will receive events from the OMRS Topic to service their own In and Out Topics.
  • OMRS Connector calls are made from the OMAG Server to other repositories in the cluster in support of calls from the OMASs.
Figure 1: ABC tools deployed with the Access Layer of the OMAG Server

...

Figure 2 shows the OMAG Server with both the Access Layer and a local metadata repository enabled.  Now metadata from ABC is stored in its local OMAG Server's repository.  This is blended with metadata from other repositories by OMRS. With a metadata repository in play, ABC can operate independently and connect into the open metadata repository cluster cohort and is therefore now a open metadata Native.

...

 

The role of the repository proxy is to connect a proprietary metadata repository to the metadata highway and translate calls and messages between the XYZ proprietary formats and the open metadata formats.

Although the OMAG Server does not have its own repository enabled in this case, it is acting as a proxy for XYZ and so registers with the open metadata cluster cohort registry.  Hence you see the OMRS message exchange between the Repository Proxy and other repositories in the clustercohort.

Figure 3: XYZ tools and repository using the OMAG Server as a Repository Proxy

...