MARKETING. Pega Marketing. Upgrade Guide 7.4

Transcription

1 MARKETING Pega Marketing Upgrade Guide 7.4

2 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or service marks are property of their respective holders. For information about the third-party software that is delivered with the product, refer to the third-party license file on your installation media that is specific to your release. Notices This publication describes and/or represents products and services of Pegasystems Inc. It may contain trade secrets and proprietary information that are protected by various federal, state, and international laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form without prior written authorization of Pegasystems Inc. This publication is current as of the date of publication only. Changes to the publication may be made from time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc. and must be returned to it upon request. This publication does not imply any commitment to offer or deliver the products or services described herein. This publication may include references to Pegasystems Inc. product features that have not been licensed by you or your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems Inc. services consultant. Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors, as well as technical inaccuracies. Pegasystems Inc. shall not be liable for technical or editorial errors or omissions contained herein. Pegasystems Inc. may make improvements and/or changes to the publication at any time without notice. Any references in this publication to non-pegasystems websites are provided for convenience only and do not serve as an endorsement of these websites. The materials at these websites are not part of the material for Pegasystems products, and use of those websites is at your own risk. Information concerning non-pegasystems products was obtained from the suppliers of those products, their publications, or other publicly available sources. Address questions about non-pegasystems products to the suppliers of those products. This publication may contain examples used in daily business operations that include the names of people, companies, products, and other third-party publications. Such examples are fictitious and any similarity to the names or other data used by an actual business enterprise or individual is coincidental. This document is the property of: Pegasystems Inc. One Rogers Street Cambridge, MA USA Phone: Fax: Document: ii

3 Software version: 7.4 Feedback If you have suggestions or comments for how we can improve our materials, send an to iii

4 Contents Prerequisites...5 Upgrading the application...8 Updating the ExternalMKTData database rule...8 JDBC Connection Pool syntax... 8 JNDI name syntax... 9 JDBC URL syntax... 9 Importing the application bundles...10 Running the Pega Marketing Setup Utility...11 Deploying the Pega Marketing Help and Microsite WAR files on the application server...11 Optional: Configuring Microsite settings...11 Restarting the application server Required post-upgrade steps...12 Adding database grants...13 Configuring Pega Marketing Help dynamic system settings Updating implementation application references Running the Column Populator utility...15 Running the Upgrade activity Re-indexing all Rule- classes Verifying the Decisioning top level class Configuring the Decisioning DNode Cluster...17 Verifying resource URLs...17 Verifying the Context Dictionary...18 Verifying the System Health page...18 Configuring and starting agent schedules Enabling Artifacts Agent schedule...19 Optional post-upgrade steps Adding the Pega Field Marketing ruleset to your implementation application Enabling generic operator accounts Updating Microsite authentication access Configuring Social Sentiment mappings Verifying upgraded rulesets Verifying the sample application... 23

5 Prerequisites Prerequisites Before you begin the upgrade process, make sure that you complete all of the following tasks. Important: If you are upgrading from Pega Marketing 7.21, you must first upgrade to Pega Marketing If you are upgrading from a version older than 7.21, you must first upgrade to Pega Marketing 7.21, then Pega Marketing For more information, see the Upgrade Guide for Pega Marketing 7.31 and Ensure that you can stop and start the application server. 2. Review the database policies and application permissions that are used by your Pega Platform upgrade. 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. 3. Upgrade to Pega Platform 7.4 or later, and then verify your installation as described in the Platform Upgrade Guide for your environment, available on the Deployment Guides page. Note: If you are installing on a UTF-8 encoded database, see Issue: "Error: Commit failed" when loading CPM 6.1 RuleSets into a UTF-8 encoded database. 4. Apply any required hotfixes to the Pega Platform before proceeding with the Pega Marketing application upgrade. For a list of required Pega Platform hotfixes for Pega Marketing, see the Pega Marketing Hotfixes page. 5. Update the Pega Platform online help to the latest version from the Online Help Files section on the Pega Platform Update page. After you download the latest prhelp.war file, deploy it in your Pega Platform installation before continuing. For deployment information, see the Pega Platform Installation Guide for your application server. 6. Before you install Pega Marketing, 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 PegaDATA schema name (if using split schema) Pega Marketing external schema This is the schema that contains your customer data repository and other marketing assets. This schema must have the database privileges to create views and to select from tables in the PegaDATA schema. Pega Marketing external user and password This user must already exist. This is the user that Pega Platform uses to connect to the Pega Marketing external schema. This user must have full privileges to the Pega Marketing external schema. This user must have the database privileges to create views and to select from tables in the PegaDATA schema. Pega Deployment user and password 5

