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

{ process name[ workflow name] –user username } | workspace name
deploy[ targets 
names]
comment 
comment-text

Arguments

Description

process name [workflow name]

The name of the project to create and use for the import. If qualified by the workflow argument, the project uses the specified workflow; otherwise, it uses the default workflow:

/Content Administration/editAssets.wdl

If importing into a VersionRepository, you must supply this argument or –workspace.

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.

If importing into a VersionRepository, you must supply this argument or –process.

This argument cannot be used with process.

deploy[ targets names]

Checks in and schedules assets for deployment. 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.

user username

The user who performs the import. If a secured repository is accessed for the import, this user’s authorization is checked.

This argument is required when the process argument is supplied, so the user can be identified as the process creator.

comment comment-text

Comment to use for each item when checking in imported data. The default is import. This comment is stored in each item’s version history. It should not contain spaces.

If you do not supply this argument, you must supply the nocheckinargument.

Note: When running startSQLRepository 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.

For complete details on startSQLRepository, see the ATG Repository Guide.

 
loading table of contents...