
11
To implement two users, you configure access to the database in your application server by
creating two data sources:
■ One datasource referencing the JNDI location jdbc/PegaRULES that
specifies the username and password for the base DB user. This user must
have at least read and write permissions for the database.
■ A second datasource referencing the JNDI location jdbc/AdminPegaRULES
specifying the username and password for the DB Admin user. This user
must have full access including permission for CREATE_TABLE and
ALTER_TABLE operations.
How Process Commander Uses the two Database Accounts
If you configure a second datasource for the Admin user, Process Commander
uses that user when performing a small number of functions that require altering
the database, specifically:
■ Using the Database Schema Management tool (Tools > Database > Modify
Database Schema).
■ Creating any new Circumstance Definition rule or defining a single
circumstance on a rule. The extended permissions are needed to support
reporting on circumstanced properties. (On the Pega Developer Network,
see PRKB-25173: How to create a rule with multiple circumstance
properties.)
■ Exposing embedded properties for selection and reporting. (On the Pega
Developer Network, see PRKB-25278: How to create Declarative indexes for
embedded properties.)
For all other functions, Process Commander uses the base DB user which only requires read and
write permissions.
If you do not provide ALTER TABLE and CREATE TABLE permissions to any user, Process
Commander generates a warning when you use these features. The warning includes SQL script
that you can provide to your DBA to manually make the necessary database changes.
Follow the guidelines for the appropriate database in the following sections
User Permissions for the Microsoft SQL Database
Set the user account for the Process Commander database user with public and db_owner
roles with all corresponding System Permissions granted.
Comentarios a estos manuales