1 person found this helpful
Clearly you applied Apr 2019 CPU which introduced the connection filters to EBS 12.2. You can check below links to fully understand this behaviour:
Alternative Methods to Allow Access to Oracle WebLogic Server Administration Console from Trusted Hosts for Oracle E-Business Suite Release 12.2 (Doc ID 2542826.1)
Basically what you need to do now is:
** Edit the run file system context file to set the value for the s_wls_admin_console_access_nodes context variable to the list of trusted hosts that are allowed to access the Admin Server. For each host, specify either the FQDN or the IP address. Use commas to separate the hosts in the list. For example:
** Run AutoConfig.
** Stop and restart the Oracle WebLogic Admin Server.
Ensure you take necessary backups and needless to say test it first in Non-Production.
Hello. Does this need any downtime? we have cloned PROD to TEST again because we could not fix the issue. As you said we applied cpu patches before. we will apply and check the solution.
weblogic must be stop to take the new setup
thank you all. we fixed the issue now.