6 Prerequisites This user must already exist. This is the user that the setup utility will use to connect to the database. This user must have permissions to create and modify objects in all Pega schemas. (Oracle only) This user must have permission to create materialized views. User associated with PegaDATA DB rule Set in application server configuration. For Tomcat, this would typically be in the context.xml file. The user mapped to the PegaDATA DB 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 User associated with PegaRULES DB rule Set in application server configuration. For Tomcat, this would typically be in context.xml. The user mapped to the PegaRULES DB 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 can be the same as the PegaDATA user, provided the user has permissions to both schemas. 7. Log off all users and check in all checked out rules, if possible. 8. Back up existing database and app-server level application data. 9. Log in as an operator with the <your application>:marketadmin access group. 10. Finalize any in-use database templates. 11. Click Designer Studio > Decisioning > Decisions > Data flows > Batch Processing and ensure there are no data flow runs in progress. 12. Disable agent schedules. a) Click Records > SysAdmin > Agent Schedule. b) Open all Pega Marketing agent schedules. This includes the following agent schedules: PegaNBAM-Artifacts (or your equivalent artifacts ruleset) PegaMKT-Engine PegaMKT-PushNotification PegaMKT-Install PegaMKT-FieldMarketing (if installed) ServiceLevelEvents c) Uncheck Enable this agent and ensure that each individual agent is disabled. d) Click Save. 6

7 Prerequisites Note: If you do not disable agent schedules, the agents will automatically restart after Pega Marketing has been upgraded, with existing scheduled queue items trying to run, unsuccessfully. This will result in a list of broken queue items that will need to be manually addressed. 7

8 Upgrading the application Upgrading the application To upgrade Pega Marketing, complete the following steps: 1. Updating the ExternalMKTData database rule 2. Importing the application bundles 3. Running the Pega Marketing Setup Utility 4. Deploying the Pega Marketing Help and Microsite WAR files on the application server 5. Optional: Configuring Microsite settings 6. Restarting the application server 7. Required post-upgrade steps 8. Optional post-upgrade steps 9. Verifying upgraded rulesets Updating the ExternalMKTData database rule 1. Log in to the Pega Platform ( by entering the administrative ID that you set up when you installed Pega Platform, such as and the password that you specified. 2. Click Records > SysAdmin > Database. 3. Open the ExternalMKTData database rule. 4. In the Authentication section on the Database tab, set the username and password to a valid database user that owns the objects in the ExternalMKTData schema. 5. 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. 6. Click the Advanced tab. 7. In the section List other databases that should be reachable by views in this database, click Add item to add a new row, and enter PegaDATA into the Database Name field. 8. Click the Database tab. 9. Click Save. 10. Click Test Connection. JDBC Connection Pool syntax JNDI name syntax JDBC URL syntax JDBC Connection Pool syntax JDBC connection pooling is the recommended method to connect to your external database. As part of installing the core platform, a JDBC connection pool is usually configured in the application config.xml file. 8

9 Upgrading the application See below for an example of the syntax on Tomcat. The data source in the example is set to mktdatasource. <Resource name="jdbc/mktdatasource" auth="container" type="javax.sql.datasource" driverclassname="oracle.jdbc.oracledriver" username="<usename>" password="<password>" /> 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 <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>; 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; 9

10 Upgrading the application currentschema=mktdata; Importing the application bundles 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: a) Transfer ownership of VIEW MKTDATA.MKT_INTERACTION_DETAIL to user MKTDATA PRESERVE PRIVILEGES. b) Transfer ownership of VIEW MKTDATA.MKT_COMMUNICATION_HISTORY to user MKTDATA PRESERVE PRIVILEGES. 2. Log in to the Pega Platform ( by entering the credentials that you specified when you upgraded this server. 3. Import the following bundles in the order they are listed below, following step 4 through step 8. Rules/PegaMarketing_0740.zip. This contains the Pega Marketing framework application which consists of schema changes, JAR files, and rulesets required by Pega Marketing that are not shipped separately. Important: When you import the Rules/PegaMarketing_ 0740.zip, library compile errors appear in the log file. To resolve them, log out and restart the application server, then continue the import process. Rules/PegaMarketing_Application _ 0740U.zip. This contains the upgrade version of the Pega Marketing implementation application. This version will not overwrite configuration settings that may have been made to your existing Pega Marketing implementation. (If licensed) - Rules/PegaMarketing_FieldMarketing_0740.zip. This contains the Pega Field Marketing application and rulesets. Note: Pega Field Marketing is required if you plan to use Pega Marketing with the Pega Customer Relationship Management suite. (If licensed) - Rules/PegaMarketing_MKTOperations_ 0740.zip. 4. To open the Import wizard, click Designer Studio > Application > Distribution > Import. 5. Click Choose File, browse for the file from your distribution media, and follow the wizard instructions. To ensure that you import all components, do not select the Enable advanced mode to provide granular control over the import process check box. The wizard identifies differences between the database schema of your current system and the schema of Pega Marketing Based on the review of the database policies and application permissions that are used by your Pega Platform upgrade (Prerequisites), perform the appropriate step: Select the Automatic check box and complete the wizard. Select Manual and complete the following steps: a) Click View/Download DDL SQL, which produces a text file containing Data Definition Language (DDL) statements for the needed changes. b) 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. c) After the database administrator has applied the DDL, repeat the Import wizard steps. 10

