Skip to main content
LinkedIn
Copied!

Table of Contents

Completing the prerequisite tasks

Version:

Only available versions of this content are shown in the dropdown

Before you upgrade your application, ensure that you complete all of the following tasks.

  1. Ensure that there are no open change requests in your application, including requests created through Revision Management and through Pega 1:1 Operations Manager.

    If any change requests are in status other than Resolved-Completed or Withdrawn during the upgrade, they may fail.
  2. Ensure that any existing responses to adaptive models are updated.

  3. Run the Pre-Upgrade Check component to assess if your application is ready for the upgrade. If the check reports any issues, resolve them.

  4. Ensure that you can stop and start the application server.

  5. Before starting an upgrade, and before backing up your system, 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.

  6. If you are upgrading from Pega Marketing 7.13, 7.21, 7.22, 7.31, or 7.4, apply the required upgrade hotfix for the version you are upgrading from.

    • Pega Marketing 7.13 - HFix-48983
    • Pega Marketing 7.21- HFix-49813
    • Pega Marketing 7.22 - HFix-50020
    • Pega Marketing 7.31- HFix-46621
    • Pega Marketing 7.4 - HFix-67467
    You can request the upgrade hotfixes from Global Customer Support.
  7. Run the activity in the upgrade hotfix, depending on the version you are upgrading from:

    • Pega Marketing 7.13 - UpgradePMToSeamless
    • Pega Marketing 7.21- UpgradePMToSeamless
    • Pega Marketing 7.22 - UpgradePMToSeamless
    • Pega Marketing 7.31- UpgradePMToSeamless
    • Pega Marketing 7.4 - UpgradePMTo74CloudReady
  8. If you are upgrading from Pega Marketing 7.13 and your environment includes Pega Field Marketing, ensure that all Field Marketing campaigns are in Pending-Details or Resolved-Completed status.

    If any Field Marketing campaigns are in Open-Running status during the upgrade, they may fail.
  9. If you are upgrading from Pega Marketing 7.13, in the PR4_RULE table located in the PegaRULES database schema, update the length of the pyDescription column to 1000.

  10. If the ServiceLevelEvents agent in the Pega-ProCom ruleset is enabled, disable it.

  11. If you are upgrading from Pega Marketing 7.13, 7.21, or 7.22, import the bundle PegaMarketing_Upgrade_DB_0801.zip.

    The PegaMarketing_Upgrade_DB_0801.zip file is distributed as attachment to the required upgrade hotfix for the version you are upgrading from. For more information, see step 3 above.
  12. Unlock all artifacts rulesets that contain any artifacts which you want to continue using after the upgrade.

  13. Before you upgrade Pega Marketing, ensure that you have the following database information available:

    • Such database connection information as:
      • Hostname or IP address
      • Database port
      • Database name
    • JDBC driver JAR file for your database type
    • PegaRULES schema name
    • If using split schema, PegaDATA schema name
    • Ensure that the Pega Marketing external schema meets the following requirements:
      • This is the schema that contains your customer data repository and other marketing assets.
      • This schema must exist in the same database as the PegaDATA and PegaRULES schemas.
      • This schema must have the database privileges to create views and to select from tables in the PegaDATA schema.
    • Ensure that the Pega Marketing external user and password meet the following requirements:
      • 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.
    • Ensure that the Pega Deployment user and password meet the following requirements:
      • This user must already exist.
      • This user must have permissions to create and modify objects in all Pega schemas.
      • If using Oracle, this user must have permission to create materialized views.
    • Ensure that the user associated with PegaDATA DB rule meets the following requirements:
      • This user must be set in application server configuration.
        • For Tomcat, this would typically be in the context.xml file.
      • The user that is 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
    • Ensure that the user associated with PegaRULES DB rule meets the following requirements:
      • This user must be set in application server configuration.
        • For Tomcat, this would typically be in the context.xml file.
      • The user that is 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 user can be the same as the PegaDATA user, provided the user has permissions to both schemas.
  14. For IBM Db2 databases, if you use JDBC URL to connect to your external database, add the following parameters to the template URL and the prweb.xml file where the Pega DB connections are defined:

    • resultSetHoldability=1;
    • resultSetHoldabilityForCatalogQueries=1;
    • allowNextOnExhaustedResultSet=1;
    See below for an example of the syntax. 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;

    The setting values also apply to the PegaDATA and PegaRULES connections created by Pega Platform.

  15. Check in all checked out rules and log off all users.

  16. Back up existing database and app-server level application data. For more information, see Backing up your system.

  17. Log in as an operator with the your application:MKTAdmins access group.

  18. Edit the your application:MKTAdmins access group, or another access group with administrator privileges which your application uses, and add the PegaRULES:SecurityAdministrator user role.

    The PegaRULES:SecurityAdministrator role is required to manage operator access in Pega Customer Decision Hub. At least one administrator access group in your application must include this role.
  19. Finalize any in-use database templates.

  20. If you are using Paid Media Manager:

    1. Ensure that your Cassandra database version is 3.11.3 or newer.

      This is required for the Paid Media landing page to work correctly.
    2. In the navigation pane of App Studio, click Settings Channels Paid media Sync tracking , and verify that all sync jobs are complete.

    3. In the navigation pane of the Pega Customer Decision Hub, click Next-Best-Action Designer Channels .

    4. In the Channels section, click Edit.

    5. Disable Paid, and then click Save.

  21. Click Configure Decisioning Decisions Data flows Batch Processing and ensure there are no data flow runs in progress.

  22. Disable agent schedules by performing the following actions:

    1. Click Records SysAdmin Agent Schedule .

    2. Open all Pega Marketing agent schedules, including the following:

      • PegaMKT-Engine
      • PegaMKT-PushNotification
      • PegaMKT-Install
      • PegaMKT-FieldMarketing (if installed)
    3. Uncheck Enable this agent and ensure that each individual agent is disabled.

    4. Click Save.

    If you do not disable agent schedules, the agents will automatically restart after Pega Marketing has been upgraded to Pega Customer Decision Hub, with existing scheduled queue items trying to run, unsuccessfully. This will result in a list of broken queue items that you will need to address manually.
  23. Upgrade to the latest version of Pega Platform 8.6, and ensure that you can log in as an administrator. For more information, see the Pega Platform Upgrade Guide for your environment on the Deploy Pega Platform page.

  24. In Admin Studio, stop the RevalidateAndSave agent from the Pega-ImportExport ruleset on all nodes.

  25. Disable the agent schedule for the RevalidateAndSave agent.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us