Discussion

4
Replies
757
Views
VenugopalA Member since 2016 5 posts
JP Morgan
Posted: April 27, 2016
Last activity: April 6, 2018
Closed

Upgrading Pega 5.5 to Pega 7.2 using single schema and then splitting the schema

We are upgrading Pega 5.5 to Pega 7.2 using single schema and then splitting the schema.

With reference to guide pega-72-platform-upgrade-guid.pdf. I am some queries/concerns as mentioned below. I would be happy if someone could answer these concerns/queries. Thanks

--------------------------------------------------------------------------------

Step1 : Migrating the rules tables with one database (page 44 & 45)

Use the migrate script to migrate the rules tables and other required database objects from the existing rules schema to the new schema

pega.source.rules.schema=original data schema name

pega.target.rules.schema=new rules schema name

pega.target.data.schema=original data schema name

Note: If pega.target.data.schema is blank, the rules schema is used by default.

Query/concern:

1. why "original data schema name" is mentioned in source.rules.schema and target.data.schema. As per my understanding the target.data.schema should by PEGADATA.

2. Also in this step we are migrating rules table from source.rules.schema to target.rules.schema then why target.data.schema needs to be mentioned?

--------------------------------------------------------------------------------

Step2 : Upgrading the migrated rules schema (page 46)

pega.rules.schema=new-rules-schema-name

pega.data.schema=new-rules-schema-name

--------------------------------------------------------------------------------

Step3 : Generating rules schema objects (page 48)

pega.source.rules.schema=original rules schema

pega.target.rules.schema=new rules schema

pega.target.data.schema=original data schema

Note: If pega.target.data.schema is blank, the rules schema is used by default.

Query/concern:

1. In this step we are generating rules schema objects then why target.data.schema is mentioned?

2. why target.data.schema is mentioned as orginal data schema, shouldn't it the target.data.schema be PEGADATA?

--------------------------------------------------------------------------------

Step4 : Upgrading the data schema (page 72)

pega.rules.schema=new-rules-schema-name

pega.data.schema=original-data-schema-name

Query/concern:

1. In this step we are upgrading data schema then why rules.schema is mentioned?

2. why target.data.schema is mentioned as orginal data schema, shouldn't it the target.data.schema be PEGADATA?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn