Moving to Pega7

Agenda

• Top 10 Reasons for Upgrade

• Types of Upgrades – Comparative Analysis– Tolerance, Compliance, Enhancement Upgrade

• Upgrade Process– Rules Migration

– Rules Upgrade

– Data-Only Upgrade

– Update Wizard

– Post Upgrade Steps

• User Interface - Upgrade Impacted Areas & OOTB Utilities

• Maintenance Level Update Process

• Best Practices

• Q&A

2

TOP 10 REASONS TO UPGRADE TO PEGA 7

1. Modern UI

2. Responsiveness

3. Mobile Ready

4. Modern Browsers

5. User Efficiency

6. Robust Case Management

7. Decisioning and Analytics

8. Social Integration

9. Improved Development

10. Quality

Types of Upgrades

Tolerance

• Infrastructure upgrade

• Pega7 platform upgrade along with Applications

• Cross-Browser Dev environment

• Split schema and better performance

• Parallel Development

• Hotfix Rollback

• Not suitable for Production

Compliance

• Complete IE11 and Cross-Browser support

• Crash recovery

• Responsive UI

• Enhanced Reporting Capabilities

• Next-Gen UI Capabilities

Enhancement

• Federated Case Management

• Stage-based Case Management

• Mobile Readiness

• Decisioning and Analytics

• Social Integration

Tolerance Upgrade• Scope

– Complete PRPC Upgrade & Strategic Apps Upgrade in Split Schema mode– Fixing issues related to compatibility

• Business Benefits– Adopting Split Schema for continuous availability– Better performance with Application Based Assembly / Caching– Parallel Development Leveraging Branch & Branch Rulesets– Ability to rollback Hot Fixes– Enhanced AES & System Monitoring

• Developer Incentive– Cross – Browser Compatible Development Environment– Ease of development with intuitive and new Rule Forms– New Shapes & Utilities are provided to avoid custom coding– Private check-out of Rules for making local changes to validate / verify / debug– Live UI for easy debugging of UI elements

Note : This upgrade option is achievable only when the customer application do not have any Pega Strategic Apps and HTML5 /

IE11 / cross-browser support is not required for the customer application

Compliance Upgrade – HTML5 / IE11

• Scope – 100% Tolerance Upgrade++

– Re-engineer application to update deprecated features and custom code

– Making Composite Portals to work across browsers

• Business Benefits– Crash Recovery as part of High Availability

– Cross-Browser support – IE / Chrome / Mozilla etc.

Compliance Upgrade – Responsive UI Conversion

• Scope – 100% Tolerance Upgrade++

– UI Conversion to HTML5 / CSS3 (Standards Mode)

– Replace all existing Smart and Free-Form Layouts with Dynamic Layouts

– Re-engineer List Views with Report Definitions or Grids

– Re-engineer existing composite portals with Pega7 Case Manager Portal

• Business Benefits– Crash Recovery as part of High Availability

– Responsive User Interface across different form factors e.g. Mobile / Tablet / PC

– Better UI Performance with Next Generation UI capabilities

– Cross-Browser support

– OOTB Pega Pulse, Case Tagging, Case Follow

– Enhanced Reporting with 3D Charts

Enhancement Upgrade• Scope

– 100% Tolerance & Compliance Upgrade++– Re-engineering to adopt new features like

• Case Management, Stage Based Case Mgmt. or Federated Case Mgmt.• BIX & Advance Reporting• Security and Authorization features• Integration, Data Modeling features etc.

• Business– Case Management Life Cycle– Federated Case Management (FCM) & FCM Repository– Grids with the support of keyboard events and actions– Independent Data Loading in a screen (asynchronous data loading)– Enhanced Security based on policy configuration

• Captcha during login• Capturing login failures• Password expiration

– Leverage Predictive & Adaptive Analytics with Decision Strategy Manager

Upgrade Process

9

Upgrade Methodology

• In-Place Upgrade (not recommended)− Traditional way of upgrade− Requires more Production downtime

• Out-Of-Place Upgrade (recommended)− Pega7 suggested upgrade methodology

− Least Production Downtime

− Provides High Availability and Rolling Upgrades / Updates

• Migration Upgrade (not recommended)

− Taking the R-A-P out of 6.x versions and install on fresh Pega 7.x

− Suggested for Applications not in Production

− Not suggested for Applications running in production as Work Object and

Data Migration is carried out separately

10

Recommended Upgrade Approach (Dev & Prod)

PRPC 6.x Temporary DB

PRPC 6.x

Upgrade Window

Pega7 App Up &

Running

Multi-Channel Support

“Out-of-Place” Upgrade

(Split Schema)

Rules Migration

• Migratesystem.properties drives the migration process

• Extracts all the Rule- inherited class tables from the source schema

• Unloads the respective rule table dump from the source schema to temp directory