11 Upgrading the application If there are errors that you cannot resolve, post your questions to the Pega Product Support Community. 7. Optional: For best performance and initial user experience, run the Static Assembler utility to preassemble the rules in the application. For more information, see Preassembling rules in an application by using the Static Assembler utility. 8. Apply any required hotfixes. For the list of required Pega Marketing hotfixes, see the Pega Marketing Hotfix page. Running the Pega Marketing Setup Utility The Pega Marketing Setup Utility is used to run database scripts against your database. It can be run either interactively, or with a preconfigured database.properties file. It requires the appropriate JDBC driver file for your database. This utility is located in the ResourceKit/setup folder. The steps that follow are relative to this folder. 1. Copy the JDBC JAR file for your database to ResourceKit/setup/core/lib. 2. To interactively create the properties file, skip to step To use a preconfigured properties file, create the file database.properties in the ResourceKit/setup folder, and set the properties as appropriate for your database. The file database.properties.template describes each property. You can use it as a template when you create your file. 4. Run the script setup.bat (Windows) or setup.sh (Unix/Linux). The utility validates the DB connection and generates scripts based upon the properties set in the database.properties file. The scripts are created under the Generated folder. 5. After the scripts are generated, you are prompted to execute the scripts or cancel setup. You can review the scripts before executing them. 6. After running the scripts, you can review the run_sql_errors_<hostname>.log file in the logs folder to make sure that there are no critical errors. Deploying the Pega Marketing Help and Microsite WAR files on the application server Update the Pega Marketing online help to the latest version by deploying the MarketingHelp.war file on the application server. If you want to use the Microsite functionality, deploy the MS.war file as well. 1. If you deployed an older version of the Pega Marketing Help WAR file, undeploy it. 2. Optional: If you deployed an older version of the Microsite WAR file and PRGateway, undeploy them. 3. Deploy the WebArchives/MarketingHelp.war file from your distribution media. For deployment information, see the Pega Platform Installation Guide for your application server. 4. Optional: Deploy the WebArchives/MS.war file from your distribution media. For deployment information, see the Pega Platform Installation Guide for your application server. Optional: Configuring Microsite settings If you deploy the MS.war file on a different machine than the one on which you installed Pega Marketing, you need to modify the index.html file. 11

