4 2
Release 4.2 (July 2023)¶
Release 4.2 has a focus on runtime optimization and the start of the work to optimize the process of getting Egeria up and running in a new environment. This theme is continued in release 4.3.
OMAG Server Topic Configuration
Except when the no-topics
option is specified, the configuration document helper methods add a connection for both the InTopic and the OutTopic to each Open Metadata Access Service (OMAS) configuration irrespective of whether the particular OMAS supports these topics. This has no impact at runtime because the OMASs simply do not start topics they do not use. However, from a set-up point of view, it is misleading - and can result in an organization thinking they need to set up (and may be pay for) topics that are not use.
This release adds knowledge of whether an OMAS supports the inTopic and/or OutTopic to the AccessServiceDescroption class. This information is used by the configuration helper methods when setting up the access service configuration. For example, this is the list of topics for cocoMDS1
at release 4.2:
List of Topics used by cocoMDS1
egeria.omag.server.cocoMDS1.omas.assetcatalog.outTopic
egeria.omag.server.cocoMDS1.omas.assetconsumer.outTopic
egeria.omag.server.cocoMDS1.omas.assetmanager.outTopic
egeria.omag.server.cocoMDS1.omas.assetowner.outTopic
egeria.omag.server.cocoMDS1.omas.communityprofile.outTopic
egeria.omag.server.cocoMDS1.omas.dataengine.inTopic
egeria.omag.server.cocoMDS1.omas.datamanager.outTopic
egeria.omag.server.cocoMDS1.omas.digitalarchitecture.outTopic
egeria.omag.server.cocoMDS1.omas.governanceengine.outTopic
egeria.omag.server.cocoMDS1.omas.assetlineage.outTopic
Notice Data Engine OMAS supports an InTopic only. All of the others support just an OutTopic. Prior to this change, each OMAS had both an InTopic and an OutTopic configured.
OMAG Server Platform
- Fixed bug with http headers propagation feature.
- The name of the JAR file to start the platform is now
omag-server-platform.jar
in theplatform
directory of the distribution/install image. The previousserver-chassis-spring.jar
is still present in theserver
directory, to allow time for teams to migrate their operational scripts. However, this old jar file name is deprecated and will be removed in a future release. - The REST API calls to start and stop OMAG Servers have been moved from the Administration Services to the Platform Services. The original Java client and REST API calls are still available, but they have been deprecated and will be removed at a later date. This change is to separate the operational responsibilities from the configuration responsibilities. Prior to this change, the operational responsibilities where split between the Platform Services and the Administration Services.
New My Profile Open Metadata View Services (OMVS)
In this release we have added a new view service called My Profile OMVS to aid organizations writing user interfaces (UIs). My Profile OMVS returns information about the supplied user's profile. It is intended to supply information about the logged-on user.
Open Metadata Types
- The CollectionMembership relationship has new properties stewardTypeName, stewardPropertyName, userDefinedStatus and notes to improve ability to manage collection membership.
Raise an issue or comment below