I had a brief email exchange with Bryn about this, which I paraphrase below.
Any errors are MINE, but I hope I have captured the essentials:
1) EBR can be used only after adopting it. And adopting it means changes
to the set of within-database artifacts that define the application's
backend. Moreover, patch scripts then have to be written, for each exercise,
a new way. If you'll be at OpenWorld you can attend the talk by AmEx on how
they did this. CON8704 in the content catalog
<https://events.rainfocus.com/oow15/catalog/oracle.jsp?search.event=openworl
dEvent> .
2) For folks using any off the shelf app, you need to get the software
vendor to adopt EBR methods. In the case of Peoplesoft the vendor is now
Oracle, in particular Oracle's Peoplesoft Development Team.
3) All the up to date documentation and papers starts at oracle.com/ebr
(quite an obvious url, once you realize that is the starting point.)
4) The latest published version of the paper of interest is HERE
<http://www.oracle.com/technetwork/database/features/availability/edition-ba
sed-redefinition-1-133045.pdf> . An update of the document is pending,
likely to include details of improvements for 12.1 and 12.2 when details of
12.2 can be documented.
mwf: For software where you do control the source, the referenced paper
explains the overall process including the "cross editions triggers" that
are essential to maintaining edition correct equivalence across editions you
describe below as "current" and "new" for the code and "active" and
"not-yet-active" with respect to the data. I would urge you to use precisely
the language Bryn uses in the official documents as you move forward.
Good luck with the lobbying effort with development. As per usual my
suggestion on that is to leverage both key accounts AND users groups in that
effort.
Mark
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Chitale, Hemant K
Sent: Monday, October 12, 2015 10:27 PM
To: ORACLE-L
Subject: Edition Based Redefinition with Peoplesoft 8.x / 9.x in 11.2
I understand that EBusinessSuite (EBS) was a primary driver for Edition
Based Redefinition (EBR).
(Referencing Bryn Llewellyn's comment at
https://connormcdonald.wordpress.com/2015/04/03/edition-based-redefinition-a
n-apology/ )
However, I am looking for references / experiences using EBR with Peoplesoft
applications.
Peoplesoft doesn't use Triggers and Stored PLSQL to the extent that EBS
does.
(Peoplesoft is "database agnostic").
SQL definitions are stored in a number of tables and, at runtime, the SQL
definitions are read and submitted for execution.
How could we use EBR for a scenario where we need to change Peoplesoft code
"on-the-fly" --- i.e. have two different "versions" of the code
co-existing. The "current" version running batches and application till the
"new" version is completely migrated into Peoplesoft. Obviously, both
"versions" are simply rows in different tables. So, we'd have to have a way
to specify "active" row and "not-yet-active" row in a way that is
transparent to Peoplesoft.
Similarly, there may be "new" active tables and "new" columns (possibly
could be handled to by editioning views). But do we need to add "hooks"
into Peoplesoft to handle this.
I've never worked with EBR but have only downloaded Bryn Llewellyn's
presentation (2011 OOW ?)
Hemant K Chitale
This email and any attachments are confidential and may also be privileged.
If you are not the intended recipient, please delete all copies and notify
the sender immediately. You may wish to refer to the incorporation details
of Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at
https://www.sc.com/en/incorporation-details.html
