Versioning Arguments

The following arguments determine how importRepository interacts with the versioning system. Typically, you omit these arguments and use default versioning-related settings instead.

process name [ workflow name ] | workspace name
deploy[ targets names] | batchsize size
checkinComment comment-text
username name
nocheckin
noworkspace
versionManager path

Versioning argument

Description

process name [workflow name]

Specifies the name of the project to create. If qualified by the workflow argument, the project uses the specified workflow; otherwise, it uses the default workflow:

/Content Administration/editAssets.wdl

This argument is available only if the Publishing module is included in your application. If a process is created, it is not checked in unless deploy is also specified.

This argument cannot be used with workspace.

workspace name

Specifies the workspace of an existing project to use during the import operation, where name has no embedded spaces and is unique among all workspace names.

The workspace is the area in the VersionManager where the import takes place. If the specified workspace does not exist, the system creates it.

The default workspace is import. This argument cannot be used with process.

deploy[ targets names]

Directs deployment of assets. If qualified by the targets argument, assets are deployed only to names, where namesis a comma-delimited list of targets; otherwise, assets are deployed to all targets.

This argument cannot be used with batchSize.

checkinComment comment

Comment to use when checking in imported data. The default is import.

username name

Username to use when checking in imported data. The default is importRepository.

nocheckin

Specifies that the import should not check in imported data. This allows use of the workspace for multiple imports or other versioning operations, so all assets can be checked in at the same time.

noworkspace

Specifies that the import should not use the versioning system. Use this argument to import data into unversioned repositories.

versionManager path

Component path of version manager to use for versioned imports. Use this argument only if the version manager runs in a non-standard location.

Note: After deployment targets are initialized, use process with importRepository instead of workspace. If you use the workspace flag after target initialization, the importRepository tool imports the assets using the specified workspace into the main branch only, and not to any target branches. Consequently, later deployments cannot deploy these imported assets as they do not exist in the target branches.

By contrast, when you use process, assets are imported into a created process, which advances the assets through the specified workflow and performs the appropriate merges.

If using workspace after initialization causes problems, delete the target through the ATG Business Control Center’s Admin Console interface and reinitialize it.

 
loading table of contents...