EBS 12.2 -- Weblogic Aware Administration

In EBS 12.2 , Weblogic is a core component for us as Apps Dbas..
To have such a capable but also complex Application Server in our Technology Stack brings us the requirement to have advanced administration knowledge about it.. Also , our forms server, oacore server ,oafm and more reside in Weblogic.. So if our Weblogic is down, then we can say that EBS is down from the users perspective.. (http server, listeners, concurrent managers and the database is up actually:) )
Okay, I said advanced , because I have faced the situations which made me spend times to solve..
I mean, if you say "this is EBS , Weblogic is just a component comes built-in, so I manage the Weblogic using EBS tools, and I solve the problems using autoconfig and similar operations in conjuction with Oracle support document" , you will have hard times.. You need to follow oracle support doc, that is for sure but there are times that we need to take deeps dive in to the Weblogic to solve some of our problems, or lets say : to diagnose the problems..

I have seen this, I have done this.. Look at my posts about EBS 12.2.
Weblogic is involved in patching, in cloning, in restarting, in java deployments , in performance problems and so on.. Weblogic itself is also need to be patched rarely..
Sometimes, you connect in to the Weblogic using admin console to take necessary actions and sometimes you wont find an admin console to connect to, that's why using manual approaches..
Anyways, In this post I tried to draw attention to Weblogic in EBS 12.2..  Java knowledge is also important, one should understand the java error stack , one should able to deal with java command line parameters like xmx,xms,permsize so on..

One last thing... If you are not in TXK and AD.C delta 5 patch levels, you will be a Weblogic specialist one day, as there are bugs that you need to diagnose (especially performance)and solve in the previous patch levels.

Essential Weblogic related Bugs fixed in for AD Delta 5 and TXK Delta 5

• Performance improvements have been made for managing application tier services, including implementation of the Managed Server Independence Mode feature (-msimodeparameter to adstrtal.sh) to allow application tier services to be started or stopped without the WebLogic Administration Server running.
• On a multi-node application tier system configuration, remote connectivity is no longer required for packaging the Oracle E-Business Suite WebLogic Server domain.
• JVM heap size (-Xms and -Xmx) has been increased to 1 GB for the WebLogic Administration Server and all managed servers.