12 Upgrading the application Note: Only operators who have the role PegaMarketing_FW:MicrositeAdmin can create Microsites. By default, Marketing Analysts do not have this role. If an operator requires the ability to create Microsites, associate the operator with an access group that contains the PegaMarketing_FW:MicrositeAdmin role. For information about configuring access groups, refer to the Pega Platform help. 1. Navigate to the directory where you deployed the MS.war file (for example, Tomcat\webapps\MS). 2. Edit the file index.html and add the host name and port for your Pega Marketing installation to the script source URLs: <script src =' pyactivity=pzincludemashupscripts'></script> <script src =' PegaMKTMicrosite/Services/IncludeMicrositeScripts'></script> 3. In Designer Studio, open the application rule associated with the PegaNBAM:Agents access group. 4. Click the Integration & Security tab. 5. In the Mashup security section, click Add a row. 6. In the Trusted origin field, enter the URL for the location of the deployed MS.WAR file. Restarting the application server At the end of the upgrade process, restart the application server. 1. Log out of the Pega Platform. 2. Stop and start the application server. Required post-upgrade steps After upgrading the application, you need to complete several configuration steps, such as granting database rights, configuring agents, and others described below. For all configuration tasks, log in as an operator with the <your application>:marketadmin access group. Adding database grants Configuring Pega Marketing Help dynamic system settings Updating implementation application references Running the Column Populator utility Running the Upgrade activity Re-indexing all Rule- classes Verifying the Decisioning top level class Configuring the Decisioning DNode Cluster Verifying resource URLs Verifying the Context Dictionary Verifying the System Health page Configuring and starting agent schedules Enabling Artifacts Agent schedule 12

13 Adding database grants The user associated with the ExternalMKTData schema must have grants to certain tables in the PegaDATA schema. From your database client, run the following statements: ExternalMKTData privileges GRANT SELECT ON ${dataschema}.pr_data_corr_sms TO ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_corr_ TO ${mktdatauser}; GRANT SELECT ON ${dataschema}.mkt_data_corr_sms TO ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_push_message TO ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_push_registration TO ${mktdatauser}; Note: On IBM Db2 environments, use the following syntax instead: Upgrading the application GRANT SELECT ON ${dataschema}.pr_data_corr_sms TO USER ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_corr_ TO USER ${mktdatauser}; GRANT SELECT ON ${dataschema}.mkt_data_corr_sms TO USER ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_push_message TO USER ${mktdatauser}; GRANT SELECT ON ${dataschema}.pr_data_push_registration TO USER ${mktdatauser}; Replace ${dataschema} with the name of the schema referenced by the PegaDATA database rule, and ${mktdatauser} with the name of the user associated with the ExternalMKTData database rule. Interaction History Data privileges If the Interaction History tables are installed in a schema associated with a DB rule other than PegaDATA, for example PegaIHData, you must grant SELECT privileges on all Interaction History tables to the users and schemas associated with both the PegaDATA and ExternalMKTData DB rules. GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_application to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_channel to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_context to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_customer to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_journey to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_location to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_operator to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_outcome to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_fact to ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_application to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_channel to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_context to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_customer to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_journey to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_location to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_operator to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_outcome to ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_fact to ${mktdatauser}; Note: 13

14 Upgrading the application On IBM Db2 environments, use the following syntax instead: GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_channel to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_context to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_customer to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_journey to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_location to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_operator to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_outcome to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_fact to USER ${pegadatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_channel to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_context to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_customer to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_journey to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_location to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_operator to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_dim_outcome to USER ${mktdatauser}; GRANT SELECT on ${ihdataschema}.pr_data_ih_fact to USER ${mktdatauser}; Replace ${ihdataschema} with the name of your IH schema, ${pegadatauser} with the name of your PegaDATA user, and ${mktdatauser} with the name of your External Marketing user. Configuring Pega Marketing Help dynamic system settings 1. Click Records Explorer > SysAdmin > Dynamic System Settings. 2. Search for the HelpURI/MarketingHelp setting purpose. 3. Edit the value to point to the Pega Marketing Help application at the host and port where the MarketingHelp.war file has been deployed. Updating implementation application references Follow these steps to update either the Pega-provided implementation application Pega Marketing, or your implementation application built on the Pega Marketing foundation. 14

15 Upgrading the application 1. If your rulesets are using Ruleset Validation, ensure that the highest version of rulesets listed in your implementation application has a dependency on the ruleset PegaMKT-Install: If your rulesets are using Application Validation, this step is not required. 2. Review the application rulesets and verify that they reference the ruleset version that contains all of your existing artifacts and rules. 3. Ensure the implementation application is built on the application PegaMarketing_FW: On the Cases & data tab, add a reference to the new subscription microsite. 5. Review the access groups for your application. For each access group: a) Verify that the Application is the implementation application that is built on application PegaMarketing_FW:7.4. b) On the Advanced tab in the Design time Configuration section, verify that the default destination ruleset references the Artifact ruleset and version that contains your artifacts. The standard access groups are: PegaNBAM:Agents PegaMarketing:SOAPUsers PegaMarketing:FieldMarketers PegaMarketing:FieldMarketingManagers PegaMarketing:MarketAdmins PegaMarketing:MarketAnalysts PegaMarketing:MarketManagers c) Optional: Add one of the following roles to your access group: CustomerDecisionHub:DataAnalyst - This role grants the user access to the Data menu in the Pega Marketing portal. The Data menu includes Data Management (previously in Application Settings) and Interaction History Summaries items. CustomerDecisionHub:DataAdmin - This role grants the user access to the same menu options as CustomerDecisionHub:DataAnalyst. In addition, it grants access to the Data > Data Flows menu in the Pega Marketing portal. Running the Column Populator utility In Pega Marketing 7.4, additional properties have been exposed. Run the Column Populator utility to copy data from the BLOB to these columns. 15

