You can use startSQLRepository
to import repository data into versioned repositories. Before you run this script, format the repository data in an XML file that adheres to the SQL repository definition file syntax.
Note: When running startSQLRepository
on a third-party application server, configure the server to use an Oracle Commerce Platform data source and transaction manager, not your native application server’s data source and transaction manager.
Use the following syntax in order to import repository assets to a versioned repository:
startSQLRepository [-m
startup-module
]... [-s
server-name
]
-importinput
-
file
-repository
path
{project-spec
|
workspace-spec
} -comment
[arguments]
Importing to a project or workspace
The import operation must be directed to a project or to a workspace, as follows:
-project
name
[-workflow
name
] –user
username
–comment
text
-workspace
name
–comment
text
Note: After deployment targets are initialized, use –project
with startSQLRepository
instead of -workspace
. When –project
is used, assets are imported into a new project with the default or specified workflow. Users can then access this project and perform the tasks associated with its workflow.
Versioning arguments
The following arguments are specific to the versioning system.
Argument | Description |
---|---|
| The name of the project to create and use for the import. After running You must specify this option or Qualifiers: If qualified by the
If qualified by the - - |
| Specifies the workspace to use during the import operation, where The workspace is the area in the VersionManager where the import takes place. If the specified workspace does not exist, the system creates it. Importing into a workspace requires you to supply a check in comment through You must specify this option or |
| 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 |
| Comment to use for each item when checking in imported data. This comment is stored in each item’s version history. It should not contain spaces. |