|
Storing and managing arbitrary resources and collections
|
WSO2 Registry can be used to store resources with any type of content. It can be XML, text files, word documents, spreadsheets, images, zip archives or anything that is needed for the SOA deployment. These resources can be managed in a hierarchical manner using collections. Thus, the organization of resources and collections in the Registry is similar to the files and directories in a normal file system. |
|
Tagging, commenting and rating
|
WSO2 Registry provides a set of community features, which would help to categorize and evaluate resources by a authorized set of users. Tags can be used to associate arbitrary strings with resources, which provides additional description and categorization for those resources. Users can tag resources and search resources based on tags. Comments provide a method for associating descriptive opinions about resources. Positive and negative comments given by authorized users would be useful in determining the validity of resources. Ratings give a simple and quick way to evaluate resources by multiple users.
|
|
Managing users and roles
|
A complete set of user management functionalities is integrated with the WSO2 Registry. This allows to add/edit/remove users and roles, manage users by grouping them to roles and integrate external user stores. |
| Authentication and authorization on all resources and actions |
All the resources and collections in WSO2 Registry have a comprehensive authorization system. Read, write, etc permissions can be assigned for each resource per role basis. So it is possible to perform authorization actions like allow access to particular sections of the resource tree only for some users or to make some resources read only for some users. |
|
Resource / collection versioning and rollback
|
All the resources and collections in the Registry can be versioned. Resources are versioned automatically whenever a change is done to a resource. Users can create checkpoints of collections at any point in time, which will create versions of all sub collections and resources under those collections. Once versioned, users can browse previous versions of collections or resources, and rollback to previous versions if necessary. |
| Advanced search capabilities - tags, users, etc. |
All the resources and collections in the Registry can be searched using comprehensive criteria. These include, search by resource name, author, created or updated times, tags, comments, etc and any combination of these parameters.
|
| Built in media type support for common types (WSDL, XSD) |
WSO2 Registry provides special support WSDL and XSD resources. Whenever a WSDL or a XSD is added to the Registry, custom processing module is engaged to perform dependency analysis, etc and imports all the required dependencies to the Registry. |
|
Built in support for known repository types
|
Repositories of some SOA products including WSO2 WSAS and WSO2 ESB are provided as built in collection types. All required sub collections for those repositories will be automatically created upon adding a repository. This functionality can be extended to support any type of repository. |
|
Dependency management - maintain relationships between dependent resources
|
Resources or collections stored in the Registry can be associated according to the organization's requirements. These can either be dependencies or named custom associations. |
|
Pluggable media type handlers for handling custom media types
|
Users can define custom resource / collection types and specify custom behaviors for such resources using the handler based extension mechanism provided by the Registry. These custom processing pluggings can be written in Java and can be associated with any resource type.
This handler mechanism can be used to perform various resource type specific tasks including, validating configuration files, automatically define associations between related resources, confirming documents against predefined specifications, etc. |
|
Pluggable custom UIs for resource types
|
WSO2 Registry provides a plugin mechanism to add custom user interfaces for resources and collections. In addition to the default UIs provided by the Registry, users can write JSP based UIs to view and edit necessary resource types. This allows users to have better and more convenient views on their frequently used resources. |
|
Activity log and filtering support for the activity logs
|
All the common activities done by the users are tracked in the Registry with the user and the time. Users with necessary privileges can browse and search these activities to monitor the actions performed on the Registry. |
|
Atom Publishing Protocol (APP) support for reading/writing the data store remotely
|
WSO2 Registry exposes all its functionalities via APP based remote interface. Other applications can access the Registry remotely via this interface and perform all resource oriented operations. |
|
Subscribe to directories, comments, tags, etc. with any standard feed reader (Bloglines, Google Reader, etc)
|
APP based remote interface of the Registry provides Atom feeds for resources, collections, comments, etc. Users can subscribe to these Atom feeds and monitor the updates and activities in the Registry through feed readers. |
|
Web-based user interface
|
WSO2 Registry is shipped with a easy-to-use user interface targeting both technical and business users. All the functionalities of the Registry can also be performed and monitored using this built in web console. |
|
Support for deploying back end and front end (UI) in separate servers
|
WSO2 Registry back end server and the front end UI can be deployed in two separate servers. This gives the ability to manage multiple back end servers from a single UI server. |