• Apply the schema changes in destination schema

• Loads the respective rule table dumps from temp directory to destination schema

• Allows user to generate the migration DDL

12

Rules Migration

13

Rules Upgrade

• SetupDatabase.properties drives the upgrade process

• SetupDatabase.xml ANT file runs the entire upgrade process

• Upgrade.sh command runs the Rules upgrade

• “UpgradeFinalization” ANT target is used for upgrade process

• Allows users to manually generate the DDL for the Data Upgrade

14

Rules Upgrade

15

Rules Upgrade

16

Target Description

Initialization • Checks if enough space is available in the file system

• Checks whether valid DB Connection details are provided

• Creates temp directory etc.

Configuration Generates configuration files (prbootstrap.properties, prconfig.xml) used for the upgrade process

Cleanup RulesetsThis will generate the SQL scripts for deleting older Process Commander rulesets (it does not

generate scripts for Customer Rulesets)

Generate Upgrade DDLIt will generate the DDL for the version you are upgrading from, to the Pega7 platform. Generated

DDL’s can be found in (([core distribution]/schema/generated/[db-type]/update/statements))

Schema Upgrade The generated DDL is applied in this target

Apply UDF’s Applies the UDFs generated in Generate DDL step

Disable Database Triggers Disables the database triggers on tables in the rule schema to preventing population of update cache

Engine Load Loading the new Engine classes for the new version of Pega

Reorganize Database Indexes This target calls the SPPR_REBUILD_INDEXES procedure to rebuild indices and force the

recomputation of table stats for the purpose of upgrade performance.

Upgrading Java Syntax This utility is run against the existing rulebase to identify, document and correct embedded java

included in customer rules that have used identifiers that in newer versions of Java have become

reserved words (for example, "enum").

Rules Upgrade

17

Target Description

Rules UpgradeLoads the rules for Pega7 platform. As part of this process it checks against the existing rulebase

and import rules as needed

Remap Database TablesThis will remap the D-A-DB-Table instances to respective D-A-DB names

(PegaRULES/PegaDATA) respectively

Optimize Newly Exposed Columns This will run the column population for the different classes

Generate Declarative Indexes Generate Declarative Indices for Customer Rules

Import Assembled Classes Import pre-assembled rules for Pega7 version

Run Update WizardThis step is run mandatorily for version upgrades. This will invoke UpdateExisitng Application

functionality

Run AssemblerRuns the static Assembler on the rule base. This is a resource intensive step but is an optional

step

Prebuild Conclusions This step will regenerate the conclusion cache for the upgraded system

Enables Database Triggers Enables the database triggers which are enabled during the initial targets

Cleanup Cleans up the temporary directory

Data-Only Upgrade

• SetupDatabase.properties drives the Data upgrade process

• SetupDatabase.xml ANT file runs the Data upgrade process

• This process should start only after rules upgrade is completed

• In case of two databases, make sure that rules are re-migrated and Rule Schema Objects are generated

• This step does not touch the customer-specific work Objects

• Upgrade.sh –dataOnly true command runs the Data-Only upgrade

• “UpgradeDataSchema” target is invoked

• It allows users to manually generate the DDL for Data Upgrade

18

Data-Only Upgrade

19

Data-Only Upgrade

20

Target Description

Upgrade Data Config Sets the properties required for the data schema upgrade

Initialization Creates the temp directory etc

Configuration Generates the SQL DDL statements for the Data Schema

Apply UDF’s Adds the User Defined Functions to Data Schema

Schema Upgrade Apply the generated DDL

Replace System Name Replaces the system name in auto generated prconfig.xml with the properties file system name

Optimize Data instances

This step will expose the properties for the following classes

• Data-Admin-Nodes

• Data-Admin-System-Settings

• Data-AutoTest-Result-Suite

• Data-AutoTest-Result-Case

Data Upgrade Imports the PRPC_Data.jar file

Run Update WizardThis step is run mandatorily for version upgrades. This will invoke UpdateExisitng Application

functionality

Resave Migrated Data Instances If Upgrading from 6.1 GA or earlier it will exposes the properties for the Data-Content-Image class

Cleanup Cleans up the temporary directory

Post Upgrade Steps

• System -> Release -> Upgrade Landing Page

• PRPC Schema Report does not alter custom work tables

• Upgrade tools help to convert the flow actions, upgrade CSS etc.

• Validate will allow to run the Revalidate and Save

21

Post Upgrade Steps

• Application -> Structure -> Ruleset prerequisites Landing Page

• Upgrade all the pre-requisites to point to Pega7 rule sets

• ABV (Application-Based Validation) feature eliminates pre-reqs after upgrade

22

User Interface - Upgrade Impacted Areas

• All Layouts has to be converted to Dynamic Layouts, Repeating Dynamic Layouts and Column Layouts for responsive UISections

