Whether you are deploying Pega Customer Decision Hub within your enterprise's
network or using a cloud platform, ensure that your environment meets the configuration
requirements for a successful installation.
Pega Customer Decision Hub
Installation Guide
Pega Customer Decision Hub
Installation Guide
Pega Customer Decision Hub
Installation Guide
Pega Customer Decision Hub
Installation Guide
Prerequisite tasks for client-managed cloud environments
Before you install Pega Customer Decision Hub on a cloud platform of your
choice, ensure that your cloud environment is configured to support Pega applications.
Read and follow the recommendations for client-managed cloud environments.
Prerequisite tasks for on-premises environments
Before you install Pega Customer Decision Hub on servers within your organization’s
enterprise network (on-premises deployment), complete the following prerequisite
tasks.
- Ensure that you can stop and start the application server.
- In your external database, create the schema where your customer data resides,
for example, CustomerData, and ensure that the operator
that the database uses to connect has full permissions for this schema.
- Before starting an installation, review the database policies and application
permissions that are used by your Pega Platform
installation. Determine whether the application is permitted to update the
database automatically or if you must generate the database scripts that your
organization will use to manually make schema changes.
- Install the latest version of Pega Platform
8.7, and ensure that you can log in as an
administrator.
- If you are setting up a single-node environment, set the node types to Universal.
- If Pega Platform will be running on a Windows 10
machine, install Jansi for Windows to ensure
that decisioning nodes start correctly.
If you cannot install Jansi on your machine, you can disable the
requirement by editing the
$catalina_home/bin/setenv.bat file and adding
the following JVM argument: -DskipJansi=true.
However, disabling Jansi limits the scope of the decisioning node
logs.
- Specify the schema where your customer data resides (for example,
CustomerData).
- If you are using the Installation and Upgrade Assistant, specify
the schema on the Database Connection
page.
- If you are using the install script, include the
–customerDataSchema command line
option.
The installer then creates the address, contact, and organization
tables in the customer data schema. The tables created by the
installer have the prefix P_.
Important: Future versions of Pega Platform will no longer support deployment on embedded
Cassandra. In version 8.7, this deployment
option still works, but is considered deprecated and is not supported by
Pega. To ensure future compatibility and
support from Pega, do not create any new
installations using embedded Cassandra.
- If the ExternalMKTData database admin name is configured to use
Configuration preferences, in Pega Platform, create the following dynamic system settings to
specify the default schema used by the ExternalMKTData
database rule:
| Owning ruleset | Setting purpose | Value |
| Pega-Engine | prconfig/database/databases/ExternalMKTData/defaultSchema/default | name of the schema where the customer data resides, for
example,
CustomerData |
| prconfig/database/databases/ExternalMKTData/datasource/default | java:comp/env/jdbc/PegaRULES |
- Restart Pega Platform to enable the settings.
- Before you install Pega Customer Decision Hub, ensure that you have the
following database information available:
- Database connection information:
- Hostname or IP address
- Database port
- Database name
- JDBC driver JAR file for your database type
- PegaRULES schema name
- If using split schema, PegaDATA schema name
- Ensure that the Pega Customer Decision Hub external schema meets the
following requirements:
- This is the schema that contains your customer data repository
and other marketing assets.
- This schema must exist in the same database as the
PegaDATA and
PegaRULES schemas.
- This schema must have the database privileges to create views
and to select from tables in the PegaDATA
schema.
- Ensure that the Pega Customer Decision Hub external user and password
meet the following requirements:
- This user must already exist.
- This is the user that Pega Platform uses to
connect to the Pega Customer Decision Hub external schema.
- This user must have full privileges to the Pega Customer Decision Hub external schema.
- This user must have the database privileges to create views and
to select from tables in the PegaDATA
schema.
- Ensure that the Pega Deployment user and
password meet the following requirements:
- This user must already exist.
- This user must have permissions to create and modify objects in
all Pega schemas.
- If using Oracle, this user must have permission to create
materialized views.
- Ensure that the user associated with PegaDATA
database rule meets the following requirements:
- This user must be set in the application server
configuration.
- For Tomcat, this would typically be in the
context.xml file.
- The user that is mapped to the PegaDATA
database rule must already exist.
- This user must have the following privileges on the
PegaDATA schema:
- Select,
Create, and
Drop on tables, indexes, and
views
- Insert,
Update, and
Delete on tables
- Alter on tables and indexes
- Ensure that the user associated with PegaRULES
database rule meets the following requirements:
- This user must be set in application server configuration.
- For Tomcat, this would typically be in the
context.xml file.
- The user that is mapped to the PegaRULES
database rule must already exist.
- This user must have the following privileges on the
PegaRULES schema:
- Select,
Create, and
Drop on tables, indexes, and
views
- Insert,
Update, and
Delete on tables
- Alter on tables and indexes
- This user can be the same as the PegaDATA
user, provided the user has permissions to both schemas.
- For IBM Db2 databases, if you use JDBC URL to connect to your external
database, add the following parameters to the template URL and the
prweb.xml file where the Pega database connections are
defined:- resultSetHoldability=1;
- resultSetHoldabilityForCatalogQueries=1;
- allowNextOnExhaustedResultSet=1;
For example: See below for an example of the syntax. The database in the example is set to
MYDB and the marketing external schema is set to
MKTDATA.
jdbc:db2://localhost:50000/MYDB:fullyMaterializeLobData=true;
fullyMaterializeInputStreams=true;
progressiveStreaming=2;
progressiveLocators=2;useJDBC4ColumnNameAndLabelSemantics=false;
currentSchema=MKTDATA;
resultSetHoldability=1;resultSetHoldabilityForCatalogQueries=1;allowNextOnExhaustedResultSet=1;
Note: The setting values also apply to the PegaDATA and
PegaRULES connections created by Pega Platform.
Request required hotfixes
Request the required hotfixes, which are one of the configuration requirements for a
successful installation.
- Go to your account on My Support Portal.
- Click , and then select .
- Fill out the case creation form, and then click
Finish.
