Installing the application
This content applies only to On-premises and Client-managed cloud environments
To install Pega Customer Decision Hub, complete the procedures in this section.
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.
-
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. - Click .
- Click Create.
- Enter the following information:
- Short description - External Marketing Data
- Database - ExternalMKTData
- Click Create and open.
- 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.
- Click the Advanced tab.
- 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.
- Click the Database tab.
- Click Save.
- 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/dbNameJNDI 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/mktDataSourceJDBC 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.
- Log in to Pega Platform as [email protected].
- To open the Import wizard, in Dev Studio, click .
- Click Choose File, browse for the
Rules/PegaCDH_Core_0807.zipfile from your distribution media, and follow the wizard instructions. - 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:
- Click View/Download DDL SQL. This produces a text file containing Data Definition Language (DDL) statements for the needed changes.
- 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.
- After the database administrator has applied the DDL, repeat the Import wizard steps.
- 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.
- 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.
- Log out of Pega Platform.
- Stop and start the application server.
Previous topic Completing prerequisite tasks for installation Next topic Completing required post-installation steps