16 Upgrading the application 1. For instructions on how to run the utility, see How to use the Column Populator utility. When you edit the COMMON PROPERTIES - DB CONNECTION (REQUIRED) section of the <PEGA_HOME>/scripts/ utils/prpcutils.properties file, make sure to enter the value of the following parameters for your installation: pega.jdbc.username pega.jdbc.password rules.schema.name data.schema.name 2. Run the utility against the following classes: Data-Corr- PegaMKT-Work Rule-Obj-Corr-SMS Rule-Obj-Flow-Offer Rule-Obj-Report-Definition-Segment Rule-Obj-Treatment-Outbound Rule-PegaMKT-Passbook You can use this expression in the PRPCUtils.properties file to include the classes with properties exposed in Pega Marketing 7.4: expose.classes.included=pegamkt-work,rule-obj-corr-sms,rule-obj-flow- Offer,Rule-Obj-Treatment-Outbound,Rule-PegaMKT-Passbook,Rule-Obj-Report- Definition-Segment,Data-Corr- expose.included.descendent=true Running the Upgrade activity This activity updates your existing campaign runs and segments to work with Pega Marketing Run the UpgradePegaMarketing activity, located in the PegaMKT-Install class. Ensure that the check box for UpgradeFrom731To74 is checked. If you are upgrading from 7.22, ensure that the check box for UpgradeFrom722To731 is also checked. If your environment is configured with physical partitioning, ensure that the check box for Physical Partition is checked. 2. As the activity runs, a popup window appears. When the run finishes, this popup window displays the XML output. Important: Do not close the popup window while the activity runs. 3. Ensure that the activity completes successfully. If there are any errors, contact the product support team. Note: The XML output may include messages that some segments have not been upgraded automatically. These messages do not indicate an error. To resolve them, review the affected segments and update them manually. For more information, see Upgrading Segments in Pega Marketing. 16

17 Re-indexing all Rule- classes Upgrading the application To ensure that offers, strategies, and other Pega Marketing rules created before the upgrade are shown in Search, re-index all Rule- classes. 1. Click Designer Studio > System > Settings > Search. 2. Click Re-index in the Default Indexes > All rules section. Verifying the Decisioning top level class 1. Click Designer Studio > Decisioning > Decisions > Proposition Management > Hierarchy. 2. Hover your mouse over the Show context link. The current context is displayed. 3. If the current context is different from your existing Top Level SR class, click the SR Class link to modify it. Configuring the Decisioning DNode Cluster Confirm that the following DNodes have been created for the Decisioning services Decision Data Store, Adaptive Decision Manager, Data Flow, Real-time Data Grid, and Stream. If they have not, follow the steps below to add them. 1. Click Designer Studio > Decisioning > Infrastructure > Services. 2. On the Decision Data Store tab, click Add node. Select the node you want use as your decision data store. 3. On the Adaptive Decision Manager tab, click Add node. Select the node you want use as your adaptive decision data store. 4. On the Data Flow tab, add a node for each entry in the Service drop-down list. 5. On the Real-time Data Grid tab, click Add node. Select the node you want use for Real-time Data Grid. 6. On the Stream tab, click Add node. Select the node you want use for stream services. Verifying resource URLs 1. Click Designer Studio > System > Settings > URLs. 2. On the Resource URLs tab, verify that the resource URLs are correct. 3. Verify that the public link URL can be accessed by an external user. 4. If you change the value of a resource URL, log off and log back in for the change to take effect. 17

