WSO2 Governance Registry - User Guide [ Documentation Index ]

WSO2 Governance Registry - User Guide

Symbolic links and Remote links

Symbolic links are much like hyper links to existing resources or collections in the local registry instance. When you access a symbolic link, the actual resource meta-data, community features, associations and the content can be vi wed from that location. If you make a change to the Symlink resource, the actual resource will get affected. These Symlink resources are soft links so that the actual resource does not keep a count for links from which it is referenced by. Instead the link shows a resource with a description saying that it couldn't make link to the original resource. Symbolic and remote links doesn't support versioning at the moment.

Remote links are created to mount a collection of a remotely deployed registry instance to the local instance. Any path/collection of the remote instance can be mounted at any point in the local instance. After mounting, the rest is very similar to symbolic links. You can work on the remote resource from the local instance.

Symbolic links and Remote links can be created in a similar way to adding a normal resource. Add resource drop down list contains options to add symbolic and remote links.

Figure 16 : Add Symbolic Link

When adding a symbolic link, you have to provide a name for the link and the path of an existing resource or collection which is being linked. It creates a link to the particular resource. The created symbolic link is shown by an icon with an arrow in the entries panel.

Figure 17 : Symbolic Link

Adding a Remote link is much similar to adding a symbolic link. You can mount a collection in a remotely deployed registry instance to your registry instance by adding a remote link. You can provide a name for the remote link in the name field, and choose the instance to which you are going to mount (Please refer the registry user guide to see how to configure the remote instances in registry.xml). You can give the path of the remote collection which you need to mount for the path field, or else the root collection will be mounted.

Figure 18 : Add Remote Link

After mounting the remote collection you can access and work on that collection from your local instance.