In the navigator, under Registry, click Resources.
Figure 1 : Registry User Interface
Figure 6 : Permissions
To assign permissions to users or roles follow the steps given below:
Users can enter as many tags as they like provided individual tags are separated by commas and a given tag is not used by the same author to identify the same resource repeatedly.
Figure 7 : Tags
Users can perform a "tag" search using the search block. To perform an advanced search, in the navigator, under Registry, click Search.
Figure 8 : Search
Users can either rate or view ratings made by others using the ratings block.
Figure 9 : Ratings
Users can either comment or refer comments made by others using the comments block.
To add a new comment:
1. select the "Add Comment" located on the comments block
2. enter comment in the text box provided
3. click the 'Add' button to continue.
Figure 10 : Comments
Resources or collections stored in the Registry can be associated according to the user's requirements. These can either be dependencies or named custom associations.
Each collection or resource that you create and store on the repository has an associated media type. However, you also have the option to leave this unspecified enforcing the default media type. There are two main ways in which you can configure media types for resources.
The first method is by means of a one-time configuration which can be done by modifying the mime.types file found in the server configuration directory. This can be done just once before the initial start-up of the server. The second method is to configure the media types via the server administration console.
Managing media types for resources can be done via the server administration console, by editing the properties of the /system/mime.types/index collection. This collection contains two resources, collection and custom.ui. To manage media types of collections and custom user interfaces, you need to edit the properties of these two resources.
WSO2 Governance Registry only allows you to upload one resource at a time. However, a WSDL file can have several imported resources (Schemas and WSDLs) that are required to be uploaded all at once. To address this, you now can create a zipped-archive of the WSDL file you want to upload including the imported Schemas and WSDLs placed in a proper directory structure. As an example, let's upload the WSDL file found at http://184.108.40.206/SoapWsdl_BaseDataTypes_XmlFormatter_Service_Indigo/BaseDataTypesDocLitB.svc?wsdl
Save the WSDL to your local file system (by the name
to a folder named, myWSDL.
Step 2: You need to open the WSDL file and identify the directory structure of the imports. The WSDL file we use has absolute Schema locations. Therefore, we first of all need to make them relative.
We will replace the Schema locations to reflect a relative directory structure. Replace
schemas/xsd1.xsd. Similarly replace the other two locations as,
Create a folder named schemas inside the folder myWSDL.
Now, save the three Schemas, within the schemas folder. Save
Step 5: You then need to open each Schema file and fix the locations of the imported Schemas. The Schema files we have uses absolute Schema locations, and we need to make them relative as well.
Open xsd1.xsd, and replace
xsd2.xsd. Then, open xsd2.xsd and do the same changes.
Step 7: Save and close the WSDL and Schema files, if you haven't done so. Then, create a zip archive of the folder myWSDL. Lets say you named it myZIP.zip. Now change the extension of this file from .zip to .gwa. Your file should now have the name, myZIP.gwa.
Step 8: Upload the myZIP.gwa to the registry, through the 'Browse' sub menu under the 'Resources' menu. Now, you should see your WSDL listed under the 'WSDLs' section under the 'List' sub-menu of the 'Metadata' menu.