EM 13.2: Oracle Cloud Control Autodiscovery Fails To Discover Weblogic Domain Targets With The Same Domain Name, but On Different Hosts
(Doc ID 2212767.1)
Last updated on JUNE 12, 2023
Applies to:
Enterprise Manager for Fusion Middleware - Version 13.1.1.0.0 to 13.2.1.0.0 [Release 13.1]Information in this document applies to any platform.
Symptoms
If you have separate WLS domains with the same name on different hosts, the Auto-Discovery feature does not discover the second Weblogic Domain because it would cause a duplicate name in the Enterprise Manager (EM) Repository. For example, if you have a WebLogic Domain called 'myDomain' on <HOSTNAME1>.<DOMAIN_NAME> and another WebLogic Domain also called 'myDomain' on <HOSTNAME2>.<DOMAIN_NAME>, AND the first host & WebLogic Domain have already been discovered, Auto-Discovery will not discover the domain by the same name on the second host.
This is evident if you navigate to Setup > Add Target > Configure Auto Discovery > Discovery Modules: <HOSTNAME2>.<DOMAIN_NAME>
You will notice the Page has 'Oracle Fusion Middleware' Module enabled and Discovery Parameters have: Enter value of Middleware Home(s)=*
The 'Discovered Targets' column for this host shows zero (0) despite the existence of a WebLogic Domain on this host.
Changes
The existence of two separate WLS Domains of the same name on two separate hosts.
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 |