Recommended Patches for Oracle WebCenter Portal
(Doc ID 1087226.1)
Last updated on JULY 27, 2019
Oracle WebCenter Portal - Version 126.96.36.199.0 and later Information in this document applies to any platform.
WebCenter Bundle Patches
The goal of this document is to supply customers the recommended and most up to date patches for the Oracle WebCenter 11g product.
As part of Oracle’s overall commitment to full support and reliability of any released version of its software, Customers are expected to always implement the latest Bundle Patch in all environments Bundle Patches target product defects reported by our customers in their use of the version the patch has been created for. Applying the bundle patch assures our customers that they do not have to find a “known issue” in their environment to benefit from a fix that has been implemented in another customer’s environment. The Bundle Patch provides cumulative compilation of all such fixes.
While individual one off patches are not fully tested, the Bundle Patch go through rigorous Quality Assurance (QA) testing and provides the customer with a level of assurance that applying the bundle will not have any negative impacts. Bundle Patches for WebCenter Portal and other FMw products to be targeted to be uniformly available on specific dates (see below).
From July 2012, we 've started to release quarterly Bundle Patches for many of the FMW products, including WebCenter Portal. The schedule aligns with the Critical Patch Updates (CPUs) schedule, which is January, April, July and October. Hence the planned and release dates are as following:
17 July 2012 --> Released PS5 BP3 (188.8.131.52.3)
16 October 2012 --> Released PS5 BP4 (184.108.40.206.4)
15 January 2013 --> Released PS5 BP5 (220.127.116.11.5)
16 April 2013 --> Released PS5 BP6 (18.104.22.168.6)
16 July 2013 --> Released PS6 BP1 (22.214.171.124.1)
15 October 2013 --> Released dot8 BP1 (126.96.36.199.1)
14 January 2014 --> Released dot8 BP2 (188.8.131.52.2)
15 April 2014 --> Released dot8 BP3 (184.108.40.206.3)
15 July 2014 --> Released dot8 BP4 (220.127.116.11.4)
14 October 2014 --> Released dot8 BP5 (18.104.22.168.5)
20 January 2015 --> Released dot8 BP6 (22.214.171.124.6)
14 April 2015 --> Released dot8 BP7 (126.96.36.199.7)
14 July 2015 --> Released dot8 BP8 (188.8.131.52.8) & dot9 BP2 (184.108.40.206.2)
23 October 2015 --> Released dot9 BP8 (220.127.116.11.8)
19 January 2016 --> Released dot9 - 18.104.22.168.160119WCPBP - new BP version numbering introduced - refer to KM <Note:2061926.1>
19 April 2016 --> Released: dot9 (22.214.171.124.160418WCPBP) and R12 (126.96.36.199.160419WCPBP) --> new BP version numbering introduced - refer to KM <Note:2061926.1>
19 July 2016 --> Released: dot9 (188.8.131.52.160719WCPBP)
18 Oct 2016 --> Released: dot9 (184.108.40.206.161018WCPBP)
17 Jan 2017 --> Released: dot9 (220.127.116.11.161128WCPBP)
Oracle WebCenter 11g sits on top of ADF technology.
This means that customers using Oracle WebCenter Portal 11g, may benefit from ADF patches as well (into the oracle_common Oracle Home directory). This is the reason why they are referenced within this note.
For other product Bundle Patches, like for Oracle SOA, Oracle WebCenter Content, Oracle Access Management, Oracle Identity Management, etc. are equally recommended to be installed in their recommend suites/Oracle Homes, if you are integrating the Oracle WebCenter Portal, with those products. Such will make sure that the software is as much up to date as possible for the patchset you'll be in. Mixed versions between products are highly discouraged, unless properly documented within Product Documentation and/or FMw Certification matrix.
To know what are the most recent Bundle Patches for other Products, please do kindly refer to the:
<Note:1494151.1> - Master Note on Fusion Middleware Proactive Patching - Patch Set Updates (PSUs) and Bundle Patches (BPs)
IMPORTANT TO READ
The note refers to two separate sections, eg, one for the Oracle WebCenter (server side) and one for the Oracle JDeveloper (development side / IDE), due to both MUST match in terms of version and patch level, so that in both systems there won't be any discrepancies in any library.
For the WebCenter server side, nothing extra needs to be done as the install of the patch(es) on that side requires a restart of the Spaces managed server(s). On the JDeveloper side, and for end users, which are still developing things through the JDeveloper, it is highly recommended, post installing the same level of patch(es), to restart the Integrated WLS, recompile things, redeploy them, so that the fixes are properly uptaken. If you are deploying them on the WebCenter server side, and such contains already the same patch(es), it is recommended to do the same.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!