You can automate exporting rules and data to an archive by connecting to an active instance of Pega Platform from a web service. One request can export rules and data to one archive file from one system. You can export by product, application, or branch.
You must have a running Pega Platform instance to use the prpcServiceUtils tool.Property name | Value |
---|---|
export.exportToRepository | Indicates whether to export to a repository. The default is false , which exports to a file system. To export to a repository, set this to true . |
export.archiveName | When exporting to a file system, the path of the archive file to be created. |
export.repositoryName | When exporting to a repository, the name of the repository. |
export.async | Specifies whether to run the process in asynchronous mode or synchronous mode. The default, |
Property name | Value |
---|---|
export.productName | The name of the product to export. |
export.productVersion | The version of the product to export. |
Property name | Value |
---|---|
export.applicationVersion | The version of the application to export. |
export.applicationName | The name of the application to export. |
Property name | Value |
---|---|
export.branchName | The name of the branch to export. |
export.branchAppContext | The application context of the branch ruleset to export, for example, PegaRULES:07.10 |
Run the prpcServiceUtils.bat script or the prpcServiceUtils.sh script with the export option, for example:
prpcServiceUtils.bat export
Pega Platform downloads the exported archive file and saves the export log files to the logs directory. For more information about logs, see the PDN article Pega Platform logging using Log4j 2.