Re: R12.2.4 adcfgclone on taret - unable to delete managed servers, OHS Config errors

Posted by ErmanArslansOracleBlog on Jun 02, 2016; 4:41am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/R12-2-4-adcfgclone-on-taret-unable-to-delete-managed-servers-OHS-Config-errors-tp1031p1051.html

Hi ,

There are 2 facts;

1) ADF applications are not intended to be used on the same Weblogic server home for E-Business Suite.

2) Online patching manages automated movement of applications/configurations between the two Oracle Homes ( patch and run), and "tools are not aware of any additional applications or customizations". Thus ADF is not intended to be installed inside the FMW_home that EBS uses. It should be installed on a separate Weblogic server.

You can check : FAQ for Integration of Oracle E-Business Suite and Oracle Application Development Framework (ADF) Applications (Doc ID 1296491.1)

So, based on these , probably your ADF application is causing the issue.
Besides, the ADF application definition in the moveplan.xml is written before the OA_HTML itself. So the code parse it before the OA_HTML and as it is not hardoced/not expected, it may be encountring the errors.

I reuqested your cluster and managed server conf, because I saw there were 2 definition in your moveplan.xml, which includes the same managed server+port, that is the oacore_server2:port

I didnt see the ADF there, but when you say that there is an ADF, I recognized the situation..

You can try 3 things:
1)You may need to modify the code for that (put an if clause or something like that in "UpdateOhsT2PMovePlan.class" to make it ignore your ADF application)  -- this will be super unsupported :)

2)You can make Oracle to send you a patch or a modified java class for the above(for the Step1)

3)You can try placing your ADF application in to a new managed server (lets say create a managed server named blabla and place it there) --unsupported (creating a custom managed server in EBS 12.2), but can be tried with taking the risk

4)You can try changing the order of the moveplan.xml, and make the ADF portion  to be after OA_HTML portion..

On the other hand, 3-4 may not work, you need to try and see.
The best solution is , placing ADF application outside the EBS.

Well, waiting for your updates on this.