This documentation is for WSO2 Governance Registry 5.1.0. View documentation for the latest release.
||
Skip to end of metadata
Go to start of metadata

WSO2 Governance Registry stores governance metadata and information on governance related entities. The metadata of a Web service describes what a client needs to know in order to interact with it. For example:

  • XML Schema - Describes the format and the content of the messages that are exchanged.
  • WSDL description - Describes the abstract operations, concrete network protocols, and endpoint addresses of the service.
  • WS-Policy - Describes the requirements and capabilities of the service such as reliable and transacted messaging.

Registry resources storing these information and/or metadata are known as Governance Artifacts.

With Service Metadata you can import most of the information which is separately stored in the WEB in to the Governance Registry and manage it as Governance Registry Resources.

Users are provided to add common service information through standard service metadata formats like using WSDL (Web Services Description Language) files, Policy file and schema files. User have to give the location of their WSDL, Policy or Schema files from local file system or as a URL, Governance Registry is importing those information in to Registry as resources. All the special resources are having their own Media Type which will be useful to users to handle them convenience way.

All service artifacts are going in to be in the directory governance based on the metadata type user is importing. As an example:

  • WSDLs are going to /_system/governance/wsdls/ directory.
  • Policies are going to /_system/governance/policies/ directory.
  • Schemas are going to /governance/schemas/ directory.

During the WSDL and Schema import we are providing WSDL validation (not supporting WSDL2), WS-I Validation and Schema Validation.

WSDL and Schema validation can optionally be disabled from the registry.xml.

WSDL and Schema validation requires a connection to the internet for the very first time, and will not work on systems without internet connectivity. Instead of just storing the required artifact in to the repository we do some other tasks specific to the metadata type and those information is mentioned on following metadata type based descriptions.

With Metadata Management users can manage the imported artifacts as resources management in the Governance Registry since all the information is stored as resource information inside the Governance Registry. In the "Metadata" list part, users can list imported Services, WSDLs, Schemas and Policies.

For Service resources users can always update the information given and dependencies between service resources, Schemas and WSDLs can be viewed. If user adds a given artifact in normal resource adding UI in Governance Registry, the same process for each artifact type is performed and a symbolic link to the resource is created in current location where you add the resource.

Deleting Governance Artifacts using the registry browser will lead to unexpected behavior in the artifact listing.

For more information see the following pages: 

You can attach one more life cycles to all governance artifact types listed below or any custom type. For instructions on life cycles, see Lifecycles.

  • No labels