Using the Java Clients¶

Egeria's Java clients are primarily written for use by Egeria's runtime. They allow the View Server and governance servers to call the Open Metadata Access Services (OMASs), Administration Services, Platform Services and Server Operation Services. They wrap calls to Egeria's REST APIs. The aim is to provide a language-specific interface that manages parameter validation along with the marshalling and de-marshalling of the call parameters and responses to these services.

Many of Egeria's Java clients provide the mechanism to register a listener with a topic that an Egeria service is publishing notifications to. This removes all requirements for the consuming Java application to interact with the event bus technology.

Some of Egeria's Java clients also support the creation of digital resource connectors that can access the content of digital resources along with the metadata about the digital resource.

The Javadoc for these clients are:

• Asset Consumer OMAS
• Asset Manager OMAS
• Asset Owner OMAS
• Community Profile OMAS
• Data Manager OMAS
• Data Science OMAS
• Design Model OMAS
• Digital Architecture OMAS
• Digital Service OMAS
• Governance Program OMAS
• Governance Server OMAS
• IT Infrastructure OMAS
• Project Management OMAS
• Security Manager OMAS
• Software Developer OMAS
• Stewardship Action OMAS

Raise an issue or comment below