On my travels down the WCC projects I have encountered a new and interesting item I wanted to share with you.
I helped a customer do an installation of WebCenter Content 12.2.1.4 and obvious I had them apply all the latest bundle patches for Fusion MiddleWare and WCC.
This is the list of the OPatches we installed:
|
Product |
Patchnr |
Remarks |
|
OPatch |
28186730 |
Make sure to download the version for opatch 13.9.4.2.11 |
|
WLS |
34883826 |
for log4j exploit fix |
|
WCC |
34781126 |
Latest WCC Bundle patch January 2023 |
|
Coherence |
34845927 |
Not strictly used but needed to fix start-up issues |
|
OHS |
34840613 |
|
First important remark here: if you want to install the latest PSU patches for Fusion Middleware and WCC, you first need to upgrade OPatch itself. So start with patch 28186730n before you do anything else.
All the patches installed just fine and everything looked perfectly OK when we created the WCC domain, but when we tried to access the enterprise manager (server:7001/em) it wasn't there.
So we searched the logs and found a message saying:
<Feb 28, 2023 12:12:53,630 PM CET> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "em">
Looking at the rest of the trace, there is an indication that EM was not able to load due to a missing log4j library.
As it turns out, there is something missing. With the serious exploit that got out last year, everybody scrambled to close the breach as fast as possible. Turns out that this can lead to the situation I was in. The Fusion MiddleWare layer is correctly patched, but some of the basic underlying WebLogic core server stuff still has references to log4j.
Fortunately, the fix is easy and straightforward to apply. Simply turn to the Oracle support site and download the following patch: 34542329. Apply this patch using opatch restart the entire stack and everything will be running normally.
