Oracle Access Manager (OAM) High Availability Setup - Second OAM Host Is Not Showing In Weblogic Domain
(Doc ID 2632260.1)
Last updated on MAY 15, 2024
Applies to:
Oracle Access Manager - Version 11.1.2.3.180717 and laterInformation in this document applies to any platform.
Symptoms
Oracle Access Manager (OAM) High Availability Setup - Second OAM Host Is Not Showing In Weblogic Domain
1.Following the documentation for "Configuring High Availability for Oracle Access Management Access Manager Components"
2. The below step to startup OAM on the second node, there is no <
6.4.10.3 Start Access Manager on <OAM_HOST_X>
To start Access Manager on <OAM_HOST_X>:
Log into the WebLogic Administration Console using this URL:
http://<OAM_SERVER_FQ_HOSTNAME>:<WLS_ADMIN_PORT>/console
Supply the WebLogic administrator username and password.
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Click the server <WLS_OAMX>_SERVER>
Click Start.
Click OK to confirm that you want to start the server.
To start Access Manager on <OAM_HOST_X>:
Log into the WebLogic Administration Console using this URL:
http://<OAM_SERVER_FQ_HOSTNAME>:<WLS_ADMIN_PORT>/console
Supply the WebLogic administrator username and password.
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Click the server <WLS_OAMX>_SERVER>
Click Start.
Click OK to confirm that you want to start the server.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |