This documentation is for WSO2 Governance Registry 5.0.1. View documentation for the latest release.
||
Skip to end of metadata
Go to start of metadata

The Check-in Client is a tool used to replicate the resources tree in the Governance Registry into your file-system or to a dump file. Much like a version control system like Subversion, you can do checkout, check-in and update operations using this tool.

You can use the check-in client tool only for registry/repository use cases. Therefore, you cannot use it for governance scenarios.

When you are checking out, you can specify which path of the collection tree should checkout and where in the local file-system checkout to. And you can give more options to make it more flexible as described in the following sections.

The tool basically functions in two modes.

  • Replicating the Registry to a file structure (the Default):

In this mode the collections in the registry are mapped to directories/folders and non-collections are mapped to files. Once you checkout the registry to the file system, you can edit existing files, delete existing files or directories and add new files and directories and then you can check-in them back to the registry. This will enable you to navigate and work with more familiar file system. Specially, when you have to import lots of files to a collection, it will be easy to checkout that collection to a local directory, copy the required files to that directory and commit it back.

  • Replicating the Registry to a dump file (with -f option):

In this mode the resource tree (from a path specified) will be dumped to a single file. You are not supposed to edit these files. Rather you can use this mode to get backups/restore and possibly move a resource tree from one registry to another as an alternative to doing a remote mounting and moving.

The check-in client tool does not support the '&' and 'space' characters, and thereby, you will get errors when resources have these special characters. Therefore, the asset names, which are authorized need to be handled by the check-in client tool as well.

For more information about the Check-in Client see the following pages:

  • No labels