Question
JP Morgan
IN
Last activity: 27 Apr 2016 8:48 EDT
We are 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
--------------------------------------------------------------------------------
@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?
Message was edited by: Marissa Rogers - added category
Pegasystems Inc.
IN
Hi Venu,
I request you to review the forums specific to Upgrade on Pega Upgrade center at below:
https://pdn.pega.com/forums/pega-upgrade-center
You would find all Upgrade related FAQ here,
Pegasystems Inc.
US
Just to confirm you are trying to upgrade from 5.5 single schema to 7.2 single schema and then want to split the 7.2 single schema into 2 schemas. You can certainly do this. You would just run the upgrade either via UIA tool or with the upgrade script and then you would use the migrate script to split. There are SA articles on how to split a schema after an upgrade.