• Retrofit any customizations at harness level to the new Pega7 New / Perform / Confirm / Review harnesses to get latest featuresHarness

• Deprecated, needs to be replaced with Dynamic Container Work Area

• Fixed Portals are not supported. Update existing portals to use Screen Layouts instead of Panel SetsPortals

• Replace all deprecated controls with auto - generated controls Deprecated Controls

• List views are not responsive. Need to be replaced with Report Definitions/ GridsEmbedded List Views

23

User Interface - Upgrade Impacted Areas

• Need to retrofit all inline styles and custom CSS into latest skin rule

Inline Styles/ Custom CSS/Skin

• Eliminate customizations by replacing with OOTB Pega7 featuresCustom HTML/Java

Script

• Customer service has undergone major change in v7.1.3 by introducing new Interaction Portal. This may require considerable amount of effort for old CPM/ CPM Vertical frameworks’ based applications to work as is after upgrade

Customer Service/ Verticalized CPM

• Image Viewer, Performance Analyzer, Dynamic Menus, Open Authoring etc. are still ActiveX dependent. Refer PDN for more details

ActiveX Controls

24

HTML5 Readiness & UI Auto Upgrade Utilities

HTML5 Application Readiness Landing Page

• Need to run Revalidate & Save utility to populate this info

• Lists all harnesses using custom JavaScript or CSS

• Lists all non-Auto-generated sections

• Lists all sections using deprecated controls, layouts and inline styles

UI Auto Upgrade Utilities

• Upgrading Deprecated Controls

• Upgrade Work Area to Dynamic Container

• Upgrade Smart Layouts to Dynamic Layouts

• Remove inline styles

• Convert pre-6.1 Flow Actions

25

Maintenance Level Update Process

26

• This process is used only for Pega7 maintenance levels (MLs)

• Process is similar to the Upgrade Process

• Use “Update Build” for updates instead of upgrade build

• Updates can be reversible

• Reversibility is recommended only for sandbox or development environment

Other Batch / Shell Scripts

27

Target Description

Cleanup.bat / Cleanup.sh

This batch script is used to generate the DDL for deleting old Process Commander rule sets

This process is driven through setupDatabase.properties and setupdatabase.xml files

Generateddl.bat / generateDDL.sh

This script is used for generating the DDL for the Rules upgrade and Data-Only Upgrade

This process is driven through setupDatabase.properties and setupdatabase.xml files

Generateudf.bat / generateudf.sh

This scripts generates the UDF statements rules and data schema

This process is driven through setupDatabase.properties and setupdatabase.xml files

Migrate.bat / Migrate.sh

This script is used for migrating the rules as part of Upgrade or Update process

This process is driven through migratesystem.properties and migrateSystem.xml files

Best Practices

• Reduce the number of hops between the system from where you are triggering the upgrade and the database server• This will have direct impact on the time taken for the total upgrade

• Consider skimming the rulesets before starting an upgrade. Delete the old rulesets after skimming

• Rebuild the database indexes before running the upgrade

• Check for Platform support guide before you start an upgrade for supported App Server, Database, Drivers and Browsers etc.

• Modify Database to support User Defined functions (UDFs)• Enable Java for Oracle / DB2• Enable CLR for MS-SQL Server

28

Best Practices

• Backup your configurations and customizations

• Ensure that Java 6 or Java 7 is installed on the machine where you are running the upgrade

• While performing the upgrade make sure that no new rules are being developed

• Use the generate DDL option for generating DDL for Migration, Rules Upgrade and Data-Only Upgrade if automatic schema changes are not allowed

29

Best Practices

• Make sure that directory structure does not contain spaces

• User should have Read / Write permissions on the migrate, bulk mover and temp directories

• Cleanup the unused tables using Optimize schema wizard

• Cleanup the old Process Commander rule sets

• Re-import all custom .jar files after upgrade is completed

30

Upgrade FAQs• Can I skip a release to upgrade from PRPC 5.x

application to Pega 7?

– Yes. Pega 7 supports direct upgrades from PRPC 5.x to Pega 7

• I have 1 TB of work objects, what is the impact on Upgrade?

– No Impact. Upgrade process will not touch existing work objects

• What do I do about my existing platform stack?

– Check platform support guide for supported infrastructure for Pega 7

• Do I need to upgrade other Pega Components like AES, BIX?

– Yes, all the OOTB components need to be upgraded

• What are the risks in upgrades – what is likely to break?

– Underlying business processes, application data are unaffected

• UI Conversion process required to leverage new HTML5 responsive UI?

– Custom UI controls, deprecated portals, non-guardrail implementation will need to be reviewed

• Time to upgrade – what are typical surprises

– Database intensive process – proportional to size of the rule-base

– Framework upgrade must be factored in – it's not just the platform

Next Steps

32

https://pdn.pega.com/upgrade-center

Q & A