Generating a DDL file of schema changes that are referenced from an archive file
The import process can apply those schema changes from an archive automatically, or you can generate a DDL file of schema changes from the command line and apply the changes manually.
-
Configure the common properties of the
prpcUtils.propertiesfile.Property name Value pega.jdbc.driver.jarPath to the database driver .jar file. pega.jdbc.driver.classThe database driver class. pega.database.typeDatabase vendor type. pega.jdbc.urlURL of your database. pega.jdbc.usernameDatabase user name. pega.jdbc.passwordDatabase password. rules.schema.nameIf you use a split schema, the value for the rules schema name. If you do not use a split schema, the value for the schema name. data.schema.nameIf you use a split schema, the value for the data schema name. -
Configure the Generate DDL properties of the
prpcUtils.propertiesfile.Property name Value schema.archive.inputThe full path to the archive file that contains the schema definition. To specify multiple input files and generate multiple DDL files, use commas to delimit the list. schema.generated.outputThe full path to the output directory for the DDL files. For example, C:/Output. - Save and close the
prpcUtils.propertiesfile. - Run the
prpcUtils.batorprpcUtils.shscript with the generateDDL option, for example:prpcUtils.bat generateDDL - Give the DDL file to the database administrator to apply to your database.
Previous topic Importing rules and data by using a direct connection to the database Next topic Migrating products and applications from the command line