@PonnurangamN1990 Mario is correct in stating that what you are using is now outdated. Any product issues you encounter need to be replicated on supported enterprise software.
How to implement Pega Customer Decision Hub using the Pega Express™ delivery approach: The Prepare phase
Please have a look at the limitations of using the Community Edition/ Trial edition softtware as described in the support document Working with Pega Platform Trial and Community Edition
It includes App Studio, Dev Studio and Prediction Studio only.
This is also shown in the Community Edition download page and the Community Edition FAQ..
This indicates you cannot install Customer Decision Hub (CDH) on top of the Pega Community Edition, Personal Edition, or Trial Edition software. These editions are not designed to support such frameworks.
@Supraja.V indicated this in this PSC post.
@sethr please can you check the steps you provided before?
Log in to Dev Studio as the system architect operator in the CDHTemplate:CDHInstall access group.
Result: The system launches the Pega Customer Decision Hub setup wizard.
If you want to run the CDH Setup wizard from Dev studio, then you can do it from Launch portal → CDH setup wizard.
@sethr are you sure that CDH install can be run from a Community Edition platform?
One of the prerequisites listed is:
-
Enable decisioning nodes.
For more information, see Enabling decision management services.
CDH System Component Overview
How to implement Pega’s Customer Decision Hub, or ‘the gift that keeps on giving’
How to implement Pega Customer Decision Hub using the Pega Express™ delivery approach: The Prepare phase
Understanding the relationship between Pega Customer Decision Hub, Pega Marketing, and decision management
The user states that they "..imported CDH8.7 softwares in PE 8.7 " ’ and their issue now is :
" Pega Customer Decision Hub CDH Setup Wizard Setup wizard got stuck while defining context class .i see quite few exceptions ‘duplicate key value violates unique constraint "pr_sys_ruleset_index_pk’, "
You could try the following:
This is similar to the below articles:
https://community.pega.com/support/support-articles/ora-00001-unique-constraint-errors-when-monitoring
Frequent “duplicate key value violates unique constraint” error in the database