WebLogic Admin Tricks & Tips

Today I want to test Sun One WebServer 7 proxy plug-in with WebLogic 11g. Mr. Prasanna yalam suggested to use autodeploy of simple Jsp to the connectivity. To Autodeploy a web application in WebLogic Standalone AdminServer we need to follow the steps:1. create a Exploded folder say for example 'myweb' in domain_name/autodeploy folder2. create a Test.jsp file using any editor Hello from WebLogic Pavan Devarakonda save this fileat the same folder create WEB-INF folder 3. create web.xml deployment descriptor file 4. touch WEB-INF/REDEPLOY create this file for new timestamp when AdminServer lookup for the autodeployments. verify this on the console deployments section.choose Testing tab and click on the url with Test.jsp that's all you need to do..It will give you the autodeployed application output on your browser. Ref: http://download.oracle.com/docs/cd/E13222_01/wls/docs92/deployment/autodeploy.html#wp1021620

The Oracle WebLogic Server instances are nothing but each one running on a single JVM, when this JVM crashes there could be one of the reasons as overworking of Garbage Collection or not working at all (waiting continuously).   It is good practice that monitoring GC in JVM with detailed statistics will give you a clear idea to analysis at what circumstances happening wrong. And the best way to look in deeper levels of garbage collection also like Young Generation (Eden space, Survivor spaces S0, S1) Old Generation (tenured Generation), and Perm Generation (Statistic Objects/Classes). JDK 1.5 and latest providing excellent JDK command utilities for interrogate the current running Java Process and look inside of JVM take snap with following: 1. jps (Java Process) 2. jstat (JVM status) The 'jps' command with -lv options gives you complete detailed java process arguments for MEM settings and relavent WebLogic Server instances name. We have already discussed about this command ...

Some times the WebLogic Server logs showing that one of the managed server removed from the cluster... How to confirm in faster way or from commandline... it is pretty simple way is... java  weblogic.Admin -url adminserver:port -username user -password passwd CLUSTERSTATE -nameofthecluster

My experience on experimenting with WebLogic domains repository that is config.xml . It was a challenging experiment, where the WebLogic 9.2 MP3 was the version on which I did this workout. Here the basic thing need to know is how the config.xml is constructed and referring to the "http://www.oracle.com/technology/weblogic/90/security/wls.xsd". This is the major change new versions using XSD to ensure that quality of XML is wellformed in the config.xml Before editing the config.xml Smart Admin always prefer to take backup before editing the config.xml. You need to take a complete backup that should include the jdbc, jms directories if already created. To ensure complete backup of configuration use the following command: cp -R config config_date Editing with vi editor Here you need to have little wise thinker to understand about complexType, simpleType, sequance these all XML schema types and used to define the xml instances (xsi).  What we can edit in the confi...