exportRepository exports the contents of one or more standard repositories to a .jar data file. You typically use this tool together with importRepository, which imports the exported data into a standard or VersionRepository.
Note: When running exportRepository on a third-party application server, you must configure the server to use an ATG data source and transaction manager, not your native application server’s data source and transaction manager.
Syntax
You run exportRepository from <ATG9dir>/home/bin as follows:
exportRepository [–m startup-modules] [-s server-name]
–file output-file { -all | -r repository-list } [-batchSize size]
Command-line help
To obtain command-line help on syntax usage, type:
exportRepository -help
Required Arguments
Argument | Description |
|---|---|
| Specifies the target output file for the exported content. The file path can be absolute or relative to the current directory. |
| Specifies to export the contents of all repositories registered in the repository registry service, located in Nucleus at You must specify this option or |
| Specifies the absolute Nucleus component path of one or more source repositories, where You must specify this option or |
For example:
exportRepository –m Catalog –file /users/joe/CatalogExport.jar –r /myApp/Catalog
Optional Arguments
Argument | Description |
|---|---|
| Lists a module to start for the export process, which contains the source repositories of the data to export. Supply multiple This argument must precede all others, including |
| The ATG instance on which to run this script. Use this argument when you have multiple servers running on a machine. If specified, this argument must precede all others except |
| The number of items to query at one time. The larger the specified number, the faster the export but the greater the amount of memory required. The default is 1000. Specify -1 to export all items in a single batch. |
Print Arguments
See Print Arguments under importRepository.
