After you specify the ATG modules that you want to create tables for, the Database Initializer displays a list of the scripts you can run. As discussed above, this list can include DDLGen files, SQL script files, and repository template files.
The Database Initializer gathers the list of files by examining the manifest file for each selected module. Each manifest can use one or more of the following manifest attributes to specify the files for the Database Initializer:
Manifest Attribute | Description |
|---|---|
| A space-delimited list of the DDLGen files for the module |
| A space-delimited list of the repository template data files for the module |
| A space-delimited list of the SQL script files for the module |
| A space-delimited list of the files that will be unselected by default; this list should include only files that are also listed under one of the other |
The manifest file for each ATG module contains the necessary DBSetup entries for the module. For example, the manifest file for the DPS module includes this entry:
ATG-DBSetup-TableCreationPath: sql/dbsetup/ddlgen/user_ddl.xml sql/dbs
etup/ddlgen/logging_ddl.xml sql/dbsetup/ddlgen/logging_init.xml
When you create your own application modules, you can use these manifest attributes to specify the files that the Database Initializer can run. Be sure to associate each file with the correct manifest attribute. If, for example, you include a repository template file in the ATG-DBSetup-TableCreationPath list (rather than ATG-DBSetup-InitialDataPath, which is the correct attribute to use) the Database Initializer will attempt to run the file, but errors will result.
Note: You should make sure there are no conflicts or inconsistencies between the files you specify. For example, you should not include a DDLGen file and a SQL script that create the same tables.
Specifying Defaults
When the Database Initializer lists the available files for the selected modules, each filename appears beside a checkbox that controls whether that file should be run or not. By default, the checkbox for each file is selected, although it can be deselected by the user.
If you want certain files to be unselected by default, use the ATG-DBSetup-ExcludeFromDefaults manifest attribute to specify this. Each file listed under this attribute will be unselected in the Database Initializer, and a note will appear next to the filename indicating that the file is not recommended for most applications.
Note that the files must also be listed under one of the other DBSetup manifest entries as well, or the Database Initializer will ignore them. However, it is not necessary for all of them to be listed under the same entry. For example, the DBSetup entries for a module might look like this:
ATG-DBSetup-TableCreationPath: sql/dbsetup/ddlgen/workflow_ddl.xml sql/dbsetup/dd lgen/media_ddl.xml sql/dbsetup/ddlgen/user_profile_ddl.xml ATG-DBSetup-InitialDataPath: install/test-repository-data.xml install/test-file- repository-data.xml ATG-DBSetup-ExcludeFromDefaults: sql/dbsetup/ddlgen/media_ddl.xml install/test- file-repository-data.xml