18 Verifying the Context Dictionary Upgrading the application 1. Switch to Express Mode by selecting the arrows icon in the lower corner of the left navigation bar. 2. Click Settings > Context Dictionary. 3. Verify that the ruleset for generated artifacts is correct. 4. Verify the Primary Context by clicking the gear icon in the Primary Context box. The sidebar should contain: Your customer class and the correct class keys Properties for full name, , and mobile numbers Optional: The exclusion list that was previously configured in application settings Any classes that were previously associated to your customer class 5. Verify the Prospect Context by clicking the gear icon in the Prospect Context box. The sidebar should contain your prospect class and the correct class keys. 6. Optional: If you need to update any data, make the necessary changes, and then click Save and Generate. Verifying the System Health page 1. Log in to the Pega Marketing portal. 2. Click Configuration > Settings > System Health. 3. Review and address any errors or warnings. Configuring and starting agent schedules The agents included with Pega Marketing are provided disabled by default. After you restart the application server, enable the agent schedules. 1. Click Records Explorer > SysAdmin > Agent Schedule. 2. Open the agent schedule of each node on which you want to run the agent. This includes the following agents: PegaMKT-Engine PegaMKT-PushNotification (If licensed) PegaMKT-FieldMarketing Note: Enable the agent RefreshCampaignOfferStats on only one node to avoid duplicate requests to refresh statistics. ServiceLevelEvents agent within the Pega-ProCom agent schedule 3. Check Enable this agent and ensure that each individual agent is enabled. 4. Click Save. 5. Update the Pega-RULES agent schedule on every active node. a) Open the agent schedule and click the Security tab. b) Set the access group to PegaNBAM:Agents. c) Ensure that the Bypass activity authentication check box is selected. 18

19 Upgrading the application Enabling Artifacts Agent schedule Re-enable the PegaNBAM-Artifacts (or equivalent artifacts ruleset) agent schedule that you disabled prior to the upgrade. If not using the PegaNBAM-Artifact ruleset, you can use the agent PegaNBAM- Artifacts: as a template. This agent contains the ProcessBatchJob agent name. Optional post-upgrade steps The below configuration tasks are optional and depend on specific features of your implementation application. For all configuration tasks, log in as an operator with the <your application>:marketadmin access group. Adding the Pega Field Marketing ruleset to your implementation application Enabling generic operator accounts Updating Microsite authentication access Configuring Social Sentiment mappings Adding the Pega Field Marketing ruleset to your implementation application If you use Pega Field Marketing, verify that its ruleset is in your application stack for either the Pegaprovided implementation application Pega Marketing, or your implementation application built on the Pega Marketing foundation. 1. Click on the name of your implementation application and select Definition. 2. If needed, add the PegaMarketing_FieldMarketing:7.4 application to the Built on application(s) list. Enabling generic operator accounts For security purposes, Pega-provided operators (for example, MarketingAdministrator and MarketingAnalyst) are disabled when you upgrade to Pega Marketing 7.4. If you want to continue to use generic operators in your implementation, use the Pega-provided operators as a template to create your own. Note: Customized operators in your implementation are not affected and can be used immediately after the upgrade. 1. Log in as a Pega Platform administrator. 2. Click Designer Studio > Org & Security > Organization > Operators. This page lists all operator accounts. For a list of Pega-provided operators, see Pega Marketing operators and access groups. 3. Click the Pega-provided operator that you want to use as your template. 4. Click Save > Save As and enter the Operator ID. This creates a new operator record with all the settings and preferences of the Pega-provided operator. 5. Optional: In the Contact Information section on the Profile tab, fill out the required information. 6. In the Access settings section on the Security tab, click Update password and enter a temporary password for this operator. 7. Select the Force password change on next login check box and clear the Disable Operator check box. 8. Click Actions > Save. 19

