V7 Upgrade Guides - "In-place" upgrade?
A documentation question for Mary Carbonara and others.
The 7.1.8 upgrade guide is twice as long as the v7.1.7 version.
Is this because 7.18 is vastly more complex, or the upgrade is more complex? Or was it expanded for clarity? I expect some of both.
This is from the v7.1.7 documentation. Italics mine.
"PRPC 7.1 supports in-place upgrades and will continue to work with a standard configuration. This is now known as a single-schema configuration. In addition to a standard in-place upgrade, PRPC 7.1 provides new tools and a process to create a new 7.1 compliant split-schema configuration from a PRPC 5.x or 6.x single schema configuration. ... A split schema configuration is now the recommended configuration for new PRPC 7.1 installations, and for any customers upgrading to PRPC 7.1."
So the text is asserting that the standard upgrade - which just isn't the same as the recommended upgrade. What is the value of the in-place upgrade? Maybe it's just simpler?
A documentation question for Mary Carbonara and others.
The 7.1.8 upgrade guide is twice as long as the v7.1.7 version.
Is this because 7.18 is vastly more complex, or the upgrade is more complex? Or was it expanded for clarity? I expect some of both.
This is from the v7.1.7 documentation. Italics mine.
"PRPC 7.1 supports in-place upgrades and will continue to work with a standard configuration. This is now known as a single-schema configuration. In addition to a standard in-place upgrade, PRPC 7.1 provides new tools and a process to create a new 7.1 compliant split-schema configuration from a PRPC 5.x or 6.x single schema configuration. ... A split schema configuration is now the recommended configuration for new PRPC 7.1 installations, and for any customers upgrading to PRPC 7.1."
So the text is asserting that the standard upgrade - which just isn't the same as the recommended upgrade. What is the value of the in-place upgrade? Maybe it's just simpler?
Also from 7.1.7: "Note that you must execute an in-place upgrade in at least one environment."
Why?
The text quoted above was eliminated in the guide for 7.1.8: "Upgrade the Development system using the standard in-place upgrade process."
It's still called "standard." Again, why? Is it just simpler? Practically speaking, is split-schema not needed in development? (We'd done so in an our clean v7 setup, since we figured it would best resemble the other environments).
Suppose we need to keep the v6 environment around (for support of the v6 application).
My sense is, we would clone the v6 system and then run the Pega7 upgrade on that (is that "in place" or "out of place" or does that terminology really matter?), and then proceed with our unit testing of that, the update of our own rules, etc.
***Updated by moderator: Lochan to close 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.
Pegasystems Inc.
US
Susan Carboni did a lot of work on the new 7.1.8 upgrade guide. She may be able to provide more insights.
Updated: 17 Jul 2015 9:41 EDT
Thanks John!
You're right; the major benefit of an in-place upgrade is simplicity. The changes to the upgrade guides for Pega 7.1.8 added pages as we tried to make the process clearer and the guides easier to use regardless of your upgrade path.
Although Pegasystems recommends a split-schema configuration for development systems, single-schema is still supported.
As for your question about upgrading from PRPC 6, please follow the instructions in the upgrade guide for your path:
- single-schema to single schema
- single-schema to split schema
- split-schema to split-schema
The upgrade guides include information about how to migrate for each path.
I will look into the difference between a standard upgrade and a recommended upgrade and will respond to that ASAP.
Pegasystems Inc.
US
I will look into the difference between a standard upgrade and a recommended upgrade and will respond to that ASAP.
A “standard” upgrade is the traditional in-place upgrade process used for upgrades to 6.x and earlier, and a “recommended” upgrade is the new out-of-place upgrade process introduced in 7.1. Yes, in-place upgrades are simpler since tables do not have be migrated and there is no data schema upgrade step.
Pegasystems Inc.
US
Jon,
It appears that the two Pega SMEs have answered your question. Yes?
Can you mark this discussion closed with Correct Answer?
The Upgrade Guide changes suggested in this discussion have been made for the Pega 7.1.8 and the pending 7.1.9 deployment guides (and for all future releases as needed).
Following standard practice, Pega 7.1.8 documentation was modified in response to high-priority bugs. The product doc team is now focused on the Pega 7.1.9 documentaion deliverables.
Thanks!
-Mary