startSQLRepository
uses the following syntax:
startSQLRepository
arguments
xml-file[
...]
You can supply multiple XML files to startSQLRepository
, and it processes them in the order specified. For example, you can pass your full repository definition file together with a test file that uses the test operation tags to manipulate repository items, as shown in SQL Repository Test Example.
The following example loads an XML template whose configuration path name is /atg/test.xml
in a repository with a Nucleus address of /atg/userprofiling/ProfileAdapterRepository
:
startSQLRepository -m DPS
–repository /atg/userprofiling/ProfileAdapterRepository /atg/test.xml
The XML template file name is located in the application’s configuration path. For example, you can reference a file in the localconfig
directory as /
file-name
. You can also use a file with the same name as your repository’s existing definition file and omit the file name argument from the startSQLRepository
command. The startSQLRepository
script uses XML file combination to combine all files with the same name into a single repository definition. See the Nucleus: Organizing JavaBean Components chapter of the Platform Programming Guide.
For example, you can use startSQLRepository
to print all profiles in the Profile repository by including the following file in:
<ATG11dir>/home/localconfig/atg/userprofiling/userProfile.xml
<gsa-template> <print-item item-descriptor="user"/> </gsa-template>
You can use the startSQLRepository
script together with the test operation tags described earlier in this chapter to quickly test a query, or add, update, remove, or print an item.
General Arguments
The startSQLRepository
scripts take the following arguments:
Argument | Purpose |
---|---|
| Lists a module to load which contains the target repositories. Supply multiple
This argument must precede all others, including |
| The Oracle Commerce Platform instance on which to run this script. Use this argument when you have multiple servers running on your machine. This argument must precede all others except |
| Customizes the DDL for the SQL variant used by the specified vendor’s database software, where
|
| Outputs additional logging information. This option is equivalent to setting the |
| If the content you are exporting contains non-ASCII characters, use this option to specify an encoding such as 8859_1 or SJIS in which to save your content. |
| Exports items of one or more item descriptors to an XML repository definition file, where |
| Exports all items of all item descriptors in this repository to a file, where |
| To export data from more than one repository into the same file, use this option. This might be preferable to the |
| Exports all repositories to one file, where |
| An integer parameter that determines the maximum number of threads created to perform an export. The thread count is set to 10 by default. When exporting more than 500,000 records, it is recommended that you set this to a higher value. Note that as you increase this value the data source connection pool must be modified to create more connections by increasing the max property on |
| The XML file or DOM that contains the repository definition to import into the target repository, where input-file is a file created from running The path of |
| If you use this argument, this operation is not wrapped in a transaction. Important: Using a transaction for large operations can run into database limitations on transaction sizes and numbers of permitted row-level locks. Multi-threading occurs when exports are done with the |
| Sends all output from |
| Outputs a DDL (SQL) file for the XML templates in the repository to standard output. |
| Outputs a DDL (SQL) file for the XML templates in the repository to the specified file. |
| The Nucleus path of the repository. For example:
If you run If you use |
| By default, when you use one of the export arguments, all referenced item descriptors are automatically added to the list of item descriptors to be exported. If you use the |
| Outputs additional logging information, equivalent to setting |