Here are some examples of using check-in client.
Here the Check-in Client is running in windows. If you are on Linux, you have to use
checkin-client.sh instead. See Running Check-in Client.
For the username and the password, the default values "admin" "admin" are used. Please, replace them with your username and password when you are trying these commands.
Command to run
Checking out a root collection from a remote registry running on https://localhost:9443 to the current working directory.
For tenant users use https://localhost:9443/t/tenant_domain where tenant_domain is the domain name of the tenant.
Checking in a collection from the current working directory back to the registry which it check out (This command is independent of whether it is checked out from a local registry or a remote registry. It will anyway commit it back to where it is checked out from).
Checking in a collection from given working directory (path) back to the registry which it check out (This command is independent of whether it is checked out from a local registry or a remote registry. It will anyway commit it back to where it is checked out from).
Dump a remote registry "/path" collection to a file.
Notice the additional
It is recommended that you check out from child collection paths (e.g.
Restore a dump file to a remote registry "/path" collection.
Provide the URL with the
Copy entire tree from "
This can be done through the
Copy entire collection from Governance Registry 1 (runs on 9443 port) to Governance Registry 2 (runs on 9444 port) using the check-in client.
This method cannot be used to restore the root of the registry. To restore the root, use the check-in client dump to file system method.
|Add the media type when checking in a file.|