WebGate Artifacts Not Getting Generated On The Servers After 10g/11g Agent Registration
(Doc ID 2485458.1)
Last updated on SEPTEMBER 18, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
You created new OAM server instances in Primary and CLONE, and then add the CLONE OAM server in the ssoWG on Primary, it will generate artifacts only in Primary. Later when you come over to CLONE site, this will show up in OAMConsole, but will not generate the artifacts in CLONE host servers.
If you pickup and copy the artifacts from Production, it will have incorrect entries for CLONE in ObAccessClient.xml file.
OAM Diagnostic log shows -
[2018-12-14T20:13:47.837+00:00] [AdminServer] [ERROR] [] [oracle.oam.engine.remotereg] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ] [APP: oam_admin] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: ] Not able to create webgate Directory
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 |