Exporting rules and data by using a direct connection to the database
To automate exporting rules and data by connecting directly to the database, complete the following steps. This method is most commonly done for a stopped instance.
-
Configure the common properties of the prpcUtils.properties file.
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. -
Do one of the following actions:
-
To export by product, specify the pzInsKey of the Rule-Admin-Product:
Property name Value export.archive.productKeyThe pzInsKey of the product rule ( Rule-Admin-Product ) to be exported. export.product.dataOnlytrueorfalse. The default value,false, exports rules, data, and database changes (DDL). Set this totrueto export only the data. -
To export by application, specify the application name and version:
Property name Value export.application.contextThe application name and version to export, for example: PegaRULES!07.10 -
To export by class name, specify these values:
Property name Value export.classes.includedA comma-separated list of the classes to be included. To export by classes, you must specify either export.classes.includedorexport.keys.file; you cannot specify both.export.included.descendentOptional: trueorfalse. The default value,true, exports the class and its descendants. Set this tofalseto export only the parent class.export.classes.excludedOptional: A comma-separated list of classes that you want to exclude. export.excluded.descendentOptional: trueorfalse. The default value,true, exports the class and its descendants. Set this tofalseto export only the parent class.export.startVersionOptional: For rule-resolved instances of Rule-, the minimum ruleset version. For example, 07-10export.endVersionOptional: For rule-resolved instances of Rule-, the maximum ruleset version. For example, 07-10-31export.keys.fileThe full path to the file name specifying the values of pzInsKey to be exported, containing one pzInsKey per line. You must specify either export.classes.includedorexport.keys.file; you cannot specify both.
-
- Save and close the prpcUtils.properties file.
- Run the prpcUtils.bat script or the
prpcUtils.sh script with the export or exportRAP option. For
example:
- If not exporting by product, enter this option:
prpcUtils.bat export - If exporting by product, enter this option:
prpcUtils.bat exportRAP
Optional: Pass one or more arguments.
prpcUtils script argument Value connPropFileThe full path to the connection.properties file that includes information for multiple targets. driverClassYour JDBC driver class (example: oracle.jdbc.OracleDriver). driverJARLocation of your JDBC .jar file. dbTypeDatabase vendor type (mssql, udb, oracledate, postgres, db2zos). dbURLJDBC URL to the database. dbUserDatabase user name. dbPasswordDatabase password. archivePathFull path to the archive to be imported or exported. propFileThe full path to the properties file, to override the default prpcUtils.properties. hfixActionIf manageHotfixes is selected, sets the hotfix operation. Valid values are commit,rollback,generateDDL,install, andscan.rulesSchemaThe rules schema. dataSchemaThe data schema. noFailOnErrorSet to trueorfalse. When enabled, instances that fail to import are skipped and import continues instead of failing.UPega user name. PPega password. accessGroupAccessGroup in which the Rule-Declare-Index of the classes being exposed exists. Applicable for the expose utility if --U or --P are not provided. - If not exporting by product, enter this option: