prpcServiceUtils Properties and Arguments
prpcServiceUtils Properties and Arguments
prpcServiceUtils Properties and Arguments
arguments
The properties in the prpcServiceUtils.properties file and the arguments to
the prpcServiceUtils.bat script or prpcServiceUtils.sh script control service-enabled
application distribution. The following tables define each property and argument.
If you need to perform these operations by using a direct connection to the database,
use the prpcUtils tool. For more information about the prpcUtils tool, see prpcUtils
properties and arguments.
Use the properties file to set property values for reuse to minimize errors in entering
commands.
Use the command-line arguments to augment or override values in the property file,
for example, to customize one script action. The use of these arguments is optional.
Each argument should be preceded with two hyphens ( --).
pega.rest.server.url The URL for the REST service, specified in the following format:
http://<hostname>:<port>/<context>/PRRestService/<tenant hash>
For example:
http://myhost:8080/prweb/PRRestService
Include the tenant hash only for multitenant systems.
pega.rest.username The operator name on the target system with access to REST services.
Property name Value
export.exportToRepositor Indicates whether to export to a repository. The default is false, which exports to a file system
y
export.archiveName When exporting to a file system, the path of the archive file to be created.
export.async Specifies whether to run the process in asynchronous mode or synchronous mode. The default
that you can use later to check the job status. When this value is false, the process starts imm
synchronous or asynchronous depends on the type of script you are writing.
In addition to the general properties, you must also configure properties for exporting
by product, application, or branch.
Export product
Property name Value
Export application
Export branch
export.branchAppContext The application context of the branch ruleset to export, for example, PegaRUL
To specify the data for populating the new column, use the include and exclude classes
properties. For example, if you include Rule- with descendants and exclude Rule-File-
with descendants, Pega Platform processes all descendant classes of Rule-, except
rules in Rule-File-.
Classes to include
expose.includedClasses Comma-separated list of classes to include in the column. To specify a range of keys from
Property name Value
expose.includeDescendents Optional: Set to false to exclude descendants of included classes. The default value, true
Classes to exclude
expose.excludeDescendents Optional: Set to true to exclude descendants of excluded classes. Setting the value to
expose.startKey The minimum value for pzInsKey. The tool exports data equal to or greater than this value.
expose.endKey The maximum value for pzInsKey. The tool exports data equal to or less than this value.
expose.startDate The minimum value for pxCreateDateTime. The tool exports data equal to or greater than th
expose.endDate The maximum value for pxCreateDateTime. The tool exports data equal to or less than this v
expose.commitRate The number of data instances processed with each database commit to balance memory usage and pe
most environments.
expose.async Specifies whether to run the expose operation in asynchronous mode and queue the request. Default
import.importFromRepository Indicates whether to import from a repository. The default is false, which
repository, set this to true.
import.archive.path When importing from a file system, the relative path to the archive from th
the path is a folder, the tool processes all archive files in that folder.
import.repositoryName When importing from a repository, the name of the repository. The reposit
import.artifactType When importing from a repository, the artifact type you are importing. The
branch, component, rulesetversion.
import.archivePath When importing from a repository, the full path to the archive file. The arch
example: MyApp_01.01.01/ExportWizard/myFile.zip
import.nofailonerror true skips instances that fail to import and continues after an import failu
fails.
import.commitRate The number of data instances processed with each database commit to ba
default of 100 is sufficient for most environments.
import.compileLibraries true or false, specifying whether to compile libraries after import. The de
import.allowImportWithMissingDependencie true or false, specifying whether to allow the import to continue even if t
s
default is false.
import.codesetName Optional: The name of the code set to receive the Java .class files.
import.codesetVersion Optional: The code set version.
import.bypassSchema Optional: Specify whether to apply database schema changes during the im
applied the schema changes manually, set this to true.
import.async Specifies whether to run the process in asynchronous mode or synchronou
which returns a job ID that you can use later to check the job status. When
immediately and waits until completion. The choice of synchronous or asyn
writing.
Hotfix scan
hotfix.operation scan
hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system que
job status. A value of false executes the operation synchronously.
hotfix.operation generateDDL
hotfix.dlFilePat Comma-delimited list of hotfix package download (DL) file names and paths.
h
hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system queu
job status. A value of false executes the operation synchronously.
Hotfix install
hotfix.operation install
hotfix.bypassSchem The default value, false, applies any schema changes automatically. A value of true indicates that you
a
changes.
hotfix.force Set only at the request of Global Customer Support to skip hotfix validations and force the hotfix data i
hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system qu
job status. A value of false executes the operation synchronously.
Hotfix commit
hotfix.operatio commit
Property name Value
hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system queue
status. A value of false executes the operation synchronously.
Hotfix rollback
hotfix.operatio rollback
n
hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system queue
status. A value of false executes the operation synchronously.
manageRestorePoints.restorePointLabe A meaningful label that will appear in the restore point lists and information log
l
Rollback settings
rollback.action SystemRollback
rollback.async Specifies whether to run the process in asynchronous mode or synchronous mode. The defau
that you can use later to check the job status. When this value is false, the process starts imm
of synchronous or asynchronous depends on the type of script you are writing.
rollback.downloadLogToFil true or false. Set to true to attach the log to the rollback results.
e
updateAccessGroup.groupList Optional: A comma-delimited list of access groups to update. If you do not enter a
access groups that access the application.
artifactsDir The full path to the output file location, for those functions that generate output.
requestTimeOut The number of seconds the system waits for a response before failing with a tim
jobIdFile The path to the job IDs file that is generated by the asynchronous operation.
propFile The property file name, to override the default prpcServiceUtils.properties file.
operationName Specify the operation that generated the job ID for getStatus: import, export, expose, hotfix, or ro
Related information