limrepo import

Note: For instructions on installing and running the Administration Utility, see Getting Started with the Administration Utility.
The limrepo import command imports named resources (such as named tables) from a local file system into the Spectrum Spatial repository. You must have the Location Intelligence Module installed to use this command.
When importing, you must point to the same folder or directory you exported to previously. For example, if you run limrepo export --s /Samples/NamedTables --o C:\export, the tool creates C:\export\Samples\NamedTables\WorldTable, and so on for each named table under the NamedTables folder or directory. Resources are exported with their full repository paths in the target folder. Running limrepo import --s C:\export then imports WorldTable back to /Samples/NamedTables/WorldTable.
Note: The limrepo import command will always recursively import all folders, including empty ones.

After performing an import, in many cases, you will need to adjust the named connections to point to their new path using Spatial Manager. For example, if your Native TAB files were installed on “C:\myfiles” in your test instance and the same files are installed on “E:\ApplicationData\Spectrum\Spatial\Spring2016” then that connection would have to be corrected in Spatial Manager after import. See the Utilities section of the Spectrum Spatial Guide for instructions on using Spatial Manager to edit a named connection.

Note: If you are using limrepo import to restore service configuration files that you exported from a pre-12.0 version of Spectrum™ Technology Platform, the files will automatically be modified to be compliant with version 12.0 and later (for example, the repository URLs will be removed).

Usage

limrepo import --s SourceFilePath
Note: To see a list of parameters, type help limrepo import.
Required Argument Description
Yes --s or source

Specifies the path to the resource or a folder on the local file system that is to be imported. This must be the root folder of a previous export on the local file system.

No --q or --quiet Disables the display of the resources copied during the import; that is, operates in quiet mode.

If the flag is specified, the default value is true. If the flag is not specified, the default value is false.

No --u or --update

Specifies whether to overwrite existing resources if resources with the same name are already on the server.

true
If there is a resource on the server with the same name as a resource you are importing, the resource on the server will be overwritten. This is the default setting if the flag is not specified or if the flag is specified without a value.
false
If there is a resource on the server with the same name as a resource you are importing, the resource will not be imported.
No --f or --fullpaths

Prints the full source and output paths.

If the flag is specified, the default value is true. If the flag is not specified, the default value is false.

No --c or --continueonerror Continues with the import if an error occurs.

If the flag is specified, the default value is true. If the flag is not specified, the default value is false.

No --a or --acl Preserves any previously exported permissions and merges them with existing permissions when importing resources. An access control list (ACL) indicates the operations each user or role can perform on a named resource, such as create, view, modify, or delete.

For example, a user has read and write permissions on a resource when exporting. If the user only has read permissions on the resource when importing, write permission will be granted again after the import finishes successfully.

Conflicting permissions cannot be merged and will be ignored. ACL entries for users and roles that do not exist in the target repository are also ignored.

If the flag is specified, the default value is true. If the flag is not specified, the default value is false.
Tip: When using this flag, the user on the server you exported from should also exist on the server to which you are importing. For example, you have "testuser" with access control settings and export the resources with ACL from one server, then import those named resources to another server that does not have "testuser". In this case, named resources will be uploaded but not the ACL.

Example

This example imports the named resources from C:\myrepository\samples on your local file system.

limrepo import --s C:\myrepository\samples