Links may not function; however, this content may be relevant to outdated versions of the product.
Using scripting with direct connection to the database and the prpcUtils tool
Use the prpcUtils tool if you have a direct connection to the database to manage system management actions even if you do not have an active instance of Pega Platform.
If you need to run asynchronous operations, or you do not have a direct connection to the database, use the prpcServiceUtils tool. For more information about the prpcServiceUtils tool, see Using service-enabled scripting and the prpcServiceUtils tool.
Configure the prpcUtils.bat
or prpcUtils.sh
script actions in the prpcUtils.properties
file.
You can also pass arguments to the script to override settings in the
prpcUtils.properties
file.
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 (--).
prpcUtils script arguments
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 (--).
prpcUtils script argument
Value
connPropFile
The full path to the connection.properties
file that includes
information for multiple targets. driverClass
Your JDBC driver class. For example, oracle.jdbc.OracleDriver. driverJAR
Location of your JDBC .jar file. dbType
Database vendor type, such as mssql, udb, oracledate, postgres, and db2zos. dbURL
JDBC URL to the database. dbUser
Database user name. dbPassword
Database password. archivePath
Full path to the archive to be imported or exported. propFile
The full path to the properties file, to override the default prpcUtils.properties. hfixAction
If manageHotfixes is selected, sets the hotfix operation. Valid values are
commit
, rollback
, generateDDL
,
install
, and scan
. rulesSchema
The rules schema. dataSchema
The data schema. noFailOnError
Set to true
or false
. When enabled, instances that
fail to import are skipped and import continues instead of failing. U
Pega user name. P
Pega password. accessGroup
AccessGroup in which the Rule-Declare-Index of the classes being exposed exists.
Applicable for the expose utility if --U or --P are not provided.
Previous topic Retrieving service-enabled job status Next topic Exporting rules and data from the command line