20 Upgrading the application 9. Repeat these steps to create all operators that you want to use with your application. Updating Microsite authentication access If you want to use the Microsite functionality, create an operator account with the required access group PegaMKT:Unauthenticated. 1. Click Designer Studio > Org & Security > Groups & Roles > Access Groups. 2. Search for and edit the PegaMKT:Unauthenticated access group. 3. In the Application section, select your implementation application in the Name field. 4. Make sure that the destination artifact ruleset is selected. 5. Click Save. 6. Click Designer Studio > System > General > Systems, Nodes, Requestors. 7. In the Requestors table, click the BROWSER requestor for your current system. Note: Your current system name is displayed in the System Name field above the table. 8. Set the Access Group Name for the BROWSER requestor to PegaMKT:Unauthenticated. 9. Click Save. 10. Click Records > SysAdmin > Dynamic System Settings > Create. 11. Enter the following values and click Create and Open: Short description - PegaMKT-Engine microsite/url Owning Ruleset - PegaMKT-Engine Setting Purpose - microsite/url 12. Enter the URL of the IAC servlet into the Value field, in the format prweb/iac. 13. Click Save. 14. Create a new operator account. In the Access Group section on the Profile tab, enter or select PegaMKT:Unauthenticated. 15. To let the Microsite authentication functionality know about the new operator, create a new dynamic system setting. a) Click Records > SysAdmin > Dynamic System Settings > Create. b) Enter the following values and click Create and Open: Short description - PegaMKT-Engine microsite/parameters/useridentifier Owning Ruleset - PegaMKT-Engine Setting Purpose - microsite/parameters/useridentifier c) Enter the name of the operator you created in step 13 into the Value field. d) Click Save. Configuring Social Sentiment mappings If you are licensed to use Pega Social, configure the Social Sentiment mappings. 1. If you have not done so already, register a Twitter app for your Twitter account on the Twitter apps portal. This step is required to obtain the OAuth settings used in step 2 below. 20

21 Upgrading the application 2. Click Save As to save the following rules into your unlocked implementation ruleset version. Do not change the name of the rules. TwitterSocialSentiment a. Fill out the required OAuth settings: Consumer key Consumer secret Access token Access token secret b. In the Search keyword(s) section, add a keyword for each Twitter handle that you want to monitor. The keyword for the handle must include symbol). DFTwitterSocialSentiment FTMTwitterSocialSentiment 3. Open DFTwitterSocialSentiment. 4. Under the Actions menu, click Run. 5. Click Activate. This starts the listening process. Social Sentiment widgets on the Pega Marketing dashboard now display your data. Verifying upgraded rulesets The following lists the highest level ruleset versions loaded by the upgrade process. Verify that your system includes these ruleset versions. If your system does not contain the following rulesets, the upgrade procedure was not successful. 1. Click Designer Studio > Application > Structure > RuleSet Stack. 2. Verify that the following ruleset versions are listed: PegaMarketing:7.4 (or your implementation application) PegaNBAM-Artifacts: PegaNBAM-Rules: PegaMarketing_FieldMarketing:7.4 (Optional - Will appear only if installed.) PegaMKT-FieldMarketing:

22 PegaMarketing_FW:7.4 PegaMKT-Install:07-40 PegaMKT-MarketingProfile:07-40 PegaMKT-Portal:07-40 PegaMKT-Desktop:07-40 PegaMKT-RevisionManagement:07-40 PegaMKT-Engine:07-40 PegaMKT-Integration:07-40 PegaMKT-MailUtilities:07-40 PegaMKT-Passbook:07-40 PegaMKT-PushNotification:07-40 PegaMKT-Security:07-40 PegaMarketing_FW_PreReqs:7.4 PegaFW-NPS: PegaFW-DashboardCharts: Pega-IAC: UIKit:11.01 UI-Kit-7: PegaDM:07.10 Pega-DecisionManager: PegaRULES:07.10 Pega-ProcessCommander: If your system does not contain the latest rulesets, it indicates that the installation procedure was not completed successfully. a) Use the Log files tool to review any errors or warnings that occurred. b) If applicable, take appropriate action to correct any existing system conditions that prevented a successful installation. c) After you correct the conditions, import the JAR files again and then verify the rulesets. d) If you cannot correct the conditions that cause the error, restore your system from the backup and see if this corrects the condition. e) If you are unable to resolve the situation, go to My Support Portal to request appropriate assistance.

23 Verifying the sample application Verifying the sample application Log in to the Pega Marketing portal to verify that the installation process has completed successfully. 1. Log in to your application as a user with the <your application>:marketanalysts access group. 2. Verify that you can view the Pega Marketing portal. 23

24