Updating the New WebCenter Content UI (ADF User Interface)
By Ken Walker-Oracle on May 05, 2014
Have you ever purchased a brand new toy that "required some assembly," only to discover that the instructions were so impossibly complex that you needed an engineer's help in putting it all together? Recently, the decision was made to separate the code required for the new Content UI (for WebCenter Content Server) so that it could be updated with code bundles independently of the patch updates released for WebCenter Content Server. This is fantastic news, in the long run, but it complicated things a little bit when this particular cow was separated from the herd.
Things are on track now, running smoothly, but there are some things you may need to know to get your software "right" and ready for the new code bundles that will be released in the future. To get your WebCenter Content UI updated, safely and correctly, to the latest available code (220.127.116.11.0), you'll need to follow these steps (if you haven't already done so):
The first Content UI bundle has been released. You can find it (and all subsequent releases for Content UI) in Note 1666237.1 Development has recommended that you bring your current Content UI implementation up to one or the other of the following levels BEFORE applying bundle #1 in the series:
a) Update the UI with the wccadfui.zip that comes with the MLR3 Content Server Patch for WebCenter Content 18.104.22.168.0.
b) Update the UI with the wccadfui.zip that comes with the MLR4 Content Server Patch; and here's the interesting part, only after Patch 18503310 has been applied to your MLR4 environment! Otherwise, you will not be able to implement the wccadfui.zip. (Important: If you are running the MLR4 release on your server, please be sure to read Note 1642394.1!!)
After the above has been resolved, then, you can apply the new code bundle for the first patch release of the Content UI (found here, or in Note 1666237.1 released 4/15/2014. Follow the Patch's Readme file for all the steps required to apply this Patch to your Content UI Middleware Home)