Oracle Access Manager (OAM) Upgrade from 11g to 12c - The WLS Admin Server Log Shows - "Component Bootstrap Failed" "Invalid OAM Keystore Configuration"
(Doc ID 2642638.1)
Last updated on FEBRUARY 28, 2020
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
After upgrade from OAM 220.127.116.11.x to OAM 18.104.22.168.0, the first time startup of the WLS Admin server Shows Errors/Warnings "Component Bootstrap Failed" "Invalid OAM Keystore configuration"
- Can successfully access and log into the WLS admin Console
- WLS Admin console shows the Admin server is up and running and the oam_Admin application status as "Failed"
- The WLS Admin server starts but reports back the below errors
- Snippets from the various WLS Admin Server logs
Oracle Access Manager (OAM) Upgrade from 11g to 12c
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|I. EM Console to confirm the password value for the Mbean Operation called Operation "getPortablecred" in regards to the .oamkeystore and the default-keystore.jks|
|II. Validate the keystore with the password retrieved in step I.|
|III. Create a new default-keystore.jks|