I used to always wonder why people in my office called me WLST Queen.
Guys was it all so that I conduct training for the fresher’s, I would have done it any ways.
Hey, but I had a great time training the fresher’s, oops they shouldn’t be called freshers..trust me they knew a lot about Weblogic.
The management had asked me to share my best practices of handling issues related of WLST.
I had the following topics in my presentation:
-->What is WLST?
-->WLST - Basics
-->Type of cases on WLST
-->Sample cases on WLST
-->Technique to handle WLST case
I totally agree that when we share knowledge, our concepts get stronger. Following is the summary of my training:.
Q. WLST ?
Ans -> A Scripting tool to monitor, manage and configure the weblogic server
Q. WLST Basics?
Ans -> A OOPS language build on Jython libraries, helps in fast performing WLS admin activities which is platform independent.
Q. Types of issues/ cases on WLST
Ans -> Writing a script performing some operations on the server, correcting the syntax errors, troubleshooting the WLST exceptions and understanding why desired output is not displayed.
Q. Techniques of handling WLST issues
Ans -> Replication, WebEx and hands on Python
The best part which I enjoyed was the session where I was discussing my cases and the way I troubleshooted those issues.
The summary of the entire session was that there is no problem which has no resolution। The catch is, you have to identify well before hand the issue gets hot that whether you have the resolution or some one else has it.
The moral of the WLST troubleshooting story is the customer is trying to reach to a destination for which he has discovered a path and finds some obstacles in the way and calls you for help, in this case you do not follow his path, instead discover a easy path which he can walk and meet his destination.