Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Installing the application

Updated on December 3, 2021

This content applies only to On-premises and Client-managed cloud environments

To install Pega Customer Decision Hub, complete the procedures in this section.

Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide Pega Customer Decision Hub Installation Guide
Before you begin: Complete the prerequisites for this installation.
Note: Request required hotfixes:
  1. Go to your account on My Support Portal.
  2. Click New RequestFor something I need , and then select Service requestExisting hotfix.
  3. Fill out the case creation form, and then click Finish.
The list of required hotfixes can be found here: Required Pega Customer Decision Hub and Pega Marketing hotfixes and here Required Pega 1:1 Operations Manager hotfixes.

Creating the ExternalMKTData database rule

Configure the ExternalMKTData database rule to default to the Customer Data Schema that you configured during the Pega Platform installation. Depending on the database and connection types, you can do this by configuring a separate data source, configuring a JDBC default schema, or by setting a search path.

  1. Log in to Pega Platform (https://<hostname>:<port>/prweb) by entering the administrator ID, for example, [email protected] and the password that you used during Pega Platform installation.
  2. Click RecordsSysAdminDatabase.
  3. Click Create.
  4. Enter the following information:
    • Short description - External Marketing Data
    • Database - ExternalMKTData
  5. Click Create and open.
  6. On the Database tab, select the connection method from the How to connect drop-down list and enter the required connection information. The recommended connection method is JDBC connection pooling. For more information, see JDBC Connection Pool syntax and JDBC URL syntax.
  7. Click the Advanced tab.
  8. In the section List other databases that should be reachable by views in this database, click Add item to add a new row, and select PegaDATA in the autocomplete Database Name field.
  9. Click the Database tab.
  10. Click Save.
  11. Click Test Connection.

JDBC Connection Pool syntax

JDBC connection pooling is the recommended method to connect to your external database. As part of installing Pega Platform, a JDBC connection pool is usually configured in the configuration file of the application server. Refer to the appropriate Pega Platform Installation Guide for your application server type to determine the correct method of updating the configuration.

Here is an example of a JDBC URL:

jdbc:postgresql:​//serverName:5432/dbName

JNDI name syntax

If you want to use JDBC connection pooling to connect to your external database, specify the JNDI name. The required syntax for the JNDI name is java:comp/env/jdbc/<Data Source>. Replace <Data Source> with the name of the resource set in the config.xml file on the application server.

See below for an example of the syntax. The data source in the example is set to mktDataSource.

java:comp/env/jdbc/mktDataSource

JDBC URL syntax

If you want to use JDBC URL to connect to your external database, see below for the syntax used by different database types.

Oracle
jdbc:oracle:thin:@<hostname>:<port>:
<dbname>
PostgreSQL
jdbc:postgresql://<hostname>:<port>/<dbname>
MS SQL
jdbc:sqlserver://<hostname>:<port>;databaseName=<dbname>
IBM Db2
jdbc:db2://<hostname>:<port>/<dbname>:fullyMaterializedLobData=true;
fullyMaterializeInputStreams=true;
progressiveStreaming=2;progressiveLocators=2;
useJDBC4ColumnNameAndLabelSemantics=false;currentSchema=<Marketing External Schema>;resultSetHoldability=1;resultSetHoldabilityForCatalogQueries=1;allowNextOnExhaustedResultSet=1;

See below for an example of the syntax on IBM Db2. 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;

Importing the application bundles

Import the application bundles from the distribution media.

  • Rules/PegaCDH_Core_0807.zip. This contains the Pega Customer Decision Hub framework application which consists of schema changes, JAR files, and rulesets required by Pega Customer Decision Hub that are not shipped separately.
  1. Log in to Pega Platform as [email protected].
  2. To open the Import wizard, in Dev Studio, click ConfigureApplicationDistributionImport.
  3. Click Choose File, browse for the Rules/PegaCDH_Core_0807.zip file from your distribution media, and follow the wizard instructions.
    Important:

    When you import the Rules/PegaCDH_Core_0807.zip, errors related to library compilation and the column populator appear in the log file. To resolve them, log out and restart the application server, then continue the import process.

    Make sure that the check box Automatically run Upgrade Application Schema when import is complete on the Schema changes page is checked before you proceed with the Rules/PegaCDH_Core_0807.zip bundle import.

    Caution: Do not select the Enable advanced mode to provide granular control over the import process check box. The check box must be cleared to ensure that you import all components.
    Result: The wizard identifies differences between the database schema of your current system and the schema of Pega Customer Decision Hub 8.7.
  4. Based on the review of the database policies and application permissions that are used by your Pega Platform installation, perform the appropriate step:
    • Select the Automatic check box and complete the wizard.
    • Select Manual and complete the following steps:
      1. Click View/Download DDL SQL. This produces a text file containing Data Definition Language (DDL) statements for the needed changes.
      2. Save the DDL file and deliver it to a database administrator to make the required changes. Depending on your organization’s policies, database administrators might need to review these DDL files to determine what changes will occur prior to applying the DDL to your database.
      3. After the database administrator has applied the DDL, repeat the Import wizard steps.
    If there are errors that you cannot resolve, post your questions to the Pega Product Support Community. For more information about the database policies and application permissions, see Prerequisites.
  5. Apply the required hotfixes. The list of required hotfixes can be found here Required Pega Customer Decision Hub and Pega Marketing hotfixes and here Required Pega 1:1 Operations Manager hotfixes.
  6. Optional: For best performance and initial user experience, run the Static Assembler utility to pre-assemble the rules in the application. For more information, see Preassembling rules in an application by using the Static Assembler utility.

Restarting the application server

At the end of the installation process, restart the application server.

  1. Log out of Pega Platform.
  2. Stop and start the application server.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us