Chandana Napagoda's Blog

Please refer my previous post which explain about  Configurable Governance Artifacts in WSO2 Governance Registry . Once you have added an RXT, it will generate HTML based List and Add view. Also it will be deployed as an Axis2 based service with CRUD operations. For example, when you upload contact.rxt, there will be a Contact Service exposed with CRUD operations. Using provided CRUD operations, external client applications(php, .net,etc) can perform registry operations. Below is an example CRUD operations provided for Contact RXT which we created in my previous post( RXT Source ). addContact - create an artifact in the type Contact . getContact - retrieve an artifact in the type Contact . updateContact - update an artifact in the type Contact . deleteContact - delete an artifact in the type Contact .  getContactArtifactIDs - get all the artifact ID s of artifacts in the type Contact . To retrieve WSDL of the above service, we need to disable "HideAdminServiceWSDLs"

Configurable Governance Artifacts is one of many well-defined extension points supported by the WSO2 Governance Registry . This is also known as Registry Extensions Types. This allows you to define own metadata models other than the default metadata model which is shipped with the product. This will support modeling any type of asset according to the user requirements. When deploying Configurable Governance Artifacts in WSO@ Governance Registry, it creates a web service which supports CURD (Create, Update, Retrieve, Delete) operations. So using external web services, client application users can consume them. Below are the main elements in RXT configuration. artifactType element artifactKey element storagePath element nameAttribute element namespaceAttribute element menu element ui element relationships element Using above basic model, you can create/modify RXTs based on your requirement. Let’s go through a sample RXT file and understand requirements of each