Oracle Access Manager (OAM) - After Upgrading OAM To 12C, OHS Is Not Found In OAM Domain
(Doc ID 2772094.1)
Last updated on MAY 04, 2021
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
12c Upgrade guide mentioned starting OHS after upgrade. However, the OHS within OAM domain can not be found
MiddlewareFusion MiddlewareRelease 184.108.40.206, Upgrading Oracle Access Manager, 3 Upgrading Oracle Access Manager Single Node Environments, Verifying the Domain-Specific-Component Configurations Upgrade, Starting Servers and Processes, Step 3: Start the Managed Servers
Method 2: Start a WebLogic Server Managed Server by using the
DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
When prompted, enter your user name and password.
- The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.
- The Mobile Security Manager (MSM) servers are not supported in 12c. After restarting the servers, the 11g configurations of MSM servers, like
WLS_MSM1, might remain. Ignore these configurations and do not restart the MSM servers.
To start system components, such as Oracle HTTP Server, use the
You can start system components in any order.
Upgrade OAM 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