Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A collection includes a set of a child collections and resources. If you select a collection in the registry, the Entries panel opens with details of the child collections and resources of the collection. For example,

Image RemovedImage Added

The Info and Actions links in the Entries panel provide the following information:

Links in the Entries panelDescription
Add CollectionSee  Adding child collections.
Add ResourceSee Adding and Editing resources.
Create LinkSee Entries and Content#Adding linksContent (Copy).
Info
  • Feed - Generate a RSS feed for the resource
  • Rating - Ratings of the resource
  • Media type -
    Anchor
    media
    media
    Each collection or resource created and stored on the repository has an associated media type. If you leave the media type unspecified, it takes the default value. There are two main ways to configure media types for resources.
    1. Use a one-time configuration, by modifying the mime.types file found in the server configuration directory. Done just once before the initial start-up of the server. This method does not apply to collections. The only way to configure media types for a collection is using the second method.
    2. Use the management console as described when adding a collection and a resource.

    Initially, the system contains media types defined in mime.types file. They are available for resources and a set of default media types is available for collections.

    Info

    Human-readable media types have shorter names in place of MIME names (for example, WSDL is used instead of application/wsdl+xml). This is achieved by introducing a new file as <PRODUCT_HOME>/repository/conf/mime.mappings . For more information, see Configuring Registry Files section in WSO2 Governance Registry documentation.

    You can manage media types for resources by editing the properties of /system/mime.types/index collection. This collection contains two resources: collection and custom.ui. To manage media types of collections and custom user interfaces, edit the properties of these two resources.

Actions

Allows you to rename, move, copy or delete a resource/child collection.
Image Removed Image Added

Info

You cannot move/copy resources and collections across registry mounts if they have dependencies or associations. You can only move/copy within a mount. For more information on mounts, read WSO2 Governance Registry documentation: Remote Instance and Mount Configuration Details.

Info

These options are not available for all resources/collections.

...

  1. Select a collection. In its detailed view, you can see the  Entries panel with details of child collections and resources it has.
  2. In the Entries panel, click Add Resource.
  3. In the Add Resource page that opens, select one of the following methods:
    Table of Contents
    maxLevel4
    minLevel4

    Uploading content from file

    Allows you to create a resource by fetching its content from a specified file (e.g., XML, WSDL, JAR). For example,

    Image RemovedImage Added

    Importing content from URL

    Allows you to fetch a resource from a specified URL path. For example,

    Image RemovedImage Added

    Creating text content

    Allows you to write the content in the UI itself, using either the Rich Text Editor or Plain Text Editor. For example,

    Info

    You can add external links (hyperlinks) as resources in the registry. To add such a link, create a text resource with the media type application/vnd.wso2-hyperlink and specify the URL as the resource's content.

    Creating custom content

    Allows you to create your own type of content with a specified media type. For example, to add a user profile to the registry, create custom content with the media type application/vnd.wso2-profiles+xml and provide the user name. For example,

...