You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The Enterprise OMRS Connector is an OMRS Connector implementation for federating calls to multiple metadata repositories and aggregating the results.  It uses the appropriate OMRS connector implementation for the target metadata repositories to issue the calls.  This means it can work with any type of metadata repository as long as that metadata repository supports an OMRS Connector.

The configuration for an Enterprise OMRS Connector is a list of connections that define the OMRS connectors it should use and the network addresses and user credentials it should use to connect to them. 

  • One of the connectors is nominated as the default OMRS connector. This connector is used for all Create calls for both entities and relationships and becomes the home repository for them.
  • Search and Query requests are propagated to all of its OMRS Connectors and each repository responds with what it knows.   The Enterprise OMRS Connector aggregates the responses, removing duplicate results due to reference copies of the metadata distributed in multiple repositories.
  • Update and Delete calls are propagated to all of its OMRS Connectors, but only the repository that home repository of the entity/relationship acts on the request.  The other repositories respond to say they are not the home repository.  This means that the Enterprise OMRS Connector can ensure that the metadata was really changed.  If the home repository is not available, or not accessible from this Enterprise OMRS Connector then the Update/Delete request is rejected.

 

 

 

 

 

 

  • No labels