Skip to main content


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

Updating the application

Updated on January 13, 2022

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

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

Pega Customer Decision Hub Update Guide Pega Customer Decision Hub Update Guide Pega Customer Decision Hub Update Guide Pega Customer Decision Hub Update Guide
Before you begin: Complete the prerequisites for this update.

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.
  • Rules/PegaCDH_Upgrade_0807.zip. This contains the update version of the Pega Customer Decision Hub implementation application. This version will not overwrite configuration settings that may have been made to your existing implementation application.
  1. On IBM Db2 environments, ensure that ownership of the MKT_INTERACTION_DETAIL and MKT_COMMUNICATION_HISTORY views is attributed to the ExternalMKTData schema owner. For example, if that user is MKTDATA:
    1. Transfer ownership of VIEW MKTDATA.MKT_INTERACTION_DETAIL to user MKTDATA PRESERVE PRIVILEGES.
    2. Transfer ownership of VIEW MKTDATA.MKT_COMMUNICATION_HISTORY to user MKTDATA PRESERVE PRIVILEGES.
  2. On IBM Db2 environments, run the ResourceKit/upgrade/DB2/upgrade_pre_import.sql script by doing the following tasks:
    1. If your database schema is different from PegaDATA, edit the ResourceKit/upgrade/DB2/upgrade_pre_import.sql script and, if different, change all references of PEGADATA to refer to your database schema.
    2. Log in to your database client as a user who can create and drop objects in your database schema.
    3. In your database client, run the upgrade_pre_import.sql script.
  3. Log in to Pega Platform as [email protected].
  4. To open the Import wizard, in Dev Studio, click ConfigureApplicationDistributionImport.
  5. 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 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.
  6. Based on the review of the database policies and application permissions that are used by your Pega Platform upgrade, 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.
  7. To import the Rules/PegaCDH_Upgrade_0807.zip file, repeat steps 3-5.
  8. On IBM Db2 environments, run the ResourceKit/upgrade/DB2/upgrade_post_import.sql script by doing the following tasks:
    1. If your database schema is different from PegaDATA, edit the ResourceKit/upgrade/DB2/upgrade_post_import.sql script and, if different, change all references of PEGADATA to refer to your database schema.
    2. Log in to your database client as a user who can create and drop objects in your database schema.
    3. In your database client, run the upgrade_post_import.sql script.
  9. 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.
  10. 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 update process, restart the application server.

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

Updating Pega 1:1 Operations Manager

After updating your Pega Customer Decision Hub application, update Pega 1:1 Operations Manager.

  1. In Dev Studio, click the name of your application, and then click Definition.
  2. Make sure that the top rule in the Application ruleset section has a major and a minor version, for example, OpsOverlay:01-02. If required, update the ruleset version.
    Note: Do not include the patch number in the ruleset version.
  3. Log in as an operator with the OpsMgrAdmin access group and make sure that the overlay ruleset is pointing to the latest version.

Updating Pega 1:1 Operations Manager in configurations with Deployment Manager 5.1

If your environment includes Deployment Manager 5.1, do the following additional steps:

  1. Create a Product rule that contains just the ruleset.
  2. Create the following deployment pipeline in the orchestration server: Business Operations environment > Development > Production.
  3. In the new pipeline, click Start deployment.
  4. Create a new Business Operations pipeline.
  5. If any merge conflicts occur on the new Business Operations pipeline, do the following steps:
    1. Log in as an operator with the OpsMgrAdmin access group.
    2. From the application definition, open the associated revision branch.
    3. Click ActionsMerge, and then click Conflicts.
    4. Solve each merge conflict, and then click Mark as resolved.
    5. Submit your changes.
    6. On the Merge Branches screen, click Cancel.
    7. In the orchestration server, retry the deployment.

Tags

Pega Customer Decision Hub 8